Android sign-up & sign-in — test script

The Movement Athlete app · 11 August 2026 · please work through this in order and fill in what you see. Roughly 90 minutes — Section Q first, it matters most.

✅ RUN AND COMPLETED — 12 August 2026. Here is what it found.

Tester: Leigh, physical Android phone · Results: the filled-in sheet (32 screenshots embedded) · Written up: docs/company/ANALYTICS/ANDROID_AUTH_TICKETS_2026-08-12.md

The headline: the door works. Someone who does the website quiz, gets the results email and types the password in signs into the app in 3 taps / about 25 seconds. The emailed password is a real password and it works — which confirms NIC-94 live for the first time.

No blocking defect was found. The manual pass turned up friction and polish problems, not a break. So the Android conversion gap remains unexplained — do not treat the list below as its cause.

Six tickets came out of it, all P3: the app discards the server's real error message and shows one generic string (TMA-A1) · no "Forgot password?" at the moment sign-in fails (TMA-A2) · an "or continue with" divider with no buttons under it (TMA-A3) · no show-password eye icon (TMA-A4) · Google Password Manager never saves, suggests or fills (TMA-A5) · password rules only appear after you submit (TMA-A6).

Also found: the results email lands in Gmail's Promotions tab while the welcome email goes to Primary — so the one email carrying the way in is the one Gmail hides. And after sign-in the app shows an email-verification wall ("tap I verified it"); clicking the activation link before opening the app skips it and lands you straight on My Results.

🔴 Two claims this test produced that turned out to be FALSE — do not repeat them

  1. "Forgot password is broken." It is not. The failed attempt used the literal example address printed in this script (see the red box below), which is not a real mailbox — it hard-bounced, was suppressed by our email provider, and so could never be sent to. A retest on a real address worked first time and was confirmed in our provider's logs.
  2. "Signing in with a wrong password says your account doesn't exist." It does not — rows B2 and B3 were filled in the wrong order, and the tester confirmed this on a retest. The server's messages are correct and always were.

Why we're asking you to do this

Our data shows that on Android, only about 2 out of every 3 people who finish setting up the app manage to get signed in. On iPhone it's almost everybody. We don't know why, and we can't see it from the data alone — somebody has to actually try it on a phone.

That's what this is. You are not looking for the app to work. You are looking for the moment where a normal person would give up.

The four rules for this test

  1. Write down the EXACT words of any error or message you see. Not "it showed an error" — the actual sentence, spelled the same way. This is the single most useful thing you can give us.
  2. Screenshot every screen where something goes wrong, and the screen just before it.
  3. Don't fix it or find a clever way round it. If you get stuck, that IS the result. Note what a normal person would have done at that point, then move on.
  4. If you're not sure whether something counts as a problem — write it down anyway. Too much detail is easy for us to filter. Missing detail we can't recover.

Before you start

You will need:

🔴 READ THIS FIRST — never type an address from this page literally

Everywhere below you will see addresses written as YOURNAME+tma01@gmail.com. YOURNAME is not an address. Replace it with your own Gmail username every single time.

This exact mistake already cost us a day. In the 12 Aug run the tester typed one of these examples literally. It is a mailbox nobody owns, so the email hard-bounced, our provider blocked the address permanently, and every later email to it silently failed — which looked exactly like a broken password reset. We nearly sent our developers an emergency ticket for a bug that did not exist.

So: write down the real addresses you use, in the sheet, as you go. If a test behaves oddly, the first question we will ask is "what exact address did you type?" — and we need to be able to answer it.

Make yourself unlimited test email addresses. Gmail lets you add +something before the @ and it still arrives in your inbox. So if your Gmail address is jane.smith@gmail.com, then jane.smith+tma01@gmail.com and jane.smith+tma02@gmail.com are all different accounts to our app, but all land in your one inbox. Use a new number for each test — with your own username, never the examples on this page.

Start completely fresh:

  1. If the app is already installed — delete it (long-press the icon → Uninstall)
  2. Reinstall from the Google Play Store
  3. Do not sign in yet

Fill this in first:

Phone make and modele.g. Samsung Galaxy S22
Android version (Settings → About phone)e.g. Android 14
App version (Play Store → app page → scroll down)e.g. 1.70.71
Date and time you started
Wifi or mobile data?

Section Q — the real journey DO THIS ONE FIRST

This is the most important test in the document

Most people don't find our app by accident. They do the quiz on our website first — which asks for their email — and only then download the app. We think that journey is where people get stuck, and we need you to walk it exactly as a real person would.

Do not skip ahead and do not take shortcuts. Go through the whole quiz properly, answer the questions honestly, then open the app. If you get stuck, that is the finding — stop, write down exactly where, and tell us.

Q1 Do the quiz on the website, start to finish
  1. On a laptop or in the phone's browser, go to quiz.themovementathlete.com
  2. Go through the whole thing as if you were a real person
  3. When it asks for your email, use a brand new one: YOURNAME+journey01@gmail.com
  4. 🔴 If it asks you to choose a password, write down EXACTLY what you typed. If it never asks for a password, write that down too — that's just as important.
  5. Finish the quiz and reach the results
Record: Did the quiz ask you to create a password — yes or no? What was it? Did you reach the end and see your results? Screenshot the last screen.
Q2 Check your inbox before you touch the app
  1. Open the inbox for YOURNAME+journey01@gmail.com
  2. Check spam as well
  3. List every email that arrived, with its subject line and what time it came
  4. Open each one and read it properly
Record — read carefully:
  • 🔴 Does one of the emails give you a password? If so, copy it out exactly, character for character. You will need it in Q3.
  • Does it look like a real password (a jumble of letters/numbers), or does it literally say something like [Chosen Password] in square brackets? If you see brackets, screenshot it immediately and tell us — that used to be a known fault and we believe it's fixed, but nobody has checked a real email since.
  • Is there a link to activate or confirm your account? Don't click it yet.
  • Screenshot every email in full.
Q3 — THE BIG ONE Now open the app and try to get in
What we think happens, and why we need you to check it: the quiz already made an account for you, so the app should refuse to let you sign up — it has to be sign in instead, using the password from that email. On an iPhone people can dodge all of this by tapping "Sign in with Apple". On Android that button doesn't exist — so an Android user has to find the email, find the password, and find the sign-in option. We want to know how hard that is.
  1. On the Android phone, install the app fresh (delete it first if it's there)
  2. Go through the app's setup to the account screen
  3. Try to get in using YOURNAME+journey01@gmail.com — the same email you gave the quiz
  4. Try it the way a normal person would: if there's a "sign up" screen in front of you, use that first. If that fails, then look for "sign in".
Record this in detail — it's what the whole exercise is for. Try them in this order, because it's the order a real person would:
  1. Sign UP with the quiz email. Did it work, or refuse? What exactly did it say? (We expect a refusal — the account already exists from the quiz.)
  2. Could you find "sign in" from there? Was it offered to you at that moment, or did you have to go back and hunt for it? How many taps? This is the bit we most suspect.
  3. Now sign IN using the password from the email (Q2). 🔴 Does that password actually work? This is the single most important yes/no in the document.
  4. If that fails, try the password you chose during the quiz, if there was one.
  5. Did you get in at all? If you ended up stuck, say so plainly, and tell us what a normal person would have done at that point.
  6. How long did the whole thing take, and how many attempts?
Q4 If you got in — did your quiz answers come with you?
The app is supposed to remember what you told the quiz. Does it? Does it show you a plan or assessment that matches your answers, or does it start you from scratch and ask everything again? Being asked the same questions twice is a finding.
Q5 If you got stuck — can password reset rescue you?

Only do this if Q3 left you locked out.

  1. Use "forgot password" with YOURNAME+journey01@gmail.com
  2. Wait for the email — note how long, and check spam
  3. Follow it through and set a new password
  4. Try to sign in again
Record: Did the reset email arrive? Did the link work? Did it get you in? If password reset is the only way a quiz user can reach the app, we need to know that.
Q6 Do it once more, the other way round
  1. New email: YOURNAME+journey02@gmail.com
  2. Do the quiz again, but this time click the activation/confirm link in the email before opening the app
  3. Then try to get into the app
Record: Was this easier or harder than Q3? Did clicking the link first make any difference?

🔢 Count everything in Q3 — this is how we compare to iPhone

You only need to test Android. We'll handle the iPhone side separately — don't worry about it.

But because we can't put the two phones side by side, your numbers have to do that job. On iPhone there's a "Sign in with Apple" button — that's one tap, no email, no password, no typing. So for Q3 please count precisely: how many taps, how many separate screens, how many things you had to type, how many times you switched to your email app, and how many minutes it took, start to finish. If the honest answer is "eleven taps and four minutes", that tells us everything we need without a second phone.

Section A — Creating a brand new account

This is the part we most suspect. Take your time here.

A1 The normal way — does it work at all?
  1. Open the app and go through the setup questions until it asks you to create an account
  2. Use a brand new email: YOURNAME+tma01@gmail.com
  3. Password: Testing123
  4. Name: Test One
  5. Submit
Record: Did it work — yes or no? How many seconds did it take after you pressed the button? Where did it put you afterwards (inside the app, or back at a login screen)?
🔴 Write this email and password down — you need them again in A5 and B1.
A2 — backup for Q3 Signing up with an email that already has an account
Only do this if Section Q didn't work for some reason (the quiz was down, you couldn't finish it). It is a shortcut version of Q3 — it creates the "email already has an account" situation artificially instead of the real way. The real journey in Section Q is far better evidence, so always prefer that.
  1. Close the app fully and delete it, then reinstall (so you're a "new" person again)
  2. Go through setup to the account screen
  3. Use the same email from A1YOURNAME+tma01@gmail.com
  4. Password: Testing456 (deliberately a different one)
  5. Submit
Record — this is the important bit:
  • What exactly does it say? Word for word.
  • Does it offer you any way to continue — a "sign in instead" link, a "forgot password" option, anything?
  • Could you actually get into the app from here? If yes, how many taps? If no, say so — that's the answer we're looking for.
  • Screenshot it.
A3 A password that's too short
  1. Fresh email: YOURNAME+tma02@gmail.com
  2. Password: Test12 (only 6 characters — our server needs at least 8)
  3. Submit
Record: Did it warn you before you pressed submit, or only after? What exactly did it say? Did it tell you the password needs to be 8 characters? — or did it just say something vague like "invalid password"?
A4 A password with letters only
  1. Fresh email: YOURNAME+tma03@gmail.com
  2. Password: password (8 characters, but no numbers — our server rejects this)
  3. Submit
Record: Exact wording. Does it tell you that you need to include a number? If someone didn't know that rule, would they be able to work it out from what's on screen?
A5 A password with numbers only
  1. Fresh email: YOURNAME+tma04@gmail.com
  2. Password: 12345678 (8 characters, but no letters — also rejected)
  3. Submit
Record: Exact wording. Is it the same message as A4, or different?
A6 Leaving fields empty
  1. Try to submit with the name box empty
  2. Then try with the email box empty
  3. Then try with the password box empty
Record: For each one — does it tell you which box is the problem, or just refuse? Does the button do nothing at all (which feels broken to a user)?
A7 An email address with a typo
  1. Try youtma05gmail.com — no @ at all
  2. Then try YOURNAME+tma05@gmail — no .com
Record: Does it catch it? What does it say?

Section B — Signing back in to an existing account

B1 The normal way
  1. Delete and reinstall the app
  2. Look for a "Sign in" or "Already have an account" option
  3. Use the email and password from A1
Record: Was the "sign in" option easy to find, or did you have to hunt for it? How many taps from opening the app? Did it work?
B2 Wrong password
  1. Same email from A1, but type the password wrong on purpose
Record: Exact wording of the message. Does it offer "forgot password" at that moment? — that's exactly when a real person needs it.
B3 An email that has never been used
  1. Try to sign in with YOURNAME+tma99@gmail.com and any password
Record: What does it say? Does it suggest creating an account instead?
B4 — IMPORTANT Forgot password — the whole journey
  1. Start the "forgot password" flow with the A1 email
  2. Check your inbox. How long did the email take to arrive? Did it arrive at all?
  3. Check your spam folder too — and say if that's where it landed
  4. Tap the link in the email
  5. Set a new password and try to sign in with it
Record: Did the email arrive — and how many minutes? Did the link open the app, or a web page? Could you finish the whole thing and get signed in? If you got stuck at any point, say exactly where.

Section C — What's actually on the screen

C1 Photograph the whole sign-in screen

Take a clear screenshot of the account/sign-in screen with nothing typed in, and tell us everything you can see on it.

Specifically — is there any button to sign in with:
  • Google? yes / no
  • Apple? yes / no
  • Facebook? yes / no

We already know the answer is no to all three on Android — it was checked on 11 Aug. Please just confirm it with a screenshot so we have it on record, and note whether the screen makes it clear what you're supposed to do instead.

C2 Is the password visible?
Record: Is there an eye icon to show what you've typed? If not — note that. Typing a password blind on a phone is a common reason people give up.

Section D — Real-world annoyances

These are the things that don't look like bugs but quietly lose people.

D1 Does the keyboard get in the way?
When you tap the password box, does the keyboard cover it up? Can you still see what you're typing, and can you scroll to reach the submit button?
D2 Does saved-password autofill work?
Does your phone offer to fill in or save the password (Google Password Manager)? Does the suggestion appear? Does tapping it actually fill the boxes?
D3 Leaving and coming back
  1. Start filling in the signup form
  2. Switch to another app for 30 seconds
  3. Come back
Record: Is what you typed still there, or has it been wiped? Did the app restart from the beginning? — that would be a big one.
D4 A bad connection
  1. Fill in the signup form with a fresh email
  2. Turn on aeroplane mode
  3. Press submit
  4. Wait 30 seconds, then turn aeroplane mode off
Record: Does it tell you there's no connection, or does it just spin forever? Does it recover when the connection comes back, or do you have to start again?
D5 How long does the whole thing take?
From opening the app for the first time to being signed in and inside — time it. How many screens? How many taps? How many things did you have to type?

Section E — After you're in

E1 Where does it put you?
After signing up, are you inside the app ready to use it — or somewhere confusing? Can you get to a first workout? How many taps?
E2 What emails arrive?
Check the inbox for the A1 address. List every email that arrived, with the subject line and how long after signup. Note anything that looks wrong — broken text, a placeholder that didn't fill in, a link that doesn't work.

You don't need an iPhone

Android only — that's the whole job. An earlier version of this document asked for an iPhone comparison; ignore that, we're covering it another way.

What replaces it is your counting. Be precise about taps, screens, things typed, trips to your email app, and minutes — especially in Q3. Those numbers are what we'll hold up against the iPhone journey, so a rough guess costs us more than you'd think.

Tell us straight away if…

Anything else, just finish the list and send it all in one go.

Summary sheet — please fill this in

TestWhat it was Worked?Exact message / what happenedScreenshot?
Q1Quiz on website, start to finishyes / noy / n
Q2Emails received from the quizy / n
Q3🔴 Get into the app with the quiz emailyes / noy / n
Q3b🔢 Q3 counted: taps / screens / things typed / minutesy / n
Q4Quiz answers carried into the app?yes / noy / n
Q5Password reset rescued you?yes / noy / n
Q6Same, clicking activation link firstyes / noy / n
A1New account, normalyes / noy / n
A2Email already has an accountyes / noy / n
A3Password too shortyes / noy / n
A4Password letters onlyyes / noy / n
A5Password numbers onlyyes / noy / n
A6Empty boxesyes / noy / n
A7Bad email formatyes / noy / n
B1Sign in, normalyes / noy / n
B2Wrong passwordyes / noy / n
B3Unknown emailyes / noy / n
B4Forgot password, full journeyyes / noy / n
C1Any Google/Apple/FB buttons?yes / noy / n
C2Show-password eye icon?yes / noy / n
D1Keyboard covers fields?yes / noy / n
D2Autofill works?yes / noy / n
D3Form survives leaving app?yes / noy / n
D4No-connection behaviouryes / noy / n
D5Total taps / minutesy / n
E1Lands inside the app?yes / noy / n
E2Emails receivedy / n

Last question — and answer it honestly

If you were a normal person who'd just downloaded this app, at which exact point would you have given up? If you wouldn't have — say that too, it's just as useful.

Thank you — this is genuinely hard to work out from data alone, and what you find here decides what we fix next.
Send everything back in one message: the filled-in table, your screenshots, and the last answer.

← back to the cockpit