I Will build your React Native app for Android and iOS, connected to your backend

One codebase for both phones is the main reason startups and small businesses choose React Native. A team that already knows React can ship a native app without maintaining two separate ones, and much of the logic can be shared with a React web front end.

Starter gets you a small app or a first slice: up to three screens with navigation and data from your API, as an Android build you can install. Standard covers up to eight screens, login against your backend, forms and local storage, with Android and iOS builds for testing. On Advanced, you get up to fifteen screens, plus push notifications, offline use for the main screens, and builds ready to submit to Google Play and the App Store.

I test the Android version on a real Android phone. iOS builds are made in the cloud with Expo's build service (EAS) and reach your iPhone through TestFlight, where you test them before anything is submitted. TestFlight runs on your Apple Developer account, so iOS test builds start once that account is in place.

Publishing needs your own developer accounts, Google Play and the Apple Developer Program. A new personal Google Play account has to run a closed test with outside testers before its first public release, so it is worth opening early. The app is published under your name, and the code is yours. For 14 days after delivery, I fix anything that does not work as we agreed, free of charge.

There is no mobile app in my public portfolio yet; the React and TypeScript work you can see there is web. That is why I show a clickable first screen early, and you decide on the direction from a real build.

Everything is agreed in writing, without calls: the screen list comes first, then a written update and a fresh test build as the work moves.

Steps for completing your project
1. Agree the screens - From your idea or design and your API, I write down every screen, what it shows in each state and which calls it makes. Coding starts once you approve that list.
2. First screen early - Navigation, the app shell and one real screen with your data, as a test build, so the direction is checked before the rest is built.
3. The rest of the app - The remaining screens, login and forms, connected to your backend, with loading, empty and error states.
4. Test builds and a review round - Android as an installable file, iOS through TestFlight. You send corrections in one list, and I fix them in the next build.
5. Code and release notes - Your repository gets the code and a note on how to build and release; on Advanced, the store builds are ready to submit from your accounts.