Comparison between solito and expo-router #428
Unanswered
ts-candide
asked this question in
Q&A
Replies: 1 comment
-
i recommend going through the docs and maybe watching some of my talks on there to better understand it. solito’s main thing is that it uses next.js on web and leverages the next.js API semantics. it makes these APIs map onto native too. expo router came along later and added file system routing, powered by react navigation under the hood. since solito uses react navigation on native, it automatically works with expo router too. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to evaluate a toolchain for building a so-called 'universal' app, sharing code across web and native. I came across solito from the tamagui project, which has an example monorepo setup with solito.
I'm also aware of the expo-router project, which seems to have similar goals to solito. Furthermore, I notice that the solito monorepo examples include a setup with both solito and expo-router.
Forgive my ignorance, but I'm unsure how solito and expo-router can work together. They both seem to achieve the same goal - routing in universal apps - so why/when would I want to use them together?
Beta Was this translation helpful? Give feedback.
All reactions