🌐
Reddit
reddit.com › r › expo
Expo
September 9, 2021 - I’m building an app with Expo and I’d love to hear what UI/design libraries you’re using in your projects. I’m curious about things like component libraries, styling systems, and design frameworks that work well with Expo. ... Is Tailwind (or Tailwind-style utility libraries like Tailwind-React-Native / NativeWind) a good fit for Expo?
🌐
Reddit
reddit.com › r/reactnative › i’m in love with expo web
r/reactnative on Reddit: I’m in love with expo web
December 18, 2019 - ... So, if I create an app with ... Workers/Any static host? ... That's basically it. Expo web generates a PWA which your users can install for offline use....
🌐
Reddit
reddit.com › r/reactnative › we’re building an expo app, what’s the best approach to create the web version?
r/reactnative on Reddit: We’re building an expo app, what’s the best approach to create the web version?
September 24, 2025 -

So we’re building an expo app (compatible with IOS/Android). It has chat and a media player with complex features. Some of the libraries used doesn’t work on web, as well as the library used for the cache. We want to have a working web version obviously. It has a different design in few pages, also we need to replace some libraries. So we’re debating whether to do the web in a different codebase using react, or continue using expo web. A different codebase will be cleaner and more optimised but means double the effort for maintaining.

🌐
Reddit
reddit.com › r/expo › how easy is it to convert a react native expo app to a website? (i fucked up with a client request)
r/expo on Reddit: How easy is it to convert a React Native Expo app to a website? (I fucked up with a client request)
September 8, 2024 -

Long story short, my client and I used both used the word "app" very differently. He thought I was building a web app, I thought he wanted me to make a mobile app. Now I have a fully built React Native Expo app and he wants a website. Around how much time will it take to convert this to a fully-functional website? From what I could find on the Internet, most of the logic can remain the same and only my visual designs (which are fairly simplistic) have to change. If that's true, how do I go about it? Any help is extremely appreciated as I'm 16 and potentially in some deep shit.

Find elsewhere
🌐
Reddit
reddit.com › r/reactnative › creating a cross platform application. react native web vs expo?
r/reactnative on Reddit: Creating a cross platform application. React native web vs Expo?
October 5, 2023 -

Hi guys,

I am creating a fairly complex application that will have majority of its functionality on web and a separate set of functionality for mobile (bar a few features). For example most of the web features will not be available on mobile, except for the likes of in-app messaging which should be available on both. Mobile app will have a smaller subset of features that are not available (but may be in the future) on web.

I have been thinking of using react native for the mobile side and rn-web for the web app. But I am new to react native and still learning. I have just come across Expo and am thinking of using that instead but have seen some gripes about how the user experience of an Expo built app vs a RN app is worse.

What do you guys think? What are the pros and cons? I see the developer experience is easier with Expo but is the tradeoff of a worse user experience worth it? The app is complex but not extremely complex. I essentially want a fairly easy development experience with a good user experience. Not sure if the tradeoff is worth it for my customers.

Top answer
1 of 2
4
The way I see it, you've got 2 options: Have a single codebase under Expo Have 2 separate codebases, one as a traditional React project, the other exclusively as RN (expo or non-expo) In the first one, you've got the benefits of consistency in your data layers. You can share typescript interfaces across web and mobile. The downside is that you're going to end up having a lot of platform-specific code. Even if both projects are related, you said that both projects have different feature sets. That alone makes managing everything in a single project more complex, but the time savings from not having to worry about syncing interfaces and common code might negate that. You can opt for a monorepo where both projects live in the same space, but are independent projects within it. That's added complexity, but does offer a nice tradeoff when it comes to sharing code. In the second one, you have the upside of simplicity in management. You have the option to go down a non-monorepo approach (typically easier to manage in this context), and it even helps with some of the non-code tasks (i.e. ensuring developers are focused only on one project at a time). The downside is that you don't have any ability to share any code between them unless you create libraries - not a bad approach, but more clunky than the first option. In your scenario, the first option would still be preferable. I'd probably set it up as a monorepo for the sake of not having to sync up on shared code. One web project under Expo, the other native project also under Expo. If the feature set was going to be identical on both platforms, I'd not have a monorepo for it, and would instead use platform-specific logic to determine what to render and what functions to invoke. As for native side specifically, unless you have some specific native integration requirements that aren't supported by Expo, just go with Expo. You can support any native code or library you need in both Expo and non-Expo RN, but it typically requires more work in Expo unless the library is already configured to support it. With that said, most major libs which have been updated at least semi-recently tend to have Expo support.
2 of 2
2
Having just done this for a large, complex commercial app i'd STRONGLY recommend you set up a monorepo with two "apps" (one react, one rn) and write shared responsive packages for each screen/page, then have your react-navigation screens and react-router routes render these packaged components. You can use react-native Views etc for all the shared "Screens/pages" and it works beautifully, but for the actuall application scaffolding it's a total mess. Expo as a universall app platform is still way too fucking janky and expo router is a buggy piece of shit. Perhaps in a year or two expo w/ router will be worth using, but until then seriously don't bother, it took me two fucking weeks to get it working (transitioning from two separate apps w/ shared packages) and it's worse than before, I wish i'd never done it, and i'm seriously tempted to just call those two weeks a hard lesson learned and revert back to the two app setup rather than the universal app. The previuos architecture w/ the monorepo (we used turborepo, but whatever should be fine) was basically like this: ``` /apps -- /web (vite w/ react-router) --/mobile (expo w/ react-navigation) /packages --/screen-one --/screen-two ``` Each app had different ways of doing certain things, but 90% of the codebase was still shared. It was good enough and i was stupid to try to close that last 10% gap.
🌐
Reddit
reddit.com › r/reactnative › react native web and expo for web
r/reactnative on Reddit: React Native Web and Expo for Web
February 19, 2018 -

Starting work on a personal project where the mobile app and web need to have the same functionality. Instead of treating it like two separate projects (i.e., writing for ReactJS, then React Native, and sharing contexts/hooks where I can), it makes sense to treat it like one project.

In playing with expo-cli I noticed in the CLI it mentioed "web" so I started looking into it. That being said, it says in bold:

This is a preview and subject to breaking changes. Do not use this in production yet.

So pursuing using Expo for Web may not be the way to go at this point in time.

Despite that, there is this decent article about it:

https://medium.com/@toastui/from-zero-to-publish-expo-web-react-native-for-web-tutorial-e3e020d6d3ff

The other option I'm seeing is just React Native Web which Expo for Web is using anyway. The documentation on getting started on it is less than helpful. This article does help clearing some of it up:

https://scotch.io/tutorials/build-mobile-friendly-web-apps-with-react-native-web

For example, the Getting Started:

Install

yarn add react react-dom react-native-web 

Starter kits

create-react-app includes built-in support for aliasing react-native-web to react-native.

create-react-app my-app

I guess the "Install" is if you plan on not using create-react-app?

Then it goes on talk about configuring alias despite saying "create-rect-app includes built-in support for aliasing react-native-web to react-native."

Again, I guess all of the bundle configs it goes on to discuss are for if you are not using create-react-app?

Then the article goes on to show:

npx create-react-app random-people

yarn add --dev babel-plugin-module-resolver babel-plugin-transform-object-rest-spread babel-plugin-transform-react-jsx-source babel-preset-expo

Why all the resolvers if create-react-app already has this built in?

I can see point of babel-preset-expo since expo is being added.

At any rate, at least the article actually explains how to setup the development environment and get things to production... nothing I saw in the repos documentation.

I guess one last question: anyone using React Native Web and what are your thoughts on it?

🌐
Reddit
reddit.com › r/reactnative › react native + expo is truly a developers dream
r/reactnative on Reddit: React Native + Expo is truly a developers dream
March 2, 2025 -

Last week I released my first app Waveous to the app store (working on finishing Android) for Spotify users to see their entire lifetime streaming stats, see what music your friends are liking and commenting on, and notifications to not miss new releases from your favourite artists.

I spent the last 6-7 months developing this part time and I cannot say enough good things about the developer experience React Native and Expo provided. Coming from using React for web development, I'm so glad I went with React Native over other alternatives. I don't have a Mac so Expo EAS was a saviour and the rest of the Expo suite is some of the most intuitive and well documented developer tools I've used in ages.

For those who have released apps and successfully got traction, any tips around getting users?

🌐
Reddit
reddit.com › r/reactnative › finally switched from expo to bare react-native
r/reactnative on Reddit: Finally switched from Expo to bare react-native
December 23, 2019 -

I'm working on startup where we are developing a video streaming app. I know react very well but I never worked on react-native. So I started learning few things about it. Expo came to my notice as it makes things lot of easier ( at least they say wherever they get chance ). I started working on our prototype. Initial development was really fast. But later, I came to know that - with Expo, I cannot use native modules from npm or external libraries which are very useful for our case. for example - the payment service which we are using and many other! With expo, you can use only those modules which are developed by Expo.

Finally I shifted from Expo to bare minimal react native project. Following are some benefits -

  1. app size reduced from 20MB + to approx 5-6 MB.

  2. full control over what I want in app and what I don't want.

  3. running app isn't that hard - setting up emulator, installing android studio, installing few more things and that's it. run the app in emulator and you are good to go!

Let's see how it goes further :)

EDIT -

Expo vs react-native debate goes on. I will suggest, if you are beginner in react-native, just try to stick to Expo because learning process is lot easier in Expo. You don't need to touch android/ios folders and don't need to write minor native code in it. Ultimately that's the focus of Expo. Two main advantages of Expo are - over the air updates (OTA) and push notifications. Else there are lot of disadvantages. Expo team just trying to simplify the things and works on the top of react-native.

But if you are familiar with react/react-native ecosystem, you already know that - Expo does not suits to your use case, sometimes. So that's the thing.

🌐
Reddit
reddit.com › r/expo › roadmap for learning react native with expo (coming from react + next.js)
r/expo on Reddit: Roadmap for learning React Native with Expo (coming from React + Next.js)
4 days ago - My current goal: Build a strong mental model of React Native + Expo fundamentals before going deep into libraries and abstractions.
🌐
Reddit
reddit.com › r/reactnative › how easy is it to convert a react native expo application into a website? (i fucked up with a client)
r/reactnative on Reddit: How easy is it to convert a React Native Expo application into a website? (I fucked up with a client)
September 8, 2024 -

Long story short, my client and I used both used the word "app" very differently. He thought I was building a web app, I thought he wanted me to make a mobile app. Now I have a fully built React Native Expo app and he wants a website. Around how much time will it take to convert this to a fully-functional website? From what I could find on the Internet, most of the logic can remain the same and only my visual designs (which are fairly simplistic) have to change. If that's true, how do I go about it? Any help is extremely appreciated as I'm 16 and potentially in some deep shit.

🌐
Reddit
reddit.com › r/expo › should i use expo with react-native or not?
r/expo on Reddit: Should I use expo with React-native or not?
January 5, 2025 -

Hey everyone,

I’m new to React Native development—so far, I’ve been working as a web developer. Now, I’ve joined a startup where we’re building a fintech product, and we’ve decided to use React Native for our frontend.
I’m trying to figure out whether Expo is the right choice or if we should go with bare React Native. I like the idea of Expo’s easy setup, OTA updates, and faster development, but I’ve heard it has limitations, especially when it comes to native modules, app size, and performance.
Since we’re building a fintech app (which might require native features like biometrics, encryption, or background services), would Expo be a good choice? Or would we hit roadblocks that force us to eject later?

Would love to hear your experiences—is Expo good for fintech apps, or should I avoid it?