Know what moving to native will cost before you commit a team to it.
One of three support options from the founder. We run the Pack's assessment on your app, check every finding by hand, and write down what a move to SwiftUI and Jetpack Compose involves. If the honest answer is to stay on React Native, the report says that.
Ask by email at hello@nativestarter.io or with the form below. We agree the scope and terms before any work starts.
- Turnaround
- 5 working days
- Walkthrough
- 45-minute call
- Your team's time
- About 75 minutes
- Other options
- Advisory call or pilot
What is in the report
A written document, usually 15 to 25 pages. Every finding points at a file in your repository, so your engineers can check it.
- 1
Summary and recommendation
Migrate, migrate part of it, or stay on React Native. One paragraph, with the reason.
- 2
Native surface
Every dependency that ships native code, its SwiftUI and Jetpack Compose equivalent, and how hard the swap is.
- 3
Custom native code and patches
Local Expo modules, app extensions, config plugins and patched dependencies you already maintain.
- 4
Screens and navigation
Every route, grouped by the native dependencies it touches.
- 5
Releases and OTA
What your release process loses without over-the-air updates, and what replaces it.
- 6
The hard parts
The five or so things that decide whether this takes a quarter or a year.
- 7
Checkpoint order
Which screens move first, and why that order keeps both apps shippable.
- 8
Brownfield or rewrite
Host remaining React Native screens in a native shell, or rebuild from the running app.
- 9
Effort estimate
Per area and in total, with every assumption written down so you can argue with it.
- 10
Stay on React Native if…
The conditions under which we would tell you not to do this at all.
How the week runs
- 0Day 0
Short scoping call. You grant read access to the repo and share a build.
- 1Day 1–2
Static pass over the codebase with the assess-rn-app skill, then every finding checked by hand.
- 2Day 3
Running the app: flows a static pass misses — push, deep links, background work, purchases.
- 3Day 4
Draft report. Open questions sent to your team the same day.
- 4Day 5
Final report and a 45-minute walkthrough call with whoever will own the decision.
What we need from you
- Read access to the app repository
- A TestFlight or internal-track build
- 30 minutes on day 0 and 45 minutes on day 5
- Someone who can answer questions about the release process
When a report is not worth it
Teams of one to five, where shared code is what lets you ship at all, should probably not migrate. We would rather tell you that in a reply than in a paid report.
Who should stay on React NativeTell us about your app
Use this for a Readiness Report, an advisory call, or to enquire about a Pack licence. Say which in the last box. It takes about two minutes.
What happens next
- 1.You get a reply from the engineer who writes the report within one working day.
- 2.If a report is worth doing, we agree the scope and terms by email. If it isn't, we say so.
- 3.Work starts on day 0, once the scope is agreed.
Prefer email? Write to hello@nativestarter.io.