Hire me
Hire an Expo developer
Managed or bare, EAS Build and EAS Update configured in your organisation, config plugins written where an SDK has none.
Expo is the right default for most React Native products now, and the teams still avoiding it are usually working from an opinion formed in 2019. Config plugins reach nearly everything, EAS Build produces signed iOS builds without anyone owning a Mac, and EAS Update lets a broken screen be fixed the same afternoon.
The value of hiring someone who also writes native code is that the managed-versus-bare decision gets made on the merits. I will keep you in the managed workflow while it is genuinely serving you, and when a native dependency has no plugin I will write the plugin or the module rather than ejecting out of caution.
What that covers
- New Expo applications, managed or bare
- Migration between the managed and bare workflows, in either direction
- EAS Build and EAS Update set up under your account
- Config plugins for SDKs with no Expo support
- Expo Router adoption, or React Navigation where it fits better
I will not recommend the managed workflow for an app that clearly needs native code it cannot reach. The point of Expo is speed, not purity.
How it would be billed
Fixed-price project
A scoped piece of work, quoted after discovery and billed against milestones. Best when you know what you want built.
Monthly retainer
An agreed number of days each month, billed in advance. Best when the work is continuous and the priorities move.
Consulting and audit
A fixed number of days ending in a written document. Best when you need an answer rather than a developer.
Inside your team
A day rate, your process, your standups, your repository. Best when you have a team and need one more senior pair of hands.
Work that backs this
VM Academy
Personal, 2026
A multi-skill learning platform. Three repositories, one API, one database.
How it is built
Kasoti
Personal, 2026
A mock-test app for one exam candidate, built as a real monorepo anyway.
How it is built
Native Ninjas
Personal, 2026
A typed monorepo starting point: Expo, Hono and TanStack Router in one graph.
How it is built
Questions
Should we eject from Expo?
Probably not, and the question is usually a symptom rather than the problem. Most ejection requests I have seen come from one native dependency, and most of those are solvable with a config plugin. Tell me the dependency and I will tell you which it is.
Is Expo production ready?
Yes, and has been for years. The relevant question is whether your specific native requirements are covered, which is a list rather than an opinion.
Can you set up EAS for our existing app?
Yes, and it is a well-bounded piece of work that does not require touching your product code. Credentials go into your Expo organisation, not mine.
Also hiring for a full stack developer?
Still the right person?
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.