Developing for multiple platforms.
Have you folks found any significant drawbacks of building even pure web apps (sometimes full stack sometimes not) with the same technologies/stack you would use for building a full stack universal app?
Also would be interesting to hear what stacks you folks would opt for if you were building a full stack web + mobile project with the same functionality on both platforms.
Background:
Working at a venture builder / agency that does a lot of web / mobile projects full stack. Sometimes only mobile, sometimes only web and sometimes both.
Considering if we should have only one unified template / CLI at work where you select if you want web, mobile and backend individually (And use universal app tools like Tamagui and Solito for the web aspects even if we are not building a mobile app)
1 Reply
If i were to be building a app with web + mobile i would be using something like react and react native with something like expo. i has seen teams use react native as a standised apporach to building web apps and just change the complier to use their custom components so for example a
View might be a customised div element.
I can't find the video but this is something that Twitter (X) did for their webapp for mobile devices.
Expo has released support for building out web apps (https://docs.expo.dev/workflow/web/).
I think the biggest benift to building the web app with react and a frame work than using something like react-native is that is essentally the same logic just changed so you can share code, functions and much more between the platforms in a mono repo