Tip-kind-aware UI affordances #52

Closed
opened 2026-04-13 14:35:37 +00:00 by alvis · 1 comment
Owner

The tip page must behave differently per kind:n- todo → tap = done (completes at provider via integrations.act)n- advice → tap = acknowledge; long-press = save for latern- ambient (M2+) → fades, no action requirednnLong-press menu always offers snooze / dismiss. Every action emits a feedback event.

The tip page must behave differently per kind:n- `todo` → tap = done (completes at provider via `integrations.act`)n- `advice` → tap = acknowledge; long-press = save for latern- `ambient` (M2+) → fades, no action requirednnLong-press menu always offers snooze / dismiss. Every action emits a feedback event.
alvis added this to the M0 — Prototype milestone 2026-04-13 14:35:37 +00:00
alvis added the webdesign labels 2026-04-13 14:35:37 +00:00
Author
Owner

Closing: premature with only one tip kind (todoist). Superseded by new tip-kind system issue in M2 that covers AI-generated tips + todoist + advice.

Closing: premature with only one tip kind (todoist). Superseded by new tip-kind system issue in M2 that covers AI-generated tips + todoist + advice.
alvis closed this issue 2026-04-16 15:23:03 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: alvis/oO#52