Brand and design · Hi-fi screens · S07 Onboarding · Notification priming
Data-binding map: S07 Onboarding · Notification priming
Data-binding map of Onboarding · Notification priming: every field to its source, and what each required state shows.
Generated by
botgumi-design indexfrom../../screens.json. Edit that file, not this page.
Every field S07 shows and where it comes from.
| Field | Source (endpoint or local state) | Format | Fallback |
|---|---|---|---|
| notification-priming · preview | local onboarding.reminder_time · onboarding.reminder_time, diagnostic article.title |
notif.daily.body |
generic body without title |
| notification-priming · preview | api POST /onboarding article.title |
||
| notification-priming · submit | call POST /onboarding · POST /v1/onboarding with all answers; PUT /v1/me/push-token if granted |
— | on failure: inline retry, answers kept |
| notification-priming · submit | call PUT /me/push-token |
||
UNUserNotificationCenter.requestAuthorization → PUT /v1/me/push-token |
device notification_permission · From the board's data-bind; no row in data-binding.md yet. |
||
UNUserNotificationCenter.requestAuthorization → PUT /v1/me/push-token |
call PUT /me/push-token |
Binds on the boards
The data-bind values across every state.
UNUserNotificationCenter.requestAuthorization → PUT /v1/me/push-tokenonboarding.reminder_time
States
- Loading: From states.md (Onboarding (6 steps)): n/a (local)
- Empty: From states.md (Onboarding (6 steps)): n/a
- Error (retryable / not): From states.md (Onboarding (6 steps)):
POST /onboardingfailed: inline banner + Retry; answers kept · fatal: generic error, answers kept - Offline: From states.md (Onboarding (6 steps)): answers kept; submit queued; diagnostic needs network → "Connect to start your diagnostic"