Who opens the app first, what the API must keep compatible, then prototype, build, test on devices and submit to stores.
Employee check-in, customer reorder and a channel catalog are three apps. Offline, push and listing are the usual reasons to leave the browser. Write the first job before you pick a framework.
Old builds stay in the wild. Design versions, auth and audit so a forced update is a last resort, not the weekly plan.
Permissions, empty states, payment failure and expired sessions. Pretty happy-path screens do not survive store users.
Test on the hardware you will support. Then submit with privacy and pay material already written. The operator console ships with the client — it is not a sequel.
Visual design can overlap build. Store accounts, merchant IDs and privacy text should start early; they block publish.
On devices and on the API, including an old build. Web-only QA is how field apps fail on day one.
Small copy can wait. Permission or pay changes often mean another review. We put that in the release note, not in a surprise.
Write the first-minute job and the API you already have. We will turn that into a sequenced build at /en/app/.