You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- An **Analytics Event Parameter** must not contain user-authored text, direct identifiers, tokens, raw exception strings, request bodies, or response bodies.
118
134
- A **Product Usage Event** uses a stable snake_case name and includes a schema version.
119
135
- A changed **Product Usage Event** meaning requires a new event name or schema version.
136
+
- A **Schedule** has a **Preparation** whose **Preparation Duration** contributes to preparation-start timing.
137
+
-**Preparation Duration**, move time, and **Schedule Spare Time** are distinct schedule timing inputs.
120
138
- User-facing copy should call a scheduled notification a **Schedule Notification**, not an **Alarm**, unless it opens an OnTime screen without the user first tapping a notification.
121
139
- The profile setting for upcoming schedule preparation delivery should be called **Schedule Notification Setting**.
122
140
- On iOS, user-facing copy may say **Alarm** only when OnTime can deliver an **iOS AlarmKit Alarm**.
- "Time Sensitive" was too platform-specific for default user-facing status; resolved: fallback iOS delivery should be called notification.
181
199
- "Status label" was ambiguous across platforms; resolved: Android uses precise notification or notification status, while iOS uses alarm status only for **iOS AlarmKit Alarm**.
182
200
- "No scheduled alarm" was too capability-specific for an empty state; resolved: use **No Scheduled Notification** across platforms.
201
+
- "Total duration" was ambiguous between **Preparation Duration** and the broader preparation-start timing calculation; resolved: **Preparation Duration** is steps only, while move time and **Schedule Spare Time** are separate inputs.
0 commit comments