13 ms·
Expo – Open-source platform for making universal apps for Android, iOS, and web
- RamblingCTO 3y agoI tried to use it and my immediate block was using a react native plugin I really needed and it wasn't compatible ...
- purplecats 3y agoi used this for my startup years ago, nice to see its still going strong
- no_butterscotch 3y agoAny major issues? I'm considering RN right now. Wondering whether to start from scratch or not. People refer to issues "ejecting" from Expo but those issues are vague and go back years. Any concerns or experiences on your end that make it a good or bad option?
- adamsaparudin 3y agoIf it’s just simple app, I’m sure Expo is still good choice. Otherwise I will prefer use RN
- throwanapple 3y agoThey like to do a lot of breaking changes between versions that are very painful to upgrade to. But this also applies to RN and JS ecosystem to a lesser extent.
- Rohansi 3y agoI believe the situation with this has improved. Before EAS you needed to target one of the more recent SDK versions or you wouldn't be able to build using their services. However, if your app is new (or upgraded) enough to use EAS now then you don't get locked out of building anymore. But still, upgrading SDK versions to stay on top of security/new features can be a burden with how many breaking changes there are.
- Rohansi 3y agoEjecting is no longer required with EAS (Expo Application Services) build. You can bring in your own native dependencies and still use Expo without ejecting. I use it for the Rust (video game) companion app, using the stock libraries bundled within Expo so development is a breeze. https://rust.facepunch.com/companion/ https://rust.facepunch.com/companion/
- jeppester 3y agoIMO the best thing about expo is that your native project folders pretty much becomes build artifacts, and so can be left out of your git repo. That is great because those project folders are usually quite fragile and can easily break over time. Before "prebuild" was introduced, you had to stick to expo-included native modules to get that advantage, and if you didn't, you had to "eject", which was hardly better than not using expo at all. With "prebuild" you can use any native module and still have a git repo free of those fragile iOS and Android folders. It is more work setting up those modules, but it's worth it IMO.
- sideproject 3y agoIs there anything equivalent for Vue? I know there was VueNative and NativeScript and there is even Ionic in Vue, but haven't really seen any framework that is either dedicated to Vue or has a strong support for Vue.
- benatkin 3y agoThe title made me think they were trying to rebrand as not being limited to React Native. I think they are instead trying to market to a wider audience by not mentioning React in their tagline, though.
- conradfr 3y agoIonic with Vue works very well. I was afraid because of the Angular roots but the docs (and typescript support) are top notch for Angular/React/Vue. I could basically transfer all my Vue knowledge (and code).
- joshstrange 3y agoQuasar+Vue (uses Capacitor as well) has worked very well for me. I used Ionic with Angular years ago and I know they support Vue now but their support wasn’t great last I looked (it’s been years, this might have changed). Quasar is Vue-only and benefits from that focus.
- asdev 3y agoworks until you need to use a native library that hasn't been ported for Expo, then you need to eject. I would only consider Expo for POC/MVP
- andridk 3y agoNot true anymore. You can use their build service (EAS) to create app and dev client for custom libraries without ejecting
- jacobp100 3y agoWhat if you need to do configuration in Xcode?
- darcien 3y agoI believe you could do it by writing a config plugin[1] that will apply the desired config changes to the native project files. Expo will apply the config from plugins when they are building the native app for you. (Disclaimer: I use Expo at work for cross-platform app including web but never wrote my own plugins) [1]: https://docs.expo.dev/config-plugins/plugins-and-mods/ https://docs.expo.dev/config-plugins/plugins-and-mods/
- jeppester 3y agoThis was my main criticism as well, but not anymore. With the "prebuild" workflow you can regenerate your iOS and Android projects anytime you need. And set up scripts for adding external libraries in the process. It is more work to set up over just altering the native projects, but the result is rather nice. I've never felt 100% confident that react native project folders wouldn't break for arbitrary reasons. Being able to so easily start over is very useful.
- jameside 3y agoWe also call this idea "continuous native generation". So glad to hear it is working well for you!
- nwithan8 3y agoThat just sounds like React Native with extra steps.
- HelloNurse 3y agoI got rid of Expo in an inherited React Native app, and now I have less dependencies to upgrade and less tools to worry about.
- Cthulhu_ 3y agoIt's RN with less (or I guess different) steps, actually; you can skip the bit where you have to manage and build the native parts of your apps, even though with RN that's already minimal, manageable and works out of the box. generally.
- TDiblik 3y agoTbh, I liked expo, but since you cannot build locally nowdays (you can eject and build, but that won't work 99% of the time, literally didn't work for me on the hello world example), I kinda just threw it in the "cool, but won't use" bucket for time beeing :/, could change in the future, but I don't know how I feel about 3d party service (EAS) building my app and holding my signing certificates (yet)
- wesvance 3y agoYou can build locally without ejecting; just throw the --local flag on the end of your eas build command This does what EAS would do, just on your local machine. If you remove the --local flag, it will send it up to EAS to do the build. eas build --profile develop --platform ios --local
- TDiblik 3y agoyes, you are right, however, AFAIK you still need to be logged + have it linked to eas project (because it uses eas credentials) + this method is planned to be deprecated soon [?] (I'm 100% sure I read stuff like this when researching it like half a year ago, but cannot find it for the love-of-god atm :D, but I would like to be proved otherwise, because the build step is the only thing I disliked about expo long-term wise) ... now looking more into it, I probably mistook `npm run export` / `expo build` with `eas build --local`. Is this correct?
- qazxcvbnm 3y agoI think your commands are kind of muddled. By `npm run export`, I assume you are referring to `expo export`? That is responsible for bundling your app for OTA updates. `expo build` is the deprecated method for building your Expo app with the old ExpoKit native shell app. Only `eas build --local` is the actual command for locally building your app. Perhaps the issue you're thinking about was what I linked to in my other comment? By my own thinking, I believe it's quite unlikely that Expo will ever manage to actually totally remove support for local builds, even though they probably will never encourage it; as otherwise, its really quite impossible to debug native builds, and indeed local builds are Expo's recommendation for debugging such issues. With regular React Native native dependencies now possible in Expo, a dizzying new array of hard to diagnose bugs can now be triggered, and its unlikely Expo is ever going to go back on their support for arbitrary native dependencies.
- wesvance 3y agoI've used Expo going on 3 years now, their development team is incredible. There are very few reasons to use base react-native over Expo anymore; They make upgrades to new RN versions easier, can support any custom native libraries, have an awesome build service (EAS), support OTA updates, their docs are great... I could go on and on. If you're a RN dev and haven't tried out Expo in the past year I highly recommend giving it another go - its not the Expo you remember before their custom dev-client days.
- techterrier 3y agowidgets!
- pests 3y agoI haven't used react native in years. Expo at the time felt like a shitty add-on trying to capture some part of the app development process but I didn't feel it added anything. Sounds like I s gotten a lot better and found an actual usecase. I'll have to check them out again.
- snordgren 3y agoI love these real takes. I had the exact same experience trying to get into React Native and Expo, eventually just decided to write native apps if I ever get into app dev.
- throw14082020 3y agoYea, felt the same but haven't used react native for years either. Some concrete examples: - Generally a poorer developer experience (bugs, bad documentation). - Couldn't use some popular/common react native packages. It needed to be compatible with Expo, and there was an expo specific version to use the camera for example. These would have different (and more) bugs. Trying to use any unsupported packages meant ejecting, a hell that might be similar to ejecting from create react app or using craco, perhaps. - Wasn't really adding much apart from being "all-in-one", but unfortunately each piece was sub par to the original react native. - Unfortunately the react native docs were defaulting to suggest using Expo. They still do that now: https://reactnative.dev/docs/environment-setup https://reactnative.dev/docs/environment-setup. And yet developers often eject from Expo, so you'd rewrite the scaffolding of your app without expo instead of ejecting. IMHO that's quite sad to see the React Native docs still suggests Expo. Side note: I've been using Flutter for a few years now, much better developer experience. Doesn't have code push yet, but https://shorebird.dev/ https://shorebird.dev/ is working on it. (I am not affiliated with them).
- gleenn 3y agoI'm a huge Clojure(script) fan, re-frame is an amazing and super elegant/easy development tool. The awesome this is you can use Clojurescript and Expo together. It was one of the absolutely most pleasant development experiences I've had, especially supporting multiple mobile platforms too. I've also done Android dev and used a Ruby + iOS toolchain before, and done a lot of mobile web. Expo + Clojurescript easily brought the most delightful experience. Interacting with their team was also fantastic, very smart and responsive.
- soks86 3y agoThis is great to hear! I'm not there yet but totally intended to try putting Clojurescript and Expo together. Too many ideas require apps and Clojure is too great not to take with me yet I wouldn't do apps without Expo. Exciting! Thanks for sharing! I'm on re-frame too and that's been a dream. I just wish I had a better UI lib on the (web) frontend. I went with re-com and it feels a bit half-done, though it's working for all my needs so far, I might just sending PRs if it comes to it.
- cha0sg0d 3y agoWe're building a universal app in Svelte, which makes Expo completely unusable. We've had to turn to capacitorjs.com instead, which is less mature but gets the job done.
- mcsniff 3y agoI'll give another vote for Expo, just a happy user here. I wrote and released an iOS and Android app a few years ago and used Expo for ease of cross platform and the hosted build system. I don't use all the fancy OTA updates and what not, but I can definitely recommend Expo as both a beginner to RN and beginner to iOS+Android app dev.
- Ayush_Chaudhary 3y agoIt sounds like browsers for mobile application
- Ayush_Chaudhary 3y agoI sound like browser for mobile apps
- hbcondo714 3y agoExpo 49[1] was released earlier this month which includes network and VSCode debugging which will make life easier. Even though I registered my Expo 48 mobile app[2] with EAS and did Android + iOS builds, I never received an email about this upgrade...glad this is posted on HN! [1] https://blog.expo.dev/expo-sdk-49-c6d398cdf740 https://blog.expo.dev/expo-sdk-49-c6d398cdf740 [2] https://github.com/hbcondo/revenut-web https://github.com/hbcondo/revenut-web
- antigirl 3y agoDeveloping with expo is a breeze. I've been using it for years and have no issues with it. The support from the team and community has been amazing.
- paradite 3y agoI've been using Expo for past 2 years and I enjoyed the experience overall. But make no mistakes that Expo is a SaaS with the ability to inspect some part of the codebase. (I stand corrected here) ~Everything important for building and distribution process is moving to EAS, cloud-based service that is not open-source and cannot be self-hosted. So if want to build your app using your own VPS, you are out of luck (at least for Expo managed workflow).~ Again I'm happy with their service and probably would pay for it when the time comes, but the open-source part is not really the big selling point anymore.
- vladev 3y agoYou can use the `--local` flag to build on your own computer/CI/VPS. `eas build --local -p ios --profile production` can locally build you an iOS bundle. Don't expect it to work out of the box, though. Your machine should have all the XCode tooling correctly installed and configured. Works for Android as well.
- artdigital 3y agoAFAIK using -—local still requires an eas account though.
- qazxcvbnm 3y agoIt does. It's possible to make a patchset that lifts this restriction, though. If you're interested, I'd be willing to make it available.
- benterix 3y agoJust to make sure: if the company goes bankrupt, will I be able to continue releasing updates etc.?
- jameside 3y agoThe Expo Updates protocol is an open standard specified here https://docs.expo.dev/technical-specs/expo-updates-1/ https://docs.expo.dev/technical-specs/expo-updates-1/ The hosted services offered by the Expo team called EAS has an implementation of an updates server that conforms to that protocol. If EAS went away or you wanted not to use EAS, you could write and operate your own server that conforms to the protocol instead.
- RobotToaster 3y agoLooks like it's mostly just a wrapper for a proprietary build SaaS
- Cthulhu_ 3y agoOn the surface, yeah, but a bit deeper it allows a more web-style development flow; you as a developer only deal with the Javascript part, nothing about the native part. Expo is a runtime, whereas React Native / Metro is a full mobile app stack. Likewise, with Expo it's easier to do code push, that is, just release a new JS bundle for over-the-air updates without going through the app store. Again, this is possible in RN as well, but it's a bit more involved. Finally, Expo allows for easier (internal) demos; anyone with the Expo app installed can scan a QR code during your internal demo to install the app over the air, again without having to go through app stores. This can score you points depending on where you work. Personally I'm still convinced 'real' native apps are better, but few companies want to invest in development & developers for that. My experience with React Native (not Expo) has been positive so far though, with very little issues between iOS and Android - actually, for me personally it's mainly been figuring out how to install custom fonts (custom fonts and Font Awesome for icons). I hope to not have to touch that again, lol.
- pzo 3y agoIt's so weird there is no mention of react native in github README, they only mention react. Did anything changed and expo is not based on react-native?
- column 3y agoI use it to create very basic quality-of-life apps coded by ChatGPT. It's great, you can iterate very fast and immediately see the changes on your phone.
- gidis_ 3y agoSo react native in fancy clothes ?
- collaborative 3y agoExpo has an impressive team and investor backing However, making your apps depend on a framework has the following dangers: - the framework might stop being maintained - the vc-backed framework might need to become monetized beyond your means At the end of the day, all these frameworks offer are convenience APIs to easily integrate with native things like push notifications or social sign-ins However, even when these work, they will force you to do things their way, and you won't be able to fully customize your app Learning how to do these things natively in iOS and Android requires extra effort but pays off in the long term. Using frameworks, the time saved in the beginning of your app development journey will be greatly offset by the extra time required to do things like editing framework output in each build towards the end of your journey
- jameside 3y agoThese are a few things I can say as one of the Expo cofounders. We've worked on the Expo framework for over eight years, and did R&D for a year or two before that even before React Native was released. Many other companies and frameworks, even from very large companies, have come and gone in that time and Expo has endured. Paul Graham wrote he found determination "to be the most important quality in startup founders" for what you find that to be worth. Also from the beginning we believed the Expo framework needs to be free and open source. Introspecting as developers ourselves, we thought people would be a lot more likely to try out and recommend open source frameworks and incrementally build up an ecosystem of modules and StackOverflow answers. Expo gives developers much more agency because it is open source. And it is really hard in my opinion to make a business from licensing developer tools, libraries, and frameworks. There are so many free alternatives. The goal of the Expo framework is to be the ultimate way to build universal, native application software. Universal apps have builds for Android, iOS, the web, and future platforms. And the user experience is truly native to each respective platform, often by using the native system UI components and not a replica. It does take significant effort to maintain the Expo SDK's set of convenient APIs. It's also just one part of Expo overall. Separately, the way we are building a business is by offering hosted services for React Native apps, called Expo Application Services (EAS for short). These are optional services for building and updating your apps and using the Expo framework doesn't require EAS. We find developers often use a combination of EAS for some tasks and their own hardware for others. We work to build developer trust. We are a small company but try to serve developers and our customers well, sometimes better than the companies that have endless trunks of money (we've all seen killedbygoogle.com). So, that's some of how we think about things at Expo.
- mrslave 3y agoSlightly off-topic: how practical is it really to build devices (iOS and Android) and web from the same code base? My poor understanding is that React Native, and hence Expo, doesn't use the same CSS frameworks as web development. I'm curious how that works from the same code base, or perhaps that's one of the major difficulties. Also I see Expo as a fancy build framework but it's still fundamentally a RN application. Is this correct? (My front-end colleagues are on another continent and we don't get any water-cooler time. Sorry for the possibly awful questions.)
- qazxcvbnm 3y agoI have never attempted to use the web target of Expo, and probably would never try, not the least because so many dependencies assume that the target of a React Native app is either iOS or Android with the web having such different APIs, and the plethora of alternative options for the web.
- joshstrange 3y agoI’m not using Expo but I do use Capacitor+Quasar to build cross platform apps to great success. I use it for my job and for my side business. Without it I doubt I could run my side business because I just don’t have the time as just 1 person to maintain 3 codebases. I’ve never used Expo, React Native, or Flutter so can’t speak to those but I’m pretty happy with my setup. Yes I have to put a tiny bit of logic behind checks for if I’m on the web or if I’m in an app but it works surprisingly well overall IMHO.
- khromov 3y agoI've used the same codebase for a PWA, iOS and Android app, but using Capacitor instead of Expo. Here is a blog post about the architecture: https://khromov.se/how-i-published-a-gratitude-journaling-app-for-ios-and-android-using-sveltekit-and-capacitor/ https://khromov.se/how-i-published-a-gratitude-journaling-ap...
- theanirudh 3y agoIt has become very practical / doable in the recent year or so. In my experience, if you have lot of frontend web experience, the easiest way to ship a RN app is by using Solito [0]. Also check out Nativewind [1] which allows you to style native apps the same way like you would on web. I was able to ship the first version of our app in about 1.5 weeks with this stack. Also checkout Tamagui [2]. [0] - https://solito.dev https://solito.dev [1] - https://www.nativewind.dev https://www.nativewind.dev [2] - https://tamagui.dev https://tamagui.dev
- r9295 3y agoWithout a doubt, Expo is one of the worst tools I have ever used. 1. I can't get a debug build of the app without using their cloud services. 2. Latest version of Android app to preview Expo apps did not work with latest stable Expo version. 3. Random build errors all the time due to some features being deprecated without being mentioned anywhere. 4. Tries to do too much and breaks quite often
- knlam 3y agoThey improve a lot in the last 2 years, give it another try. The experience nowadays is pretty pleasant compare the plain RN project
- r9295 3y agoThe experience is from my experiments earlier this year
- sirmoveon 3y ago> 4. Tries to do too much and breaks quite often This is the impression I've gotten recently testing their waters. Overall, my take has been to stay away from it unless the app I'm making is simple enough they have templates floating around the web and won't need further tweaking: similar to wordpress, great to have a certain type of app up and running fast but the minute you have to do extensive work on it, you'll wish death on it.
- siquick 3y agoWould it be fair to say that Expo is to RN what Next.js is to React?
- chainwax 3y agoNo I don't think so. Next.js adds a truckload of functionality to React, plus handles the server side, etc. Expo aims to abstract away everything that a web developer wouldn't inherently understand when moving to mobile, i.e. the native stuff. Whether or not it succeeds in that mission, or if it's worth it, is up for debate.
- Alifatisk 3y agoI think it’s a fair comparison in the sense that they are considered meta-frameworks
- jameside 3y agoExpo and Next.js are both React frameworks and Expo also uses React Native. Expo, Next.js: frameworks, React, React Native: libraries.
- explain 3y agoExpo is great. I use it. My primary issue with it is the lack of support for in app purchases (last checked in late 2022). The only easy way to do it is via RevenueCat, as none of the other RN IAP libraries work with Expo. Expo also has built in support for over-the-air updates, which is great. However, it is a paid product, for $5/m per 1000 users (first 1000 free). I believe you can run your own server for OTA updates, but it's fairly obvious that this feature will eventually be removed when they need to monetize harder.
- jameside 3y agoExpo these days is pretty extensible and the option to write your own IAP module is a bit easier with Expo Modules, which let you write custom modules with Kotlin and Swift and set up a config plugin to automate changes to your Android Studio and Xcode projects. It definitely would be good for more IAP modules to provide config plugins and automatically integrate with Expo. The ability to write and run your own update server is a part of Expo Updates and it is not going to be removed. The Expo Updates protocol is an open specification here: https://docs.expo.dev/technical-specs/expo-updates-1/ https://docs.expo.dev/technical-specs/expo-updates-1/. Separately, EAS provides an optional, hosted service that implements the server side of the standard Expo Updates protocol and supports both simple and more advanced deployment patterns, for instance: https://docs.expo.dev/eas-update/deployment-patterns/ https://docs.expo.dev/eas-update/deployment-patterns/. It also integrates with EAS's build service and appeals to teams looking for managed cloud infrastructure.
- pjmq 3y agoI just want to write Svelte and get native apps out the other end. I know we have SvelteNative but that's not great and is a big abstraction. React here is a bit of a bummer i'm not going to lie.
- janjones 3y agoI guess you can use any general "native wrapper over JS/HTML" like https://capacitorjs.com/solution/svelte https://capacitorjs.com/solution/svelte
- jacobp100 3y agoWhy go through that many hoops just to use Svelte over React? They’re so similar, just go with the one with the best bindings to the native platform
- whiddershins 3y agoI don’t agree they are “so similar”
- zodester 3y agoThis sounds like the inevitable slow death of RN to me. Web developers simply moving on to new tech that's better/more common on the web while RN languishes as the massive set of open source libraries required are abandoned
- gr__or 3y agoDon't confuse HN bleeding edge hipser tech with the real world. The world of react-alternatives is fragmented and lib-incomplete, React still gets more installed than its most popular rivals combined[1]. I have worked across these frameworks and React is the only one where I find the lib ecosystem satisfiyingly large (and still growing most steadily). [1] https://npmtrends.com/@angular/core-vs-react-vs-solid-js-vs-svelte-vs-vue https://npmtrends.com/@angular/core-vs-react-vs-solid-js-vs-...
- LeoNatan25 3y agoI used to maintain Detox for iOS when I was at Wix, from 2017 to 2021. We ended up dropping support for Expo for plenty of reasons, some technical, some "political". The people reporting "issues" (more like asking questions) for their Expo apps, usually had very little technical understanding of any of the increasingly thick environment stack (the Expo layer, RN layer, UI framework layer, OS layer). They were basically web developers who were trying to emulate developing for the browser, with zero interest (and often, capacity) in learning any of the complexities of the aforementioned complex environment. It was our experience the expo layer added a lot of complexity and many bugs, with very little ability of users to actually fix anything without "ejecting" their project away from that ecosystem. That was on top of the RN layer, which in itself was full of bugs. We would send users to report expo bugs to the expo team, and were first met by "just fix it on your end, you are detox!" type of comments from that silly community, and those that did report the issues, saw no reaction from the expo team, despite detox being one of the most popular testing frameworks in the RN world at the time (no idea about now, but back then, even Facebook was using detox to test RN itself). At the end of the day, we decided the hassle was not worth the low quality user benefit, so we decided to drop support for Expo. It was one of the best bureaucratic decisions we ever made.
- DanielHB 3y agoExpo was really lackluster when I last worked with react native around 2018/2019. I hear it has gotten much, much better now but I haven't tried lately
- zwily 3y agoIt has. I built an app using Expo several years ago and recently had to update it. Upgrading expo was a pain (as it always is) but the changes and additions in the latest version made so many things easier. And with custom clients, you can do a lot more now than you could before without ejecting.
- jamonholmgren 3y agoIt's the best way to build React Native apps, with very few exceptions, these days. (I have been building RN apps of all types since it came out in 2015.)
- josefrichter 3y agoAs a designer specialising in mobile apps, I have to say nothing still comes close to native codebase experience. Expo & RN is fantastic for MVP (and I've been a super early adopter of RN back in ~2014). But once you start building anything serious, you will very quickly start hitting the walls. As an example, some time ago, it was impossible to implement those iOS large headers that shrink to small once you start scrolling. Even though they were de facto standard in iOS for years already. Also the heavy layering of modals introduced in mostly in iOS 15 were basically impossible. Plus they heavily rely on subtle transitions like the 2nd layer scaling down, moving back and top edge peeking out at the top, so that the user gets a hint where they are in the hierarchy... Not sure if all this stuff works now, but generally Expo & RN were very slow to catch up with iOS and you had to rely a lot on dubious libraries, ending up with messy patchwork. All these minor details are extremely palpable, even by standard users, and the experience just always feels a bit off.
- jacobp100 3y agoIt’s possible to do all this stuff in RN - you just need good native bindings to the features Stuff like the iOS 13 page sheet modals being broken is still an issue - but there’s a set of present/dismiss callbacks in the modal manager you can override in your code to fix it Not sure if you meant page sheet controllers for iOS 15 (the ones that let you pin it half way up). There have been implementations of this, but they all suffered from a kind of crappy animation when you overstretched the page past its allowed limits. iOS would normally force a layout, then animate between the last layout and the new layout. But since RN’s layout is asynchronous, iOS couldn’t perform the animation and it looked sloppy
- qazxcvbnm 3y agoIf asynchronous layout were the culprit, presumably that's the precise type of issue that react-native-reanimated solves? It seems to me that the experiences created via react-native-reanimated run quite smoothly indeed. Of course, the developer still has to reimplement interactions otherwise provided by iOS etc, but React Native should not be a reason for things like sloppy interactions.
- StockHuman 3y agoI’ve very much enjoyed their libraries (though not their monorepo changelogs) in building our RN app. Seems like from the comments the situation we found ourselves in where “bare” react-native was the only option is the best way to interact with the ecosystem from the outset.
- afavour 3y agoI’m primarily a web developer that’s long been interested in native mobile environments and after trying out many of these cross platform frameworks (all the way back to Appcelerator for those who remember!) my conclusion always ends up that they’re almost always a bad idea. The experience is inferior to native, it’s full of compromises to make cross platform work and you’re at the mercy of a company standing between you and the underlying mobile OS. My advice these days is to go in one of two directions: - make a progressive web app. No, it’s not a native experience. But if your priority is cross platform then this is cross platform. Service Workers etc make it a ton more paletable than it was back in the day. - make native UI and code your business logic in some kind of shared layer (Rust, Go, Kotlin Multiplatform). Native UI has come a long way too, as someone who speaks webdev I find SwiftUI and Jetpack Compose to be very grokkable compared to their predecessors, a lot like React if you squint a little.
- kaypro 3y agoI remember Appcelerator. In fact I'm still using it to this day. The core Titanium is now open source and the Apps are "true" native. Give them another look and you may be surprised: https://titaniumsdk.com https://titaniumsdk.com
- xctr94 3y agoAfter 4 years of doing cross-platform mobile, I loathe React and React Native by now, and I dislike Expo. But… suggesting any other alternative is tricky. True native development is, indeed, much better. But a small team will be hard-pressed for doing good work on both platforms, especially once you start fiddling with more important APIs. Configuration and getting your system to compile things to properly is almost a job in itself. Sigh. KMM, Flutter, and MAUI are all promising, but with different trade-offs. So we’re stuck with RN/Expo… At least Expo promises some stability between upgrades, by handling the package compatibility checks for you. Well, when it works. “Make a progressive web app”: yes, that might be the way to go; provided you can get the users to ‘install’ it on their devices. For some companies that’s not optional due to different pressures (e.g. teachers would expect students to have our app installed on their phones). Neither of these 2 solutions is that simple. There are trade-offs involved, and each team must compromise where they can/are weaker. All in all, if you MUST do RN, at least Expo saves you a lot of headaches with config/build/compatibility. It’s mediocre, but worlds better than pure RN (at least for me).
- NayamAmarshe 3y agoI tried this a few weeks ago and their 'create-expo-app' package was broken because of incompatible dependencies. My project died before it could even start.
- Euphorbium 3y agoEveryone loves lowest common denominator.
- chainwax 3y agoMy company is moving our app to React Native and evaluated Expo as an option. Our conclusion was that we needed some of the features that using Expo doesn't let you use (a lot of native modules, as we're not rewriting 100% of the app all at once). Additionally, I think RN has come a really long way from where it was when Expo first came about. Expo sought to smooth over a lot of rough edges, some of which no longer exist. I think Expo realizes this as well, as their main revenue generator is now their deployment tools. The framework is opinionated toward using those paid services, which my org doesn't want to use as we already have processes for building and deploying, which makes working with it cumbersome. https://expo.dev/pricing https://expo.dev/pricing
- jameside 3y agoExpo supports custom native code including your existing modules. It is a much smaller step to start using Expo if you are already using React Native. Using Expo without EAS, the paid services, is definitely supported. The Expo framework is free and open source and is designed to be generally decoupled from EAS. "npx expo prebuild:{android,ios}" will generate "android" and "ios" directories that can be built with existing build processes. Expo: free and open source framework. Includes Expo CLI, Expo Modules, Config Plugins, Expo Router, debugging tools. EAS: hosted paid services. Includes builds, submissions, updates, credentials. Works with any React Native project whether or not it is using Expo.
- Zelphyr 3y agoI've seen so many projects like this come and go. They go, in my opinion, for a reason: Web technologies just aren't great as an app platform. If you want a web-like platform on which to build a cross-platform application, I recommend Flutter. It's not perfect but, it's better than all the other alternatives I've tried.
- mikecoles 3y agoIf you fancy Go, there's Fyne. I don't work in the space so I cannot judge it. https://github.com/fyne-io/fyne https://github.com/fyne-io/fyne
- rubicon33 3y agoI see a lot of comments bashing cross platform mobile development. By and large, I agree but there is one very important caveat: RN is amazing for the business, especially small businesses. Yes it’s full of quirks and yes it’s never perfect but if you’re a small to medium size business trying to get your app to market as cheaply as possible, there is no better option than RN right now. Maybe flutter.
- wslh 3y agoA few years ago our main concern with Expo was about security, man-in-the-middle kind of attacks because you are hardly depending on a third-party, has anything change to robust this? I understand that to general apps Expo could he a dream.
- jameside 3y agoThe Expo framework runs entirely on the end user's device. It's client-side software and I don't think MiTM attacks are the main part of the threat model. Like with most open source you may want to vet the supply chain and the code you include in your apps but Expo has been maintained for over seven years now and is generally trusted in this way in my experience.
- realPubkey 3y agoWith expo on android you are forced to use a 3 years old version of SQLite which is just painful. They just refuse to update it. https://expo.canny.io/feature-requests/p/expo-sqlite-ship-newer-sqlite3-version-on-android https://expo.canny.io/feature-requests/p/expo-sqlite-ship-ne...
- jameside 3y agoThis is actively being worked on. Also a big area of investment over the past couple of years has been adding support for custom native code to Expo and the Expo Modules spec. It is easier in several ways now to write your own module when an existing one doesn't work for you.
- thorben84 3y agoExpo and EAS is my preferred choice for building a new product these days. I was focused on native Android development (Java/Kotlin) for many years. React Native (I first used in late 2016) and Expo (I first used it in production in early 2020) have matured so much over the last years and all the Expo tooling is a game changer for building (cross platform) apps. A few examples of how Expo has changed the game: - The Expo Go or Expo dev client make it possible to no longer need XCode or Android Studio during development and thus make it much easier to bring engineers onto a project who do not necessarily have mobile dev experience. The dev client can be built locally by one engineer and shared with the team or can be built in the cloud with EAS Build. - Upgrades in bare React Native projects used to be painful and time consuming. With Expo prebuild, one can (re-)generate the native projects at any time including after upgrading to the latest RN/Expo versions. Further this allows having to never source control the iOS/Android folders. - Expo config plugins have made it possible (and really straightforward) to apply modification to the XCode/AS projects such as adding permissions or adding extensions. Requiring modifications to the XCode/AS projects used to be a reason for having to use bare RN / eject from Expo. - The Expo Modules API has made it really simple to create a library project and allows for writing the native code in Swift/Kotlin. Setting up and maintaining a RN library used to be a lot more involved especially if it was small and not touched very often. - The entire Expo EAS offering basically provides you with what normally a mobile ops time would provide - builds in the cloud, app store submission and ota updating. For anyone who has set this up with Buildkite/App Center/CI tool knows how much time this could cost / take. And these are just a few things that are top of mind. It is my experience that using Expo + dev client, allows me to bring together a team from all backgrounds (iOS, Android, web, backend) and quickly get everyone up and running, contributing and have impact. The first product I built with Expo was HowWeFeel (April 2020) and with a small team we shipped the initial version iOS, Android and web in less than two weeks. The most recent product is Pinterest TV Studio and because of Expo/RN it is feasible for us to have it not only available for iOS but also Android. I'm excited for the future of Expo and curious what will drop during launch party (August 8th).
- jameside 3y agoSometimes I tell people the best Expo apps have custom native code and it is a really useful skill to know Kotlin and Swift in addition to React and JavaScript. Glad to hear you have found Expo and EAS so useful! One of the features we'll be previewing during launch week is something Pinterest has been needing for a long time, and we'll make sure you hear about it.
- robin_heinze 3y agoI work for Infinite Red (leading RN consultancy), and we have really bought into Expo in full force in the past year or so. The addition of EAS, and prebuild with config plugins has completely changed the game and for us and all but eliminated the need to ever do bare workflow anymore. Things we love about the expo ecosystem - React Native upgrades are much less painful if you use prebuild. Upgrading the expo SDK takes care of most things for you - EAS makes distributing and managing certs incredibly easy - Most expo packages (like expo-camera, etc) are some of the best out there and very well documented and supported - The Expo team is incredibly talented and always willing to help if issues arise.
- jameside 3y agoInfinite Red has been a great partner for Expo. Thank you!
- blackICE91 3y agoI think there is a lot of confusion around what Expo provides. You certainly don’t have to be using their managed workflow to take advantage of the platform. I’ve used Expo modules and services at both Tesla and SpaceX for building large scale apps. I’ve consistently found that their modules are some of the best maintained in the ecosystem. One of the biggest technical risks we face is building a feature around a module that is later abandoned. Using Expo, we don’t really have to worry about this. Web support is also a huge plus (web support in other RN packages is hit or miss).
- frankcalise 3y agoI also work for Infinite Red (leading RN consultancy) for the past year, help maintain Ignite boilerplate and also have used Expo since diving into React Native back in 2018-19. Even during the early days of Expo, it served me well across 3 startups to quickly get our app running on both Android and iOS. Now that it's more mature, the possibilities are endless. There are no snags or scenarios that you can no longer accomplish. For everyone that tried it in the past and has been reluctant due to the "old Expo" of the ejection days, you definitely need to give it another try. In the industry we're in, we all know technology changes rapidly, so to not adjust your mental model after 5 years have gone by is doing yourself a disservice for sure. The RN template upgrades are painless. It enables you to develop on any operating system, which is a big forgotten perk. You can build in the cloud if you want, but you can also build locally (via EAS or the RN cli, this is important Expo apps are RN apps and vice-versa). Need to drop into Native code? You can do that very easily now. It's not a show stopper. Need to whip up a quick demo app for a presentation? It works there too. Oh yeah, do you find the app store dashboards painful? Send it over with EAS Submit all via CLI. You can even set this up in your CI if you want. Preview PRs on release channels via EAS Updates, also amazing. Your QA will love testing features in isolation. Your management will love having the product testable on their devices and you won't get bogged down when they want to see the latest and greatest for some demo you don't need to be bothered with. The team is made up of incredible, hardworking people who want the best for the native application scene. They want the best for your development team. And that's awesome!