How do I know if my app still works for customers?

Checked on

Open your live app in a private browser window and do what a customer does: sign up with a new email address, open the confirmation email, log in, and open the payment page. Repeat it after every change you publish and again on a regular schedule, because some problems start without any change from you. A home page that loads does not show that sign-up, log-in or payment works.

Why a page that loads is not enough

Your home page, sign-up page, log-in page and payment page are different pages. Any one of them can stop working while the others open normally.

A check that asks only “is my site online?” looks at one address, usually the home page. It can report that everything is fine while new customers cannot sign up.

The 5-minute check by hand

Do this on your real web address, not the preview, in a private (incognito) browser window. That shows you what a new customer sees.

  1. Sign up with an email address that is not on your team. Many email providers, including Gmail, deliver mail sent to yourname+test1@gmail.com to yourname@gmail.com, so you can make a new test address each time.
  2. Open the confirmation email. Check that it arrives, and that its link opens your real site and not “localhost” (an address that only works on the developer's own computer).
  3. Log in with an account you already had.
  4. Ask for a password reset and follow the link to the end. The reset email is a separate message from the sign-up email, so check it separately.
  5. Open the payment page. Check that the price and the Pay button show, then stop. Do not pay with a real card to test. Use your payment provider's test mode if you want to go further.
  6. Open the site on your phone once.

Some problems start without a change from you

Checking only after you publish misses problems that begin on their own. Lovable's documentation gives one example: authentication emails are limited per hour, and when your project reaches the limit, confirmation emails stop arriving (Lovable Docs: Email authentication). Some hosts also take an app offline when credits run out or a payment fails (see My app went offline. Was it my host, my AI tool or my bill?). A domain or a security certificate (the file that lets browsers show a padlock) can also run out.

So repeat the check after every change, and on a regular schedule. How often depends on what a broken page costs you.

What Heedza checks, and what it cannot see

Heedza opens your home page, follows its links to find your sign-up, log-in and payment pages, and opens them again on a schedule. It checks that each page opens and shows its email box, log-in form or Pay button. If one does not, it sends you a picture of the page and a fix to paste into your AI tool. It never signs in, never submits forms, never types a card number and never clicks Pay.

Heedza cannot see whether a confirmation email reaches an inbox, whether a payment is recorded after a customer pays, or what a signed-in customer sees. A check like this tells you a page has stopped opening or lost its form. It does not replace trying your own app now and then.

Your next step: run the free scan

Use the free scan at the bottom of this page. Paste your live web address. It opens your home page, looks for secret keys in its code, checks a few private files and looks at what search engines see. No account is needed.

More questions

Can I test my payment page without paying?

Yes. Open the payment page, check that the price and the Pay button show, then stop. To go further, use your payment provider's test mode, which does not charge a card.

Is checking the preview enough?

No. The preview and your published site can behave differently. Check the real address. See Lovable log-in works in preview but not after I publish.

Does Heedza tell me if a confirmation email arrives?

No. Heedza cannot see inboxes. It checks that your sign-up page opens and shows its email box. Check the email yourself with a new test address.

Where this comes from