Expo Blog

Some thoughts: - RN is a good place to start if you have React experience. The instant feedback via hot-reloading for UI is quite nice and makes learning fun. Maintenance can be an issue but it's gotten better over the years. Expo is a really great platform, and using Expo helps avoid many maintenance issues as well as helps you stay in JS land (including avoiding Xcode). RN will give you cross-platform out-of-the-box while also increasing exposure to platform-specific issues. In my experience, RN works well a lot of the time but then sometimes you need to deep dive on some tricky issue, which may require native code or a hack. - Swift is a nice language that'll be most performant + provide the most-true-to-platform iOS UX and there's a lot of nice online resources for learning native iOS. It's a bit tricky right now because there are two native iOS UI frameworks (UIKit, SwiftUI). SwiftUI is the newer approach to iOS dev but you still need to use/interface with UIKit for some things. I'm finding SwiftUI pretty great these days, especially because it allows for Live Previews of UI (similar to RN's live reload); again, this live code<->preview link helps make learning fun. Xcode is a bit of a beast but it's not so bad imo especially for if you aren't on a huge dev team/project. - I haven't used Flutter much so skipping discussion of that. - RN vs native can be a divisive issue for a variety of reasons. Both have pros/cons and you can learn a lot from them. - The best way…

This one?? https://expo.dev/ Our code broke It looks like there was an error we need to look at. Sorry about the inconvenience.

Yeah, and according to https://expo.dev/blog/precompiled-react-native-for-ios and linked https://github.com/react-native-community/discussions-and-proposals/is… it seems moving off CocoaPods has barely moved past planning stage. Latest update from two weeks ago links to https://github.com/facebook/react-native/pull/52909 and says it’s very very experimental. Just great…

Thats neat. It makes me think of expo [0] that does it in the same way, pretty useful to try stuff quickly, but forces to go though their servers. [0] https://expo.dev/

There’s this https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blazor And to a lesser extent this: https://expo.dev/ (It won’t target games consoles or non-headless edge devices, that I know of).

It's 'expo', right? https://expo.dev/ Haven't looked at this stack. Thanks for the suggestion.

I'm sure some web-to-native workflows are documented just by popular demand. Like this React Native + Expo review posted recently: https://expo.dev/blog/from-web-to-native-with-react-native-and-expo But for an absolutely minimal native example, I followed this guide: https://czak.pl/2016/01/13/minimal-android-project.html with a few adjustments and got an app to compile.

Would you rather work in the React and Typescript you know leveraging all that experience with a rapidly maturing platform (check out https://expo.dev/ for instance.)? Or a framework few others use written in a language Google is likely to drop support for randomly? React Native is the easy choice for me.

>The first question that popped into my head when I saw this headline was: Is React Native still a hot mess? Expo [0] is what really makes things painless now. There's no more struggling with native binary dependency hell. And the entire App store submission process is completely managed; building, signing, uploading, and pushing a new version from your machine to Apple is just a single CLI command. [0] https://expo.dev/ https://dev.to/mauro_codes/expo-101-building-mobile-apps-in-weeks-not-…

Not at all. I use Expo tho :P https://expo.dev/

What a weird comment, anybody can see the pricing on Expo's website, sure there is a free plan but you are almost certainly going to end up paying it's "optional" like so many open core projects these days that deliver a rough free version with issues (https://github.com/expo/expo/issues?q=is%3Aissue%20state%3Aopen%20buil… that naturally pulls developers into their paid plan you keep avoiding my question, what is your relationship with Expo? https://expo.dev/pricing

I get where you're coming from but React Native(RN) is a bad example. RN is actually native and uses native components. So any native view will be supported, including Liquid Glass. e.g. https://expo.dev/changelog/sdk-54-beta#ios-26-and-liquid-glass or https://github.com/callstack/liquid-glass

Cool stuff, especially spiderfier. What's your opinion of expo-maps? https://expo.dev/blog/introducing-expo-maps-a-modern-maps-api-for-expo…

As are we :) btw checkout LiveStore if you haven’t already: https://expo.dev/blog/local-first-application-development-with-livesto… It’s not fully released yet but it is now open to GitHub sponsors and it’s very cool.

My 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

Expo released their support web (still in beta) at the start of the month, bringing react native + API extensions to iOS/Android + web. https://blog.expo.io/expo-sdk-v33-0-0-is-now-available-52d1c99dfe4c Ignoring the user interface, having a single JS codebase for APIs, business logic and unit tests is pretty darn exciting IMO, especially with typescript support.

Apple can update the guidelines anytime, sometimes forcing you to drop some features. Expo's iOS client had to drop QR code reading: https://blog.expo.io/upcoming-limitations-to-ios-expo-client-8076d01ae…

oops -- i fixed the medium link. thanks for the heads up. here it is: https://blog.expo.io/introducing-expo-ar-mobile-augmented-reality-with…

For anyone missing context, naming is hard. https://blog.expo.io/expo-sketch-expo-snack-a444f8dec72b

If you're talking about Exponent, this the same company. They rebranded recently, see https://blog.expo.io/exponent-expo-b172fb6725a7?gi=922dca1bc9bd#.mcnq2…

Hello! The examples use a navigation library that is implemented entirely in JavaScript and it does not currently aim for 100% accuracy for platform gestures and animations. Pure JS navigation is a work in progress with React Native but, in my eyes, it's the ideal end-state (see a post I wrote here for more info: https://blog.expo.io/good-practices-why-you-should-use-javascript-when… but to get there we need some more powerful low level primitives such as a better gesture API. If you prefer to trade-off customizability for platform-specific animations, you can use NavigatorIOS with Expo/CRNA - https://facebook.github.io/react-native/docs/navigatorios.html. If you eject, you can use a library like react-native-navigation (https://github.com/wix/react-native-navigation) which bridges the native navigation APIs, or an upcoming library from Airbnb which they use in their app. Also, I'm curious which examples stood out to you. The "Growler Prowler" app intentionally pushes a screen on top without sharing a navbar, even though this is possible, because this works better for the detail screen. See the beautiful PocketCasts app (https://www.shiftyjelly.com/pocketcasts/) for the design inspiration there. Hope that helps!