Next step · What to do next

Test my site on real phones (iPhone and Android)

What you may see

It looks right on my computer but I have not seen it on a phone

Why this step

Most visitors use phones, and the browsers on iPhone and Android behave differently from your desktop browser.

Before you start

Which phones do your customers use (ask three of them)?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Test my site on real phones (iPhone and Android)

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
Most visitors use phones, and the browsers on iPhone and Android behave differently from your desktop browser.

DO THESE STEPS, IN THIS ORDER
1. Give me a short phone test script: open each main page, scroll, rotate, tap every button, fill every form with the keyboard open, switch language, and use the menu.
2. List what to watch for: sideways scroll, text under the browser bar, tiny tap targets, zoom on form fields, buttons needing two taps, fixed bars covering content.
3. Where possible, run automated checks in a phone-sized browser engine for Safari and Chrome and report overlaps and clipped text.
4. Turn the findings into a fix list sorted by how many customers they affect.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- Every main flow works with one hand on iPhone Safari and Android Chrome, in English and Arabic.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not judge only by a desktop window resized small.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Give me a short phone test script: open each main page, scroll, rotate, tap every button, fill every form with the keyboard open, switch language, and use the menu.
List what to watch for: sideways scroll, text under the browser bar, tiny tap targets, zoom on form fields, buttons needing two taps, fixed bars covering content.
Where possible, run automated checks in a phone-sized browser engine for Safari and Chrome and report overlaps and clipped text.
Turn the findings into a fix list sorted by how many customers they affect.

Do not do this

Do not skip Arabic on the phone.
Do not judge only by a desktop window resized small.

Try another entry