Product
Does the core journey work for someone who has never seen it?
For founders a few weeks from launch
Find what will break
before your customers do.
Concrete checks across your product, data, ownership, app stores and launch week. You get a launch report with what to fix, how to fix it and how long it takes.
Five areas where launches go wrong.
Each check is a plain question you can answer without reading code. If you're not sure, say so. Your report shows exactly how to find out.
Data & security
Is customer data separated, backed up and locked to the right user?
Ownership
Do you, not your developer, control the code and every account?
App stores & legal
Which submission requirements still need evidence?
Launch week
Will you know when it breaks, and who will fix it?
Rules founders find out too late.
Some launch blockers have nothing to do with how good your app is. Here are three the check covers.
Google Play
New personal accounts can't publish straight away.
They need 12 testers opted in to a closed test for 14 days in a row first. Founders often find this out in launch week.
App Store
No in-app account deletion means rejection.
If users can create an account, Apple requires them to be able to delete it from inside the app. Google Play has a similar rule.
Your data
A backup you've never restored is a hope, not a backup.
Restoring once, before launch, is the only way to know your customers' data can come back.
Written by people who ship apps
We've taken apps through these checks ourselves.
Arahita Labs builds and launches web and mobile products, including Petrosia, a pet-care community app published on Google Play. These checks come from that work.
If your app is ready, the report says so. If it isn't, it shows how to fix each gap yourself. You don't need to hire us to use it.
See Petrosia on Google PlayQuestions founders ask
What will I actually get?
A launch report on the page, with no signup. Every gap is listed with why it matters, step-by-step fixes, typical effort and whether you can do it yourself or need your developer. Anything you weren't sure about comes with a simple way to check. You can download the report or email it to yourself to forward to your developer.
Will this just tell me to hire Arahita?
No. If your app is ready, the report says so. If it isn't, it shows how to fix each gap yourself. Arahita Labs builds and launches apps, and a free call is offered if you want a second opinion, but you don't need us to use the report.
My app was built by an agency or freelancer. Can I still use this?
Yes, that's one of the most common cases. Choose “Not sure” whenever you don't know, and your report will show how to confirm it, often with a question you can send your developer word for word. Ownership of your code and accounts is the check most worth getting right in this situation.
What counts as a blocker?
Anything that would hurt real customers or block app store approval: a core journey that doesn't work end to end, unsafe or unbacked-up customer data, a developer controlling your accounts, missing privacy policy or account deletion, untested payments, or nobody available to fix critical bugs. Any blocker keeps your result out of the “ready” band, however high the score.
How is the score calculated?
Each check is weighted by how much damage it does if it's missing. “Yes” scores full marks, “Partly” half, “Not sure” a quarter and “No” zero. The score is a summary; the list of fixes is what matters. It's based on your answers, not an inspection of your code.
Are the App Store and Google Play rules up to date?
They reflect Apple's and Google's published policies when this check was last reviewed, including in-app account deletion and Google Play's closed-testing rule for new personal accounts. Store policies change, so check the current guidelines before you submit.