The app was finished on Thursday. Apple let it in the following Wednesday.

Thursday, 11:40 p.m. The founder sends the link to two friends and then to me, and writes: "it works." It does. Sign up, add a thing, edit it, delete it, log out, log back in. No errors. Nine days of work, and the product is real.

The next morning he tries to give it to the world. That is when the week begins.

Not the coding week. The other one. The one nobody puts in a plan, because none of it appears in any tutorial about building an app: two accounts that must approve you, a company number that may not exist yet, a domain that needs to prove it is allowed to send email, a page of legal text that a store will not accept as "coming soon", and a reviewer in another timezone who has ten minutes and no way to receive your text message.

Here is what actually happened between "it works" and "anyone can install it", in the order it hurt.

The number that takes a month

He wanted to publish under his company. That means an organization account, and Apple asks for a D-U-N-S number before it will even talk to you. Getting one is free. Getting one is also, in the worst case, a few weeks — a company registered four months ago may simply not be in the database yet, and there is nothing to do but wait and re-request.

He had registered as an individual instead, which is faster, and then discovered the second half: on Google Play, a personal developer account created these days cannot go straight to production. It has to run a closed test for a stretch of days with a minimum number of testers who actually install it. Twelve people who will reply to a message, install a build, open it, and stay installed.

So the honest arithmetic of a "five-day app" is this: the app is five days. The launch is longer, and it started before the app did — or it did not start at all, and now you are waiting.

The domain that cannot send email

The app has a password reset. It sends from [email protected]. It arrives in spam, or does not arrive, because the domain has no mail records telling the world it is allowed to send. Then, the first time a real customer says "I never got the reset link", you have lost something that is much harder to buy back than the fix: their trust in the product.

Ninety minutes of work. Two DNS records and a test message to a Gmail address. But only if you know it exists — and the version of the app that "works" on your laptop sends mail from a sandbox that never had to be trusted by anyone.

The reviewer who cannot log in

The store rejects apps with a locked front door, and the reason is almost never "the app is bad". It is a demo account that expired, an OTP screen, a login that only works in Korea, or a reviewer hitting the paywall on step one and stopping there.

What has to exist before you submit: an account that works with an email and a password and nothing else, seeded with enough data that the screens are not empty, and a note that says which button is the one to press. It takes an hour to prepare and it is the difference between a launch and a rejection notice with a screenshot.

The money goes through the store first

Both stores keep a share, hold payment, and want identity and banking details verified before the first payout. That is a second approval queue — one that is completely separate from the app, and one that is much easier on the spirit when you start it on day one instead of the day you have 400 users and no way to take their money.

Nothing here is code

That is the part that surprised him. Every single thing that blocked the launch was paperwork, an inbox, a DNS panel, or a stranger on a review team. The code was finished on Thursday. The code was the easy part.

This is also why I can say "three to five days" without lying. The build is genuinely short when the brief is clear and the scope is finished rather than invented. But the launch is only short if those parallel tracks — developer account, company number, domain email, legal page, test build, payout verification — are opened on the first morning, while the first screen is still an empty box.

On the projects I finish, that is day one, not day five. By the time the last screen is polished, the store is waiting for us instead of us waiting for the store.

If you are the one holding the idea

You do not need to learn any of this. You need someone who has done it enough times to know that the D-U-N-S request goes out on Monday morning, that the closed test has to be populated with real people, and that the reset email has to be tested from a stranger's inbox before the first customer ever sees it.

That is the job. Not just writing the app — getting it in front of a person who is allowed to install it.

If you have an idea and no developer, or a project sitting at 80% that nobody can finish: 3 to 5 days to a working, installable product is a real offer, not a slogan.

Contact: [email protected]
Studio (English): https://cpcai-studio.netlify.app/en/

Send one paragraph. You will get a straight answer about whether it fits in five days, and what it costs — a fixed price before anything starts, not an hourly meter.