A first version with login, lists and a simple transaction is often 8–14 weeks of engineering, plus App Store or Play review.
Engineering can reach a testable build while certificates, privacy text and review material are still unfinished. Those sit on the critical path. Plan them, do not write them the week you hoped to publish.
Realtime messaging, media, serious offline field work, or two native codebases with different release trains. Cross-platform helps when the screens are the same. It does not delete store review.
Users, content and order state live on the server. API versions and the operator console are not a later surprise. An app that cannot change config without a binary is already late.
If the audience is already in WeChat in China, a mini program can reach a transaction sooner. An app is for push, offline jobs or store branding. Many companies run both on one API — that is two client calendars, one backend calendar.
It counts as calendar. We schedule review assets with the build. Rejection loops are shorter when privacy and pay are not improvised.
Yes. Keep the API stable so iOS is not a rewrite. Say that in v1 so the estimate is honest.
Store review is extra days to weeks. TestFlight or internal tracks can cover a stakeholder preview while review runs.
List the first jobs in the app and whether both stores are in v1. We will put engineering and review on one calendar at /en/contact/.