Can you take over an existing React Native project?arrow_outward
Yes, and it is a large part of what I do. I start with a read-only audit: dependency and React Native version state, architecture, build reliability and the specific things blocking you. You get that assessment before committing to a build, so you can decide whether to continue the codebase or restart from it.
Do I get both Android and iOS?arrow_outward
Yes. React Native builds both from one codebase, which is most of the reason to use it. Apps still need testing on both platforms separately, and iOS release requires an Apple Developer account in your name, which stays yours.
Will the app work offline?arrow_outward
It can, and for most real products it should. Offline-first means the app keeps working when the network drops and reconciles when it returns. This affects data architecture, so it is a decision made at scoping, not bolted on at the end.
Who owns the code?arrow_outward
You do, in full, including the repository, the store listings and the Firebase project. Everything is set up in accounts you own from the start rather than transferred at the end.
Is React Native fast enough for a production app?arrow_outward
For the overwhelming majority of products, yes — the apps on this site handle realtime navigation, payments and large lists in production. Where a specific feature genuinely needs native performance, React Native lets you write that one piece natively without rewriting the app.
What do you need from me to start?arrow_outward
A description of what the app should do, any designs or references you have, and access to whatever already exists — API docs, a repository, a Figma file. If you have none of these yet, the scoping step produces them.