How to publish an app to the App Store and Google Play
A signed build, a listing, a reviewer login, and a wait you do not own. Eqlo prepares the iOS and Android packages, the icons, and the listing shots. You still open the developer accounts and click Submit. Content updates later skip a new store review.
- 5Steps to a listing
- 24 hQR test link
- $19Plus, signed builds
- 1 dayA complete mobile app
- 01
Open the developer accounts
Apple bills a yearly developer account. Google bills a Play account once. Both invoices stay on their sites. Create them when testers have already used the app, not the night you type the prompt. You will need a legal name, banking, and a contact that can answer review. Eqlo never holds those logins. The accounts stay in the customer name.
- 02
Gather what the stores ask for
A privacy policy URL the reviewer can open. A data-safety form that matches the code. A reviewer login if the project has accounts. Icons, a launch screen, and listing shots in the right sizes. Eqlo generates those assets from the screens the app actually uses. You still write the name, the subtitle, the description, the category, and the age rating.
- 03
Generate the signed file
The project produces an iOS package and an Android package with a version you can bump. Signed store builds sit on Plus at $19 a month and on Team at $49, with three and ten seats. Free keeps the 24-hour QR test. You upload the files in App Store Connect and Play Console. Walk a cold start on a second phone before you pay the queue.
The release panel in the project: a signed iOS file ready to upload, and an Android file waiting on closed testing. - 04
Fill the store listing
Name, subtitle, description, screenshots, category, age. The first line should say what the app does. A paragraph of adjectives is how listings get ignored. Screenshots are the real screens from the build you are sending, not a marketing collage. Privacy text and the Play data-safety form must match the permissions Eqlo listed.
- 05
Go through review
Leave a reviewer login if you have accounts. Answer the questions only you can answer. If review writes back, reply with a fact, not a slogan. Play expects a closed test with real testers before production. When the listing ships, it is yours to update. Eqlo stays the place you change the screens. Content updates do not go back through store review.
How long review takes
Apple often replies in one to three days on a clean binary. A missing login, a broken first launch, or a holiday weekend makes it longer. Google closed testing is yours to run. Production review after that is often shorter than people fear, and still not a date we can swear to. We cannot shorten a queue we do not own. We can stop you submitting a wrapper, a mute login, or a privacy label that does not match the project. A complete mobile app is about a day of back and forth after the first draft. The store wait sits on top of that day.
Google Play closed testing before production
Google Play usually wants real testers on a closed track before production. Plan a handful of people who will install the build you upload, keep the track alive for at least a few days, and only then promote. Eqlo prepares the Android package and the listing shots from the screens testers already used. Team at $49 gives ten seats when a committee shares one workspace. Apple has no equivalent closed-test gate, but a broken first launch still burns one to three review days. Walk both stores on a second phone while the QR link is still valid for 24 hours. Project backups stay for 30 days in the region you picked at creation.
Version numbers and resubmission
Every upload needs a version you can bump. Eqlo labels the iOS and Android packages in the release panel so you know which file matches which build. If review rejects a binary for something we generated, fix it in the project, bump the version, and send again. Content-only changes on the app skip store review. A hotfix that touches navigation or permissions is a new binary and a new wait. Free keeps the 24-hour QR test. Signed store files sit on Plus at $19 and Team at $49.
Related pages
The iPhone page, the Android page, and the shared app builder take over from here.
Frequently asked questions
Does Eqlo submit the app for me?
No. You upload and click Submit on your developer accounts. That is how the listing stays yours, and how review questions reach the person who can answer them.
Can I publish only one store?
Yes. Many teams ship Android first, or iPhone first, because that is where their members are. The other package can wait. The project does not force both.
What if I already have listings?
You can replace the binary on the existing apps. Keep the bundle id and the listing history. A new id is a new app and a new wait.
Who pays Apple and Google?
You do, on their sites. Eqlo does not add a surcharge per submission. If a package fails for something we generated, you fix it in the project and send again.
When should I write the screenshots?
After testers have used the real screens. Screenshots of a week-old build waste a review cycle. Capture them from the build you are actually sending.
Prepare the packages. Keep the listings on your accounts.
Five free projects, a QR test, no card. Signed builds sit on Plus at $19. Store fees stay with Apple and Google.