MyJackfruit

Help
Browse topics · Last checks before going live (Testing)

Last checks before going live (Testing)

← Back to How do I check my app once it is live?

How do I test my app the way a new user would, on other phones and browsers?

Short answer

Use a private window and a second e-mail address (it makes an account that stays); once live, open the address on phones and other browsers.

Deeper

Also asked:

How do I test my app the way a stranger would use it? Open it in a private window and do the one thing it is for from its first screen, without using what you know. Better still, watch someone who has never seen it use it at your computer, without helping.

How do I test my app on several phones and browsers before going live? Before it is live, your app runs only on your computer, so phones and other people cannot reach it yet. Once it is live, open its pages.dev address on your phone and in each other browser, and ask a few people with other phones to try it.

How do I check that sign-in works for someone who is not me? Sign in with a second e-mail address you can open, in a private window. Check that the code arrives (look in spam too), that the new person sees only their own vault, and that signing out works. That account stays.

A new user is someone who opens your app for the first time, with no one there to show them how. If your app signs people in, they sign in with GilbPlatform, by a code sent to their e-mail; a new person also chooses a vault name, and GilbPlatform makes their vault, the place where their records are kept. You already know your app and are signed in to it, so you see it differently. The checks below help you see it as they do; they are advice.

What your AI checks already. Agent.Coder, the agent that writes your app's code, has each part tested by Agent.Tester, the agent that tests what others built; some tests open the whole app in a browser and use it the way a person would. An agent is your AI following one written procedure, its standing instructions, for one kind of work. For every change to a screen, Agent.Coder, if it has a browser tool, a way to open and look at web pages itself, also opens the screen in a real browser at phone size, takes a screenshot and counts the errors the browser reports. Its testing rules set those browser tests up in Chrome on a computer, and its rules do not have it try your app on a real phone or in other browsers. A phone-size window on a computer is close to a phone, but not the same: Google says of Chrome's phone view that it is a first-order approximation of how your page looks and feels on a mobile device and When in doubt, your best bet is to actually run your page on a mobile device. (https://developer.chrome.com/docs/devtools/device-mode, read 13 November 2026).

Before it is live: on your computer. Your app then runs only on your computer and, by default, only there, so your phone and other people do not reach it. The answer Where can I test what I've built, and try it myself before anyone else sees it? shows how to open it there.
- Open it in a private window, a separate browser window meant for browsing without your usual saved information. This is what the browser makers say, not something we tried with a live app: Google says Chrome's Incognito window doesn’t automatically sign you into your Google Account or other websites (https://support.google.com/chrome/answer/95464, read 13 November 2026), and Apple says Safari's private window does not keep Changes to your cookies and website data (https://support.apple.com/guide/safari/browse-privately-ibrw1069/mac, read 13 November 2026). In Chrome, choose More, then New Incognito window, or press Command, Shift and N on a Mac (Ctrl, Shift and N on Windows). In Safari on a Mac, choose File and then New Private Window. Then open your app's address in that window.
- Do what a new user would. Do the one thing your app is for, from its first screen, without using what you know. Better still, ask someone who has never seen it to do it at your computer while you watch without helping, and note where they stop or guess; see How do I make my app easy for a first-time visitor?
- Sign in as someone who is not you. Sign in with a second e-mail address you can open. Each address makes its own account, so this makes a real new account with its own vault, the way a new user's is made. Check that the code arrives, looking in the junk or spam folder too; that the new person sees only their own vault, and nothing of yours unless you share it; and that your app's button to sign out works. If your app signs people in, the copy on your computer may first need your approval to reach your vaults; ask your AI what it needs. An account made this way stays until you ask for it to be deleted: GilbApp has no delete button for an account, and the answer How do I delete my account? shows the e-mail to write.

Once it is live: other phones and browsers. Only a live app can be opened on a phone or by other people. It is then at https://<name>.pages.dev, where <name> is the name given to your site, and it is public: anyone on the internet who has that address can open it. Open that address in the web browser on your phone, and in each other browser you have on your computer. If you can, ask a few people with other phones and computers to open it and tell you which phone and browser they used and what they saw; the answer Can I let a few people try my app before everyone can see it? tells more. If your app signs people in, each person needs their own account, made with a code sent to their e-mail, and what they save goes into their own vault, not yours.

What to look at, on each one: that the first screen makes clear what the app is for; that every link and button works; that text and buttons fit the screen, with nothing running off the side; and that signing in and signing out work.

When something is wrong, tell your AI which phone and browser you used and what you saw; the answer How do I tell my AI about a fault so it can fix it? shows how. The fix goes live at the same address, with your yes; see How do I update my app after it is live?

GilbPlatform gives the maker of an app no list of the people who signed in to it, so ask the people you sent it to.

This answer is written for a computer screen.

Source: Standards read from GilbPlatform on 13 November 2026: Agent.Coder (AfterIncrement: Agent.Tester tests each increment; "Open the changed screen at phone size and take a screenshot. Count the console errors."; no browser tool: say so), Rule_Code_testing (RuleTestE2e: browser tests from the user's side, set up with Desktop Chrome), Proc_v_i_c_PublishPagesDev (live at https://<name>.pages.dev; step 3: a Sign out button). Google Chrome Help, Browse in Incognito mode (https://support.google.com/chrome/answer/95464, read 13 November 2026). Safari User Guide for Mac, Browse privately (https://support.apple.com/guide/safari/browse-privately-ibrw1069/mac, read 13 November 2026). Chrome DevTools, device mode (https://developer.chrome.com/docs/devtools/device-mode, read 13 November 2026). Live help pages, sentences shared: Can I try my app on my phone?; Will my app look good on phones as well as computers?; Who tests my app, and why does my AI write tests?; Where can I test what I've built, and try it myself before anyone else sees it?; How do I make my app easy for a first-time visitor?; Can my app have its own users who sign in?; Which e-mail address should I use, and can I change it later? (each address makes its own account); How do I delete my account?; Who can see and use my app once it is live?; How do I get feedback from the first people who try my app?; Can I see who uses my app?; How do I tell my AI about a fault so it can fix it?

Checked against GilbApp d529620.