Freelance Expo developer
Expo has become the serious way to build React Native, and it is my daily tool: apps in production, EAS builds, over-the-air updates, and native modules when the ecosystem is not enough.
Expo, down to native
The strength of Expo is never opening Xcode or Android Studio again. Its limit is the day you need an API the ecosystem does not expose. That is where I come in: I write Expo modules in Swift and Kotlin, publish some as open source on npm, and unified complete native SDKs into one cross-platform Expo module for MWM.
EAS, from build to store
EAS builds, signing, profiles, store submission, OTA updates and runtime-version management: I set up the whole chain, with the rule that matters, knowing what can ship over the air and what requires a store build. Your team keeps a pipeline it understands.
What I do
- Build an Expo app from scratch, with Expo Router and EAS.
- Migrate a bare React Native app to Expo.
- Write native Expo Modules in Swift and Kotlin.
- Set up EAS Build, Submit and Update, with CI/CD.
- Unblock a team stuck on a native problem.
Missions that prove it
Frequent questions
Expo or bare React Native?
Expo, unless there is a precise, documented reason not to. Prebuilds and config plugins now cover almost every case that used to justify bare, and Expo Modules lets you write the missing native code without leaving the ecosystem.
Can an Expo app use native code?
Yes, without restriction. Expo Modules is precisely a modern API for writing clean Swift and Kotlin. It is a large part of my work: native SDKs, iOS Quick Look, modules published on npm.
How long does a migration to Expo take?
For a reasonably sized app, a few days to a few weeks depending on how many native dependencies need replacing or wrapping. I start with a dependency inventory, which yields an honest estimate before writing a single line.
Got a project in mind?
Guaranteed reply within the hour, plus a free thirty-minute video audit.