Visual architecture reference · Internal Sidebench use

Sign & Glide · Rebrand & Publishing Readiness

Compass Marine on-water towing · aka Progressive Sign & Glide (App ID 1), TravAssist (App ID 2), and the new standalone Sign & Glide (App ID 3). Where the rebrand stands and what is left before both stores go live.

Generated 2026-07-11 Apps 3 variants iOS v5.0.0 build 500 · TestFlight review Android v5.0.0 code 505 · Play internal (draft) Sources ASC API · Play Console · CircleCI · Jira SIGN
The mental model: one white-label React Native codebase ships three branded apps. The active work is the App ID 1 Progressive rebrand (new 96 Sans typography, Progressive branding, updated navigation) plus a new standalone Sign & Glide. Builds are cut, but the last mile is store gates: iOS is waiting on TestFlight beta review, Android is a draft that still needs to be rolled out to testers, and one weather bug (SIGN-600) is still open.
Shipped / live In flight / partial Held / blocker Build / CI path Human action / gate App / surface
L0

One-glance map · one codebase, three apps

A single white-label React Native codebase drives three App Store / Play listings. Each has its own theme, bundle IDs, and release state.

White-label codebase React Native · APP=1|2|3 theme per variant · shared screens
App ID 1 · Progressive Sign & Glide REBRAND IN FLIGHT
Bundle com.xplode.SignGlide · ASC app 1196614726 · v5.0.0 build 500 (iOS) / code 505 (Android)
App ID 2 · TravAssist NO CHANGES
Bundle com.xplode.travassist · rides the same codebase, untouched this cycle
App ID 3 · Sign & Glide (standalone) NEW · NOT LAUNCHED
Bundle com.compassMarine.SignAndGlide · new standalone brand · uploads to Play internal as a draft
Why it matters

One change to shared screens touches all three apps. The rebrand work is scoped to App ID 1; TravAssist is deliberately left alone this cycle.

Deadline context

Progressive target was both apps published; the standalone com.compassMarine.SignAndGlide is new and ships to internal testing first.

L1

Rebrand scope · old look and feel to new

What actually changed for App ID 1. The launch video contrasts the left column (before) with the right (after).

BEFORE · CURRENT LOOK
🔤 Typography: system / mixed fonts
🎨 Color: prior palette
🧭 Navigation: older header + menu layout
🖼️ Icons / splash: prior brand assets
📄 App identity: Progressive Sign & Glide, pre-refresh
 rebrand AFTER · NEW LOOK
🔤 Typography: 96 Sans across the board (Regular / Medium / Bold), set as app-wide default
🎨 Color: Progressive blue #0077B3
🧭 Navigation: centered header title, refreshed drawer + tab bar
🖼️ Icons / splash: new Progressive brand assets
✅ Verified: font confirmed 96 Sans app-wide
Confirmed

Font is 96 Sans across the board for App ID 1 (app-wide default plus every theme and component). The two 42dotSans assets are unused; HelveticaNeue is only in the standalone theme.

Video use

This before/after is the spine of the launch video: old screen recording, then the new Sarasota walkthrough, then this scope slide.

L2

Release pipeline · commit to live

How a change reaches users. Both platforms build from the same CircleCI run, then split into their own store gates.

Merge to prod PR → prod CircleCI build pipeline #589 · both green iOS + Android workflows iOS · TestFlight build 500 uploaded Waiting for beta review Beta App Review demo acct now set External testers then App Store review → production Android · Play code 505 uploaded Internal · DRAFT Roll out draft manual · not done Internal testers no Google review → closed / prod later
The split

iOS gate is Apple beta review (out of our hands, ~1 to 2 days). Android gate is us: build 505 is a draft that a human still has to roll out. The standalone app uploads as release_status: draft by design.

Fastest win

The Android draft can go live to testers today with no Google review · it just needs the rollout click in Play Console.

L5

Current state · timeline and status

Recent build history and where each workstream sits as of 2026-07-11.

Jul 5 to 84.6.0 builds 493 to 499 approved Jul 8v5.0.0 build 500 → TestFlight Jul 9 to 10PR 320 fix · prod build · Android 505 Jul 11 · todayreview + rollout pending
✅ SHIPPED
96 Sans rebrand
typography + Progressive branding confirmed app-wide
PR 320 · SIGN-599
READ_MEDIA_IMAGES removed via merge-remove
Builds cut
iOS 500, Android 505, CI green
Demo account
set on Beta App Review · login verified
 ⏳ IN FLIGHT
iOS TestFlight review
build 500 waiting · Apple case 102937589483
Android internal rollout
code 505 draft · needs manual roll out
Launch collateral
this page + walkthrough video + narration
 🚧 HELD / OPEN
SIGN-600 · weather
API returns today:null at some coords · client blanks the screen
App Store production
not submitted · follows TestFlight
Standalone launch
App ID 3 not yet launched
Read

The rebrand and builds are done; the remaining risk is entirely in store gates and one weather bug, not in the app work.

L6

What is left · effort vs impact

The path to launch, ordered. Top-right is do-now: high impact, low effort.

EFFORT → IMPACT → low high ⚡ NOW · high impact, low effort 🎯 NEXT · high impact, more effort 🧹 THEN · lower impact 🚫 DEFER / watch
1
Roll out Android draft 505 to internal testers · one click in Play Console, no review
2
Chase TestFlight review · demo acct set; Apple case open (102937589483)
3
Fix SIGN-600 weather · fall back to daily[0] when today is null; handle tides 400
4
Submit App Store production once external testing looks clean
5
Ship launch video + this page · old vs new, narration, published to project narratives
6
Standalone App ID 3 launch · after Progressive is live and stable
Do first

Items 1 and 2 unblock testing today. Item 3 (weather) is the only real code work left before a clean production submission.