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 URLAn iPhone app starts as a sentence you type, then as screens you test on your own phone with a QR code that lasts 24 hours. Eqlo writes native tabs, loading states, and a signed file for the App Store. The Apple Developer account stays in your name. Review stays Apple.
What you need before you start is a loop a member will repeat on a phone: open a tab, see a list, tap an action, and land on a loading or error state that still makes sense. Apple rejects binaries that only display a site. If the work is reading a page, build a website. If the work is tabs, a camera, a location, or an offline list, you are on this page. Write that loop in one sentence before you open the chat.
You do not need the account to see the first screens or to test with a QR code. You need it to submit a signed file. Apple bills that account, not Eqlo. Create it when testers have already used the app for a week, not the night you type the prompt. The listing, the banking, and the review notes sit on that account. Eqlo never holds those logins.
If the app never asks for location, do not list location. If it stores an email, say so on a page the reviewer can open. Eqlo lists the permissions the project actually calls: camera, location, push, or none. You still write the sentences only you can write, because you know what you keep. A policy copied from another app is a common first refusal.
Google Play will accept a closed test trail that Apple does not ask for. Apple will refuse a wrapper that Play sometimes still lets through. The two stores are two programmes.
Apple reviewers treat a site in a chrome with an icon as a wrapper. Eqlo writes React Native screens, native tabs, and native back. You still walk a cold start on a device that is not yours before you click Submit.
If the project has accounts, leave a login the reviewer can use. Rotate it after. Apple will bounce a wall with no demo account. Play often wants the same courtesy, but Apple is the store that fails first apps on this point.
Eqlo generates icons, the launch screen, and listing captures in the formats App Store Connect expects. You still write the name, the subtitle, and the age rating. The shots should come from the build you are sending, not from a week-old QR preview.
A complete mobile app is about a day of back and forth after the first draft, which lands in two to five minutes. The store file is a later object. You do not pay Apple to discover an empty tab.
Open the project, show the QR code, and install the test build. The link lasts 24 hours, so testers are not stuck on last week. Hand it to three people who will not be polite. Write down the tab they cannot find.
Select the element on the screen and write the change in English. Each exchange creates a version you can restore. Compare two versions when a correction goes too far. 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 App Store Connect. Content updates later do not go back through store review.
A site slipped into a frame with an icon. Walk the first launch with JavaScript in mind: if the app is only a browser, stop and build a website instead. Eqlo refuses that path on purpose.
Put the demo email in the review notes. Confirm it still opens after your last correction. A password you changed on Friday is a Monday bounce.
Listing data you do not collect, or hiding data you do, both fail. Read the permission list Eqlo shows, then write the label from that list. The label is not marketing copy.
Empty, crash, or a permission you never explain. Install the signed file on a second phone before you submit. If the splash never ends, do not pay the queue to tell you.
The Android path, the five store steps, and the shared app builder take over from here.
Not to describe the screens, test with a QR code, or send the first signed file. Eqlo produces the package. A Mac is useful later if you want to open the React Native repo locally. It is not a gate for the first submission.
Yes. Screens, accounts, and the Postgres database stay in one place. You still submit two packages, because the stores are two programmes.
Often one to three days on a clean binary. A weekend, a holiday, or a missing login can make it longer. We do not own that queue and we do not invent a date.
Read the note. If it is something Eqlo generated, you fix it in the project and send again. If it is your listing or your privacy text, that is yours to correct.
You do. It sits on your developer account. The code sits in your GitHub repository. Eqlo is the builder, not the publisher of record.
Five free projects, a QR test build, no card. Signed builds sit on Plus at $19. Store fees stay with Apple.