# C12 Native App — Voice-over Script **Runtime** ~4:14 · **19 beats** · **579 words** · paced at 148 words per minute **Screens** `prototype/shots/` · 940 × 1860 px RGBA with true alpha, device bezel included **Live prototype** `prototype/index.html` — press Space to play the same sequence on screen --- ## How to use this 1. Record the **Continuous read** at the bottom in one pass. Do not chase the timings while recording. 2. Drop the shots on the timeline in order and stretch each to the duration in the table. 3. Where a beat lists two shots, cut between them on the sentence break noted in *Cut on*. 4. Every shot is RGBA with a genuinely transparent surround, so it drops onto any background with no masking and no white box. --- ## Beat sheet | # | In | Length | Beat | Screens | |---|----|--------|------|---------| | 01 | `0:00` | 17.5s | The problem | `01-today` | | 02 | `0:13` | 18.5s | Live Activity | `02-live-activity` | | 03 | `0:32` | 9.2s | Dynamic Island | `03-island-compact` → `04-island-expanded` | | 04 | `0:41` | 19.3s | Widgets | `05-widgets` → `06-widgets-ticked` | | 05 | `1:00` | 16.5s | Dashboard, rebuilt | `07-tabbar-dashboard` → `08-tab-notifications` | | 06 | `1:15` | 18.1s | On-device summary | `09-ai-summary` | | 07 | `1:33` | 16.9s | On-device draft | `10-ai-draft` | | 08 | `1:50` | 13.3s | Notification actions | `11-notifications` → `12-notif-prayed` | | 09 | `2:03` | 11.6s | Face ID | `13-locked` → `14-unlocked` | | 10 | `2:15` | 13.3s | Scan the report | `15-scan` | | 11 | `2:28` | 10.4s | Report captured | `16-scan-result` | | 12 | `2:38` | 16.5s | Curriculum audio | `17-curriculum` → `18-carplay` | | 13 | `2:55` | 12.0s | Wallet pass | `19-wallet` → `20-wallet-stored` | | 14 | `3:07` | 14.9s | Say it out loud | `21-voice-recording` | | 15 | `3:22` | 10.4s | Commitments | `22-commitments` | | 16 | `3:32` | 8.4s | Reminders | `23-reminders` | | 17 | `3:41` | 16.1s | Dynamic Type | `24-type-default` → `25-type-xxl` | | 18 | `3:57` | 17.3s | Close | `26-close` | --- ## Beats in full ### 01 · The problem `0:00` · 13.7s · `01-today.png` > This is the C12 dashboard today, recreated from the shipping app. Six rows of label and value, then two more, then a link list. Nothing is sized by how much it matters, and the phone underneath is doing almost none of the work. ### 02 · Live Activity `0:13` · 18.5s · `02-live-activity.png` > So start with the one day a month that matters most. Forum day. A Live Activity puts it on the Lock Screen: how much of the day is left, who made it, and what the member still owes. All of that is data C12 already holds. No unlock, no app. ### 03 · Dynamic Island `0:32` · 9.2s · `03-island-compact.png` → `04-island-expanded.png` > It follows a member into every other app. Compact while they work. One press, and the rest of the day is there. *Cut on* — “Compact while they work” ### 04 · Widgets `0:41` · 19.3s · `05-widgets.png` → `06-widgets-ticked.png` > Eleven months of the year, C12 does not need a screen at all. It needs two facts: when is the next forum, and what do I owe someone. Widgets answer both. And a commitment can be closed from the home screen in about two seconds. *Cut on* — “Widgets answer both” ### 05 · Dashboard, rebuilt `1:00` · 14.5s · `07-tabbar-dashboard.png` → `08-tab-notifications.png` > Inside the app, the cheapest fix in the whole audit. Same data, sized by what actually matters. The next meeting gets the space, todo completion becomes a ring, and the tab bar finally tells you where you are. *Cut on* — “A real tab bar, in C12 colours, that marks where you are, and keeps each tab's place when you come back to it” ### 06 · On-device summary `1:15` · 18.1s · `09-ai-summary.png` > A peer brings something hard to the forum. Twelve replies. A member opens it on a Tuesday morning with four minutes to spare. The iPhone reads the thread and tells them what they missed, including the part where they were asked directly. ### 07 · On-device draft `1:33` · 16.9s · `10-ai-draft.png` > Then it drafts a reply, which the member edits and sends. All of it on the device. Nothing left the phone. For a network of CEOs sharing payroll numbers and prayer requests, that last sentence is the whole product. ### 08 · Notification actions `1:50` · 13.3s · `11-notifications.png` → `12-notif-prayed.png` > Notifications a member can actually finish. A peer's reply arrives as a person, not as an app. And I am praying is one tap. A button no other app has. *Cut on* — “And I am praying is one tap” ### 09 · Face ID `2:03` · 11.6s · `13-locked.png` → `14-unlocked.png` > C12 holds a member's real financial position. So lock the numbers, not the app. Discussions stay open. The dashboard covers itself when the phone goes down. *Cut on* — “Discussions stay open” ### 10 · Scan the report `2:15` · 13.3s · `15-scan.png` > Then the heaviest job in the product. Once a year every member writes a CORE Business Presentation, and section ten wants five Economic Value Add figures. Today a CEO reads them off printed statements and retypes them. Instead, point the camera. ### 11 · Report captured `2:28` · 10.4s · `16-scan-result.png` > Five figures, read on the device, each one labelled and every one editable. It saves encrypted against Financial Management, and the statements attach alongside them. ### 12 · Curriculum audio `2:38` · 16.5s · `17-curriculum.png` → `18-carplay.png` > C12 already offers read it to me on the monthly curriculum, so the reading is solved. What a browser cannot do is follow a member into the car. A media session puts the same audio on CarPlay, keeps playing with the screen off, and syncs where they got to. *Cut on* — “But they do drive forty minutes to forum” ### 13 · Wallet pass `2:55` · 12.0s · `19-wallet.png` → `20-wallet-stored.png` > Forum day, handled in advance. A Wallet pass surfaces itself on the morning of, and again when the member reaches the venue, costing no notifications at all. *Cut on* — “A Wallet pass surfaces itself on the morning of, and again when the member reaches the venue, costing no notifications at all” ### 14 · Say it out loud `3:07` · 14.9s · `21-voice-recording.png` > The most valuable minute in C12 is the one right after a member presents, when their peers have just told them what to do. Nobody types then. But they will talk in the car. ### 15 · Commitments `3:22` · 10.4s · `22-commitments.png` > Two minutes of speech becomes three commitments, each one attributed to the peer who raised it, and every one editable before it saves. ### 16 · Reminders `3:32` · 8.4s · `23-reminders.png` > And those commitments follow the member out of C12, into the list they already keep open all day. ### 17 · Dynamic Type `3:41` · 16.1s · `24-type-default.png` → `25-type-xxl.png` > One more thing. C12 members are chief executives over forty-five, and most of them turn their phone text up. So large text is not an accessibility edge case here. It is the median rendering of the product. *Cut on* — “So large text is not an accessibility edge case here” ### 18 · CORE preparation `—` · 17.0s · `27-core-prep.png` > One more, and it is the one that is not a meeting. The CORE Business Presentation happens once a year. Twelve encrypted sections a member fills in over months, last year's key questions carried forward, three years of figures behind it. A phone is good at exactly that: a little at a time, wherever they are. ### 19 · Close `3:57` · 17.3s · `26-close.png` > One more, and it is the one that is not a meeting. The CORE Business Presentation happens once a year. Twelve encrypted sections a member fills in over months, last year's key questions carried forward, three years of figures behind it. A phone is good at exactly that: a little at a time, wherever they are. None of this rebuilds C12 natively. Every one of these sits in the native shell around the same Rails application that already works. The web app stays the product. The shell stops being a wrapper, and starts being a tool. --- ## Continuous read Read straight through. Pause about one second between paragraphs. This is the C12 dashboard today, recreated from the shipping app. Six rows of label and value, then two more, then a link list. Nothing is sized by how much it matters, and the phone underneath is doing almost none of the work. So start with the one day a month that matters most. Forum day. A Live Activity puts it on the Lock Screen: how much of the day is left, who made it, and what the member still owes. All of that is data C12 already holds. No unlock, no app. It follows a member into every other app. Compact while they work. One press, and the rest of the day is there. Eleven months of the year, C12 does not need a screen at all. It needs two facts: when is the next forum, and what do I owe someone. Widgets answer both. And a commitment can be closed from the home screen in about two seconds. Inside the app, the cheapest fix in the whole audit. Same data, sized by what actually matters. The next meeting gets the space, todo completion becomes a ring, and the tab bar finally tells you where you are. A peer brings something hard to the forum. Twelve replies. A member opens it on a Tuesday morning with four minutes to spare. The iPhone reads the thread and tells them what they missed, including the part where they were asked directly. Then it drafts a reply, which the member edits and sends. All of it on the device. Nothing left the phone. For a network of CEOs sharing payroll numbers and prayer requests, that last sentence is the whole product. Notifications a member can actually finish. A peer's reply arrives as a person, not as an app. And I am praying is one tap. A button no other app has. C12 holds a member's real financial position. So lock the numbers, not the app. Discussions stay open. The dashboard covers itself when the phone goes down. Then the heaviest job in the product. Once a year every member writes a CORE Business Presentation, and section ten wants five Economic Value Add figures. Today a CEO reads them off printed statements and retypes them. Instead, point the camera. Five figures, read on the device, each one labelled and every one editable. It saves encrypted against Financial Management, and the statements attach alongside them. C12 already offers read it to me on the monthly curriculum, so the reading is solved. What a browser cannot do is follow a member into the car. A media session puts the same audio on CarPlay, keeps playing with the screen off, and syncs where they got to. Forum day, handled in advance. A Wallet pass surfaces itself on the morning of, and again when the member reaches the venue, costing no notifications at all. The most valuable minute in C12 is the one right after a member presents, when their peers have just told them what to do. Nobody types then. But they will talk in the car. Two minutes of speech becomes three commitments, each one attributed to the peer who raised it, and every one editable before it saves. And those commitments follow the member out of C12, into the list they already keep open all day. One more thing. C12 members are chief executives over forty-five, and most of them turn their phone text up. So large text is not an accessibility edge case here. It is the median rendering of the product. None of this rebuilds C12 natively. Every one of these sits in the native shell around the same Rails application that already works. The web app stays the product. The shell stops being a wrapper, and starts being a tool.