[Discussion]: Choose consistent mobile Threads branding

[PixPMusic]

Summary

The mobile Threads header has diverged between Android and iOS after three otherwise separate changes:

• fix(mobile): align Android home branding with desktop #3774 added the T3 Code lockup to Android
• fix(mobile): restore iOS home screen branding #4025 added the equivalent compact lockup to iPhone and iPadOS
• Synchronize mobile threads with authoritative shell snapshots #4163 synchronized mobile thread state, but its final commit, 5dc6c173a, also removed only the iOS lockup while renaming navigation headers to Threads

That last presentation change was unrelated to the synchronization work described by #4163 and left Android branded while iOS displays a plain page title.

Proposed paths

Keep mobile branding

• merge fix(mobile): restore iOS Threads branding #4862 to restore the iOS and iPadOS lockup
• then merge fix(mobile): show the correct build channel in Android's Threads page header #4861 to make Android show the correct Dev, Nightly, or Alpha pill
• close fix(mobile): remove Android Threads page T3 Code branding #4863

Use plain mobile page titles

• merge draft fix(mobile): remove Android Threads page T3 Code branding #4863 to remove the Android lockup
• close fix(mobile): restore iOS Threads branding #4862 and fix(mobile): show the correct build channel in Android's Threads page header #4861

Important

#4862 and #4863 are mutually exclusive and should never both merge. #4861 should merge only after #4862, and should be closed if #4863 is selected.

Accessibility and routing

The visible presentation does not need to replace the semantic page identity:

• the route title remains Threads
• the existing root and thread deep-link paths remain unchanged
• the branded iOS title is exposed as a heading with the accessibility label “T3 Code, Threads”
• the plain Android alternative remains an accessible Threads heading

This preserves the concerns raised around navigation naming, deep linking, and assistive technology while allowing the visual branding decision to be made independently.

Decision

Should the mobile Threads page consistently use the T3 Code lockup, or consistently use the plain Threads title?

Model: GPT-5.6 Sol | Harness: Codex in T3 Code

[PixPMusic]

Julius explained the issue on Discord!

It broke iOS scrollfade so i reverted it
[the header behind the logo] got transparant, no blur with the custom header. Might be fixable in RNS but i didn’t have it in me to debug so i just reverted it

I can confirm this. The fade stops AT the header and has no blur, only fade:

instead of past it, with blur:

[PixPMusic]

Sorted :)