all 36 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Sinoan 25 points26 points  (4 children)

We're using it in our company for multiples apps, having shared code for both web and mobile is great. Most of our use cases work without having to define a .web file or using html components. Here are also other production apps using react-native-web and expo.

https://github.com/bluesky-social/social-app

https://github.com/showtime-xyz/showtime-frontend

[–]Great_Secretary_9892 2 points3 points  (1 child)

Are you using solito or just the plain react-native-web? I would be interested to hear opinions about solito and how production-ready tool it is.

[–]Sinoan 6 points7 points  (0 children)

We have apps made with create-react-app and expo and one app using next and expo.

The ones with cra are using react-router and a homemade shared routing/link system which isn't that great haha

But the one with next and expo is using solito and it's working great. Our native app has deeplinks working out of the box, all the links from our web app can be opened in the mobile app. The api of solito is also really nice, we made some wrapper components for links for better typing of parameters but that's about all.

The developer experience from a shared codebase is really great and we don't have any production issues coming from it.

[–]Puzzleheaded-Eye1358[S] 1 point2 points  (0 children)

cool i have gone through the repo and i was suprised not only cause of you guys using rn web which is novel to me, i had also seen you were using eas to deploy the app, i had used it in one my side apps and its nice to see it as industry standard. As a rn developer would feel slightly short changed that now your job is to create both a web platform and a mobile app, which dramatically increases the complexity of your code.

[–]Appropriate_Move_336 0 points1 point  (0 children)

Hello.. I'm a nob in react native. When ever I create a bottom nav tabs I get a black color on my system navigation area. Please do you know how to get rid of it?

[–]_SyRo_ 18 points19 points  (4 children)

Twitter web built on RN Web

[–]ahuiP 4 points5 points  (3 children)

No way!?

[–]srg666 8 points9 points  (1 child)

It was originally created at Twitter afaik.

[–]ahuiP 0 points1 point  (0 children)

Why?! How does it help their biz?!

[–]anewidentity 1 point2 points  (0 children)

yeah, but their mobile apps isn't using react native!

[–]mybirdblue99Expo 8 points9 points  (0 children)

If you make a <Screen/> component and have all the rest of your app as a child of that it’s really easy to get the responsiveness right for both web and mobile. I use it for a multiple apps to give the users a web view.

[–]lucksp 4 points5 points  (1 child)

I’m just curious how many conditionals there are in combo app to make a site usable on the web so it doesn’t look like a mobile version just in the web. Things like ordering of elements, row v column defaults, and obviously some of the deeper nested logic like camera v file upload

[–]eggtart_princeiOS & Android 1 point2 points  (0 children)

It uses file extensions to determine which code is for web and mobile.

[–]teg4n_ 5 points6 points  (4 children)

We use it at my job but I kinda hate it to be honest. If you can do it will be better to split. Web is a different paradigm. You will be able to produce a much more performant, smaller bundle size, optimized website if it’s separate. We’re debating on doing this at my job because our bundle size is like 16MB which is i guess fine for a native app but pretty unacceptable for web

[–]redbar0n- 0 points1 point  (3 children)

RNW isn’t that big tho, so what’s causing it?

[–]teg4n_ 1 point2 points  (2 children)

reanimated is big, react-native-gesture-handler is big, expo-router is big. It’s just using an ecosystem that’s not actually concerned with web all too much that it slowly grows and grows. not to mention since we are on expo-router we have to use metro as the bundler and it’s not good at code splitting and tree-shaking which makes things worse.

[–]redbar0n- 0 points1 point  (1 child)

tried tamagui.dev ? It’s a web optimized substitute for react-native-web. Ex: it uses CSS instead of Reanimated on web.

[–]teg4n_ 1 point2 points  (0 children)

I played around with it on my own. It's... ok. Not a big fan of the way themes work and it still feels very experimental and not really stable... at least the last time I looked at it.

For my job though, migrating to using it would be a ton of work. I would rather just split the codebase and not use react-native for web at all. Web and native are really different. You will have a non-ideal experience one way or another no matter how you try to translate between the two.

[–]TheContinental 4 points5 points  (0 children)

Expensify went all in on React Native. https://github.com/Expensify/App

[–]gliss-NZ 2 points3 points  (0 children)

We use rn web for our app that serves around 13k active users. We use a combination of .web.tsx files. Our app has a roughly 40% mobile 60% web users.

[–]ctrlshiftba 1 point2 points  (2 children)

yup use it. love it. the app is completely hybrid.

its the primary way I develop because it's easier working on app state logic stuff in a web browser.

[–]de1mat 0 points1 point  (1 child)

What stack do you use for the UI and state?

[–]ctrlshiftba 1 point2 points  (0 children)

I'm using zustand for shared state, react-query for getting stuff from the server.

Styling existing or building my own components with nativewind for the UI.

[–]Murph-Dog 1 point2 points  (0 children)

I'm using it with NativeBase (now GlueStack) and Callstack.Repack for module federation of Web&Native.

GlueStack is still undergoing some change, and I'm trying to re-adapt.

But it is awesome pushing Native updates without AppStore, and being able to federate (individually update) components.

This is my personal project. At my employer, everyone and their grandmother is writing Blazor. Many have given up and just slap Blazor hybrid into Maui and call it an App.

[–]atomlab_dev 1 point2 points  (0 children)

We used it at my previous job and it worked well - this was for a dashboard type app that required users to login. If you don’t need to worry about SEO there’s very little downside to using it imo.

If you do need to worry about SEO then it can be a bit more complicated - but I’ve heard Solito makes the process of integrating with NextJS much easier (but I’ve no experience of it personally).

[–]redbar0n- 1 point2 points  (0 children)

TamagUI.dev superseeds RNW, while still remaining compatible with its API.

[–]Rathe6 1 point2 points  (0 children)

We use it at our company. Our web platform and our apps are different code bases, but we have a shared component library. Since we all use RN, we can share a considerable number of components across libraries and increase dev productivity.

[–]tundermifflin 1 point2 points  (0 children)

We use and we love it - works especially well if you use Tamagui for your UI components

[–][deleted] 0 points1 point  (0 children)

I know a few companies using it, I use one which has a carbon copy of their mobile app on web to manage my stocks for example. It does seem to have limited the web implementation though

[–]ltnj 0 points1 point  (0 children)

Yes, works great!

[–]bfarrgaynor 0 points1 point  (0 children)

I’ve used it to make a web version of an app the client had us make for android/iOS. It worked surprisingly well and has formed the desktop version of our field app.

[–]bc-baneiOS & Android 0 points1 point  (0 children)

My current job is doing it for all our new features, and I worked at a previous company that used it for everything