Forty public projects you can open, fork and reshape with a few sentences.
Browse templatesSeparate client workspaces, white label, and the Git repo handed over at the end of the engagement.
See the programmePaste a URL. In thirty seconds you see exactly what Google receives before any JavaScript runs.
Check a URLThe Android app lives in the same project as the iPhone one. Eqlo writes native screens, tabs, and a signed file for Google Play. You run a closed test before the listing is public. The Play developer account stays in your name. Review stays Google.
What you need before you start is a loop a member will repeat on a small phone: open a tab, see a list that reflows, tap an action, and land on a loading or error state that still reads. Android is a family of widths. A layout that only works on a large flagship will fold on a cheap device. Write the loop in one sentence, and name the smallest phone your members actually carry.
You do not need the account to see the first screens or to test with a QR code. You need it for closed testing and for production. Google bills that account once, not Eqlo. Create it when twelve testers are about to install the build, not the night you type the prompt. The listing, the data-safety form, and the review notes sit on that account.
Play asks what you collect, whether it is required, and whether it is sold. The answers must match the project. Eqlo lists the permissions the app actually calls: camera, location, push, or none. You still own the sentences, because you know what you store. A form copied from another listing is a common first delay.
Apple will review a binary you have mostly tested yourself. Play wants a trail of testers first. The two stores are two programmes.
Google Play expects a closed test before you ask for production. That is not a box you skip. Eqlo gives you a test build you can hand to twelve people. Collect the crashes and the confusing tab there, not after a listing is public.
Play wants a form, not only a privacy policy URL. Fill it from what the app does. Eqlo will not invent a collection you never asked for. If the project never stores an email, do not tick email.
IARC questions sit in the Play Console. Answer them for the audience you actually have. A kids club and a trade tool are not the same form. Apple has an age rating too, but Play is the store that blocks production until this questionnaire is done.
A complete mobile app is about a day of back and forth after the first draft, which lands in two to five minutes. Closed testing is part of that day, not a later surprise.
Open the project, show the QR code, and install the test build on a small phone and on a larger one. The link lasts 24 hours. Tablets can share the phone screens at first. A dedicated tablet layout is a later sentence, not a launch requirement.
Select the element and write the change in English. Each exchange creates a version you can restore. If a list truncates on the small phone, say so in the chat. In-place text edits skip the chat when only a label is wrong.
Signed store builds sit on Plus at $19 a month and on Team at $49, with three and ten seats. Free keeps phone testing only. You upload the file in Play Console, run the closed test, then ask for production. Content updates later do not go back through store review.
Play will usually stop you. Treat twelve testers as part of the build. They find the tab you cannot see on your own phone.
Ticking a collection you do not do, or hiding one you do, both fail. Read the permission list Eqlo shows, then fill the form from that list.
Walk a cheap device before you call it done. If a button falls under the navigation bar, fix it in the project. Device catalog honesty matters: if you drop old Android versions, say so on the listing.
Closed testers need the same courtesy as an Apple reviewer. Leave a demo account. Confirm it still opens after your last correction.
The iPhone path, the five store steps, and the shared app builder take over from here.
It is the same project. Navigation and permissions stay native on each side. You do not maintain two products. You do submit two packages.
Google bills that invoice on its own site. The amount is not an Eqlo fee. You create the account when closed testing is about to start, not on the first evening.
Play will usually stop you. Treat it as part of the build. Testers find the tab you cannot see on your own phone.
Say so. You can ship one store. The project can still grow an iPhone package later without a rewrite.
You do. It sits on your developer account. The code sits in your repository.
Five free projects, a QR test build, no card. Signed builds sit on Plus at $19. Play fees stay with Google.