Expo
Expo development
Managed and bare, with EAS Build and EAS Update doing the parts that used to need a Mac and a release.
Part of react native app developmentExpo stopped being the beginner option some years ago and most teams have not updated their opinion. Config plugins reach almost everything the bare workflow reaches, EAS Build produces signed iOS builds without anyone owning a Mac, and EAS Update ships a JavaScript fix the same afternoon instead of three days later.
I use Expo Router where the app benefits from file-based routing and React Navigation directly where it does not. The place I leave the managed workflow is a native dependency no config plugin covers, and because I write Kotlin and Swift that decision is made on the merits rather than on what I can avoid.
What that covers
- Managed and bare workflows, including the migration between them
- EAS Build with credentials held in your organisation, not mine
- EAS Update channels mapped to staging and production
- Config plugins written where an SDK has no Expo support
- Expo Router and React Navigation, chosen per project
Where this has shipped
Next: TypeScript
Tell me what you are building.
A sentence about the product and where it is stuck is enough to start. I answer every mail myself, including the ones where the answer is that I am not the right person.