The moment most people find hardest to believe is the last one. You approve the fifth screen, type "submit it", and a real iOS app goes to Apple under your business name. Here is what actually happens in that gap.
Yours. Quiny submits through your own Apple Developer account, which you connect in Settings before your first submission. Apple's Developer Program costs 99 US dollars a year, and enrolling as a business takes a day or two while Apple checks your company details, so Quiny prompts you to start it while your screens are still being built.
Quiny never publishes under its own team and never acts as the publisher. The app, the listing, the reviews and the customers belong to your account from the first upload. What Quiny asks for is an App Manager role on your team, requested once, shown in full before you approve it, and revocable at any moment from either side.
Before anything is uploaded, Quiny runs one pass over all five screens together. This is a long context step, so it is one of the places Kimi does the work. It checks that the same product has the same price everywhere, that every button goes somewhere, that the app handles no network and an empty basket, and that the text is consistent. It usually finds two or three small things and fixes them before you see the build.
You see all of this before submission and can change any of it in plain English.
Quiny compiles a signed release build and uploads it to App Store Connect. This is the slow part, and it is Apple's slow part: processing usually takes between twenty minutes and an hour. The console shows you where it is, and you can close the laptop.
Apple reviews every app by hand. Apple's own published figure is that 90 percent of submissions are reviewed within 24 hours, and that matches what we see. Some take longer. We cannot speed it up and nobody can.
Guideline 2.1, the app crashed or a feature did not work. Nearly always a reviewer testing checkout with a test card we did not expect. The fix is a better sandbox path and it costs you nothing.
Guideline 5.1.1, asking for data without a reason. Usually an account requirement in a shop where guest checkout would do. Quiny now defaults to guest checkout for this reason, and if you asked for accounts we add the explanation Apple wants.
Guideline 4.2, minimum functionality. Rare, and it happens when an app is a menu with a phone number. Apple wants apps to do something a website cannot. Reordering, notifications and Apple Pay are enough, which is why we push for them.
When a rejection arrives, Quiny reads it, tells you in plain words what Apple said, fixes what it names and resubmits. Resubmissions caused by our build are free. If the issue is with the business itself, for example a product Apple does not allow to be sold in apps, we tell you that plainly too.
Apple sends "Ready for Sale" and the app appears in the store within a few hours. From then on, changes work the same way they always did: describe the change in the console, approve the screen, and Quiny ships an update. Updates go through review too, and they are usually faster.
We load a chat window from Intercom so you can talk to us, and it keeps an identifier in your browser so your conversation follows you between pages. That is the only thing here that is not essential. Decline and the site works the same, without the chat. Read the privacy policy