Onboarding: hardware and phone acceptance for the implemented flow #2214

Goal

A new rider goes from the first power-on to a first ride with the OBC and the app. The rider can start on the OBC or in the app. Both paths meet at pairing. After pairing, every step is optional. The OBC stays useful without a phone: the preinstalled map and ride recording work from the first minute.

This epic implements item 5 of #2213 in the direction the owner chose.

Wireframes

Canvas: https://claude.ai/artifact/9UqMiWGPTNopMhHqrK2tVD (owner-private). D boards are the OBC at 2×, P boards are the app.

[!IMPORTANT]
The wireframes are a rough guide, not a design. They set the order of the steps and what each step asks. They do not set layout, copy or visuals. Design every screen in the OBC UI language (device) and the app's Day/Tent theme (app). Most OBC boards need more than one 240 × 320 screen. Check the character limit of each font tier. Spend real effort on the design.

Flow

Branch: BACK on the QR screen opens D13, "Ride without the app?". The rider can get the app later in Settings ▸ Connections.

Decisions

• The app sets only the device name. Language, units, theme, sensors, max HR and FTP are set on the OBC. No new settings protocol.
• The app shows no live sensor status. It tells the rider to look at the OBC.
• The app follows the iOS language. It is English only for now. It does not read the OBC language.
• Setup progress lives in the RRAM settings blob. A factory reset clears it, so setup runs again.
• OBC steps after pairing do not wait for the app. The update, route and ride steps use the existing cards and sync.
• The demo route ships only in the app. The rider sends it with a normal route upload.
• The demo ride ships on the OBC and syncs like a real ride. It is marked as a demo. Onboarding F10: factory demo ride on the OBC #2225 holds the details.
• The firmware update is skippable while the firmware and the app are compatible.
• Setup page rules: SELECT commits and moves on; BACK goes to the previous step; the global escape and the drawer chords are refused on every setup page. The title bar counts the titled steps.
• Button names: the physical buttons are named UP, DOWN, SELECT and BACK in every language.

How we build it

• One sub-issue at a time on each side. The owner reviews every screen before the next sub-issue starts.
• The device work lands in one pull request for the whole device series. The owner approves each screen from its obc-sim --png frames as it lands. App screens get simulator screenshots.
• The implementer designs each screen. The wireframe is only the starting point.

Sub-issues

Open questions

• The power-on gesture: which button, and how long a press.
• The QR link: a universal link on a project domain, or a custom scheme for the demo. S1 decides.
• The French and Spanish setup copy needs a proofread by native speakers.
• The lesson's button positions follow the simulator housing. Check them against the enclosure when it exists.
• No system requirement covers first use yet. Suggest one with obc req suggest.

Out of scope

• Automatic theme switching (sunset or light sensor). Dark mode: ship the Lantern theme, persist it, auto-toggle, dark map style #2048 owns theme work.
• App localisation.
• Live sensor status in the app.
• A setup path for a blank card. The existing NO MAP recovery stays as it is.