Repository navigation
Design iOS and Android different - alignment possible? #2218
Description
NOOP version
11.6.0
Platform
Android
OS version
16
WHOOP strap / Oura ring model
WHOOP 5.0
Where the data is coming from
Live Bluetooth (WHOOP strap connected)
Test Centre profile
Not a test-mode bug
What happens
The iOs app looks great. Android looks good. But different.
A screenshot from reddit confirmed differences, not only visually. Eg the coach button.
What you expected instead
Same experience on both platforms.
Steps to reproduce
See differences
Strap log
Before you submit
- I attached my exported NOOP .zip (not a screenshot of the Live screen). If my bug is a clearly reproducible UI issue I described exactly how to see it instead.
- I attached or pasted a strap log above — or my bug is a clearly reproducible UI issue that doesn't need one (e.g. a typo, a button that does nothing) and I've described exactly how to see it.
- I checked the Troubleshooting guide — especially "history syncs but no data" (most often the strap isn't banking history to flash; charge it to 100% and reconnect).
- I checked the FAQ and — if I'm on a WHOOP 5.0 / MG — the 5.0/MG status page, and this isn't an already-known limit (e.g. SpO₂, or recovery/sleep on the 5/MG).
- I've left out anything personal (strap serial, account email, raw export).
Activity
ryanbr commentedon Sep 14, 2026
You asked this on #1068 too and got no reply before it was wrapped up. That was not a decision, it was me not answering, and it is a fair thing to raise again.
So here is a real answer, starting with the one you named.
The Coach button: you are right, and it is one line of intent
iOS has five tabs. Android has four.
Coach was promoted to a top-level tab on iOS and Android did not follow, so on Android it lives inside More. Android's own shell comment still says it mirrors the iOS tab bar, which stopped being true when that promotion happened:
That is a concrete, checkable difference, it is exactly the one you picked out of a screenshot, and it is worth taking. I will pick it up.
The general ask needs splitting, and not as a way of avoiding it
"Same experience on both" is the right instinct and the wrong unit of work. Some of what differs between the two is drift nobody chose, like the Coach tab, and that should be closed. Some of it is deliberate, and closing it would make Android worse rather than more similar.
The clearest example: the Android sleep hero measures its "in bed" window differently from iOS on purpose. That was decided twice, in #160 and #395, because the Android reading is the more honest one for a split night. Aligning it to iOS would be a regression dressed as consistency. When I last went through a list of proposed alignments, several were that shape.
So what I can commit to is the first kind: differences that exist because one platform moved and the other did not. What I cannot promise is that the two apps will converge everywhere, because a few of the gaps are the better answer sitting on one side.
What would actually help
The Coach tab I can do from what you have given me. Beyond that, the useful unit is a specific thing rather than a screenshot pair: a screen, what it does on each, and which one you would rather have. That is a different question from "they look different", and it is the one I can act on.
You have effectively been doing this already, in #2219 and #2181 and the stress reports, and those were all actionable precisely because they named one thing. Coach is the same shape. More of those beats a general alignment epic, which is roughly what #1068 became.
One caution on the screenshot comparison: 11.7.0 went out today and moved several things on both platforms, so some of what you are comparing may already differ less. Worth re-checking on the current build before listing more.
Keeping this open, retitled around the Coach tab once I have the change up, and I will point at it from here.
nav(android): give Coach the bottom-bar tab it has on iOS (#2222)
ryanbr commentedon Sep 14, 2026
The Coach tab is in, as 44e4d15. Android's bar is Today · Trends · Sleep · Coach · More now, matching iOS, and Coach is out of the More sheet the way it is on iOS.
Thanks for raising it twice. The second time is what got it looked at, and the first time going unanswered was mine.
It turned out to be four things rather than one, which is worth saying because it is the argument for the kind of report you filed. The slot itself was the easy part. The More button's highlight named its siblings by hand, so Coach would have lit Coach and More at once. Coach was still listed inside More, so the same destination would have appeared in two places. And the fifth slot takes about a fifth off every label's width, on a bar whose size setting goes to 2x, so the labels needed bounding. None of those are visible in a screenshot; all of them follow from the one difference you pointed at.
There is a test now asserting the bar and the More sheet stay disjoint, because the duplication was the part a reader cannot see: those two lists sit four hundred lines apart and neither mentions the other.
It will be in the next testing build rather than the current one.
On the rest of it
I am leaving this open, because the general question you asked is still open and I do not want to close it by answering the easy part.
What I said before stands: I will take differences where one platform moved and the other did not, and I will not promise the two converge everywhere, because a few of the gaps are the better answer sitting on one side. The Coach tab was the first kind. The sleep hero's "in bed" window is the second kind.
What would help most is more of exactly what you did here: one thing, on both platforms, and which one you would rather have. Coach was actionable in a morning because you named it. A screenshot pair is a starting point, but the thing I can act on is the sentence you wrote underneath it.
If you would rather I wrapped this one up now that its concrete item has landed and opened a fresh issue per difference as you find them, say so and I will.