Create, edit and publish, then run your website and your app from their own dashboard. Every feature shown in real screenshots.
See the features
A Next.js project in React and TypeScript, sent to your GitHub repository. A spec change made in the repository comes back to Eqlo.
See the developer page
Paste a URL. In thirty seconds you see exactly what Google receives before any JavaScript runs.
Check a URLTo build an Android app without coding, you describe it in one sentence and Eqlo creates the app, its pages and its tab bar. A QR code puts it on your phone for testing, then, on the Plus plan, Eqlo signs the build and uploads it to the Google Play internal testing track. The Data safety declaration is generated from the permissions you declare, and this page explains the closed test Google may ask for.
Android devices vary far more than Apple's. The same page has to stay readable on a five-inch budget phone and on a tablet, with a larger system font, and sometimes on a folding screen that opens to twice the width.
In the store, the app shows your published Eqlo site inside a native shell. Those pages are built to adapt to the width of the screen, and every change to the product is tested so that no phone ever needs to scroll sideways. Contrast is corrected automatically, and the mobile menu works with a screen reader.
Your part is to look at the result on two very different phones, one small and one large, before you submit. The reviewer will use a device you do not own.
Google Play requires a Data safety section on every listing: what the app collects, whether it shares it, whether data is encrypted in transit, and whether users can request deletion. The answers are public and you are accountable for them.
In Eqlo, you declare the permissions the app needs, each with a reason: camera, photos, location, microphone and so on. The Data safety declaration is generated from that list, along with the Android declaration file, and a consistency check flags any gap. You still read it and correct it, but you do not start from a blank form.
The two stores do not ask for the same things. Here are the three requirements specific to Google, the ones that block first publications most often.
Google Play asks a new personal publisher to have the app tested by a group of real people before allowing public release. It is not optional and cannot be made up later, so plan it from day one. The next section covers it in full.
Where Apple asks for labels, Google asks for a detailed form, with the type of data, its purpose, whether it is shared and whether it can be deleted. A wrong answer can get the listing pulled, even after publication.
In the Play Console, you answer a questionnaire about the content of the app: violence, purchases, user interaction, user-generated content. The answers set the rating shown on the listing, and a rating that does not match the app is grounds for removal.
This is the number one obstacle for new Android publishers, and it nearly always comes as a surprise. Google asks a recently created personal developer account to have the app tested before granting public release. Rule checked in September 2026, worth confirming in the Google Play Console, because Google changes it.
How it works: you move the app to a closed testing track, enrol testers by their Google address, and that group must stay enrolled without a break for the required period. Google then asks you a few questions about what the test showed before opening production.
| Point | What Google Play asks for |
|---|---|
| Who it applies to | recently created personal developer accounts |
| Who it does not | organisation accounts, depending on the account type opened |
| Number of testers | 12, enrolled and opted in |
| Continuous duration | 14 days without a break |
| What you supply afterwards | answers about what the test revealed |
| What invalidates the test | a tester opting out and dropping the group below 12 |
The usual trap: recruiting exactly twelve testers, losing two after five days, and finding at the end that the count has restarted. Aim for fifteen to twenty people, and check the list in the console every week.
Where Eqlo helps here: the QR code test link works before and during the closed test, with no Google account, so you can put the app in your future testers' hands and fix pages before the clock starts. When you change the app's name, icon or permissions, you raise the version number in Eqlo and run a new signed build.
These fees do not go to Eqlo. They go straight to Google, and they apply whatever tool you use. Amounts checked in September 2026, worth confirming in the Google Play Console.
| Item | Amount | When |
|---|---|---|
| Google Play developer account | $25 once | on opening, never renewed |
| Closed testing | $0 | but it costs time and testers |
| QR code testing with Eqlo | $0 | before any developer account |
| Signed Android build with Eqlo | $19 per month | Plus plan |
| Google commission on your sales | none | if you charge through Stripe on your site |
Next to Apple, Google costs less but takes longer. Twenty-five dollars once instead of ninety-nine a year, but a mandatory closed test on new personal accounts and a review that often takes several days. Start the Android track first if you want both stores to go live on the same day.
Eqlo creates a test link that lasts 24 hours, can be revoked and counts how many times it is opened. You scan it with your camera and the app opens on your phone, with no Google account needed. It is the easiest way to put the app in front of the people who will later be your closed testers.
Select a page and write what should change. Every request saves a version you can restore. Use this stage to check the app on at least two screen sizes, since that is where Android-specific problems show up.
On Plus and Team, you connect your Google Play service account, which is verified and stored encrypted. Eqlo compiles the signed build with live progress and uploads it to the internal testing track. From there, you move it to the closed test and then to production in the Play Console.
Four reasons come up on first Android apps. The first is by far the most expensive, because it costs you two weeks.
Google refuses and sends you back to the start. Begin the closed test as soon as the app is usable, not when it is perfect: you can keep improving it while the days are counted.
Declaring that you collect nothing while the app asks for location, or the other way round. Compare the generated declaration with the permissions you set in Eqlo before sending. A false declaration can get the app pulled months after publication.
The reviewer tests on a device you do not own. Check your pages with the system font enlarged and on a narrow phone, two settings almost nobody tries before submitting.
If the app asks people to sign in, supply a demo account that stays active for the whole review. An expired account, or one tied to a single device, blocks the review.
The iPhone version, the publishing steps and the plans take over from here.
Both come from the same Eqlo project and show the same published site, each inside its own native shell. You maintain one project, and a content change appears on both phones at once.
25 dollars, once, paid directly to Google. There is no annual renewal, unlike Apple. While you stay on QR code testing, no account is needed and nothing is due.
Not with a recently created personal developer account. Google requires 12 testers enrolled for 14 days in a row before allowing public release. Organisation accounts follow different rules, depending on the account type opened.
Twelve enrolled and opted in, for the whole period. Recruit fifteen to twenty: if one opts out and the group drops below twelve, the count starts again. Check the list weekly in the console.
Often several days for a first publication, sometimes longer, on top of the closed test. Start the Android track earlier if you want both stores live on the same day.
That works. Connect only your Google Play account, with no Apple account and no annual fee. It is the cheapest route to a first published app, especially if most of your audience uses Android.
You do. The developer account is in your name, so the listing stays yours even if you stop your Eqlo plan. The Expo and React Native source of the app can be downloaded on every plan.
For content, yes: since the app displays your published site, a text, a price or a list changed in Eqlo shows up straight away. A new name, icon or permission needs a new signed build and goes back through review.
Start free with a QR test link, no card needed. The signed Android build comes with Plus, at 19 dollars a month.