How to test a Hercules app before launch with a clear checklist

This guide is for people who build apps and websites by chatting with the Hercules app builder and want to be sure the result holds up in front of real users. The usual failures are not in the demo: they are an app that was never republished, a sign-in that only works for the owner, a payment flow that was never tried, or a phone layout nobody opened.

You will get what Hercules already gives you for testing, a numbered test plan, and a way to add an outside, read-only check. It belongs to a series; the hub is AI app builders: how to test before launch.

How a Hercules app goes live

Per the Hercules documentation, you click Publish and choose a subdomain; every app gets a free address under onhercules.app, and you can add a custom domain later, either bought through Hercules or one you already own. The docs are explicit that your app is not updated until you republish: edits alone do not reach the live site. You can also unpublish an app, which takes it offline while keeping the app and its data.

Behind the app, Hercules provides a built-in database, serverless backend routes, and sign-in methods (social login, email codes, SMS, passwords). Every app has a production environment and a separate development environment with its own database, functions and secrets.

What Hercules already offers for testing

Browser Tests: automated workflows described in plain language with success criteria. They can run manually, on publish, or on a schedule, against the dev preview or the published app, and report pass, fail or error with screenshots and a recording. The docs state they cannot test login or onboarding.
Audits and Security Audit: reviews of your app and vulnerability scans with prioritised fixes.
Testing Hercules Commerce: a documented way to test payments on a published app.
Test Your Mobile App: testing on a real phone through a published URL.
Version control: saved versions with revert.
Hercules MCP: lets assistants such as Claude or Cursor create, edit and publish apps, and read the published URL.

These are solid tools. They work from within the platform, close to the agent that built the app.

Where problems usually hide

Published versus latest. The version people see is the last one you published.
Login paths. Browser Tests do not cover sign-in, so the first-time visitor journey needs another check.
Roles. What a member sees versus an admin.
Mobile. A layout that is fine in the builder but not on a phone.
Basics for strangers. Page titles, headings, image descriptions, contrast, and what a wrong form entry says.

Pre-launch test plan for a Hercules app

Click Publish, then Publish again after your last edit. Confirm you are looking at the latest version.
Open the published address in a private window.
Walk through every page as a visitor who is not signed in.
Sign up with a new test account using the method you offer (email code, social, password).
Sign out and sign back in. Try opening a signed-in page directly by its address.
If you use roles, test one account per role and check what each can see.
Submit every form with valid, empty and wrong data. Read the messages.
Create, edit and delete a record in the database-backed screens, using test data only.
If you use Commerce, follow the Hercules guide to test a payment on the published app.
Open the app on a real phone and on a narrow window. Check overflow and tap targets.
Use only the keyboard on the main journey. Focus must stay visible.
Run Browser Tests on the main flows and the Security Audit, and fix what they report.
Check the custom domain, if any, loads over a secure connection and shows no browser warning.

What an independent test adds

An agent that tests its own work shares its assumptions. An independent test sees only what a visitor sees: it does not read your code, it opens the published address in real browsers, and it reports evidence. It is a second pair of eyes, not a substitute for your own judgement.

Test your Hercules app with Avalyz

Avalyz tests a web app from the outside and is read-only by default: nothing is created or changed on your app.

Free test with no sign-up, 3 a day: paste your published address at /banc or start with https://avalyz.com/essai?url=YOUR_APP_URL.
Optional test account: signing in is the sole form submitted, and the signed-in pages are explored read-only. This fills the gap left by login-blind browser tests.
A GO / NO-GO verdict (or INCONCLUSIVE) with evidence and findings ranked by severity.
A report you can paste back into the Hercules chat for the agent to fix, then test again.
Plans on /tarifs.

Avalyz proves what it saw and does not promise the rest. Related guides: test a Lovable app, test a Base44 app, test a Replit app.

FAQ

Do I need to republish after every change?

Yes. The Hercules docs say your app is not updated until you republish.

The documentation says they cannot test login or onboarding. Test sign-in by hand, and with an independent test account.

Does the free subdomain need any check?

Open it in a private window and confirm it loads without browser or antivirus warnings, as Hercules' publishing page suggests.

Will an outside test change my data?

Not by default. Avalyz reads pages and submits nothing but the sign-in form of the test account you give.

Can I test with Claude through Hercules MCP?

Hercules MCP lets assistants build, edit and publish apps. For testing, run an independent test on the published URL and paste the report back.