From software problem to a clear next step.
Choose a topic and what you need to do next. Add a search phrase to find a specific problem.
Browse 20 topics
Explore the playbooks
1500 guides · Page 60 of 60
-
Triage notification permission timing before showing a prompt
Triage notification permission timing by comparing user intent, feature context, rationale, prompt result, and the recovery path after decline.
-
Prioritize notification permission timing with user intent
Prioritize notification permission timing by weighing prompt interruption, feature value, denial recovery, platform context, and the smallest informed opt-in change.
-
Investigate notification permission timing through user journeys
Investigate notification permission timing by tracing feature context, user gesture, rationale, permission result, and later settings recovery.
-
Verify notification permission timing and denial recovery
Verify notification permission timing with page-load, contextual, and explicit opt-in paths, plus allow, deny, dismiss, and settings recovery.
-
Learn from notification permission timing and prompt fatigue
Learn from notification permission timing by recording user context, prompt outcomes, and one reusable opt-in review for future notification features.
-
Triage notification channel fallback before adding another delivery path
Triage notification channel fallback by comparing event state, channel preference, failure, in-app visibility, and the risk of duplicate delivery.
-
Prioritize notification channel fallback with less duplicate noise
Prioritize channel fallback by weighing missed events, duplicate interruptions, user preference, durable in-app visibility, and the smallest alternate path.
-
Investigate notification channel fallback across delivery states
Investigate notification channel fallback by tracing preferences, channel state, attempts, alternate delivery, in-app history, and duplicate identity.
-
Verify notification channel fallback without duplicate alerts
Verify notification channel fallback with preferred success, muted channel, failed delivery, in-app history, alternate paths, and duplicate guards.
-
Learn from notification fallback and duplicate delivery choices
Learn from notification channel fallback by recording failure paths, user preferences, durable state, and one reusable delivery review check.
-
Triage notification delivery retry visibility before changing status copy
Triage notification delivery retry visibility by separating event existence, channel acceptance, delivery confirmation, retry, and user-visible status.
-
Prioritize notification retry visibility with truthful status
Prioritize retry visibility by weighing repeated user actions, missed context, event durability, channel uncertainty, and the smallest status improvement.
-
Investigate notification retry visibility from event to channel
Investigate notification retry visibility by tracing event state, attempts, channel confirmation, retry timing, in-app history, and user-facing status.
-
Verify notification retry status and recovery copy
Verify notification retry visibility with accepted, queued, delivered, failed, and retried events, durable history, copy, and safe next actions.
-
Learn from notification retry visibility and repeated actions
Learn from notification retry visibility by recording event states, channel uncertainty, user recovery, and one reusable delivery-status review.
-
Triage notification deduplication windows before suppressing repeats
Triage notification deduplication windows by comparing event identity, resource, state, elapsed time, channel, and whether a second message represents real change.
-
Prioritize notification deduplication with preserved change
Prioritize notification deduplication by weighing alert noise, missed state changes, event identity, channel overlap, and the safest bounded window.
-
Investigate notification deduplication windows with event traces
Investigate notification deduplication windows by tracing identity, state, version, elapsed time, channel, grouping, history, and latest action.
-
Verify notification deduplication across retries and state changes
Verify notification deduplication with retries, cross-channel copies, real repeated events, time boundaries, retained history, and preserved actions.
-
Learn from notification deduplication windows and hidden updates
Learn from notification deduplication windows by recording identity boundaries, legitimate repeats, retained history, and one repeatable review check.
-
Triage notification copy truncation before shortening messages
Triage notification copy truncation by comparing event, actor, resource, action, preview, viewport, and the context a person needs to choose safely.
-
Prioritize notification copy truncation with preserved context
Prioritize notification copy truncation by weighing wrong openings, missing event context, screen width, action labels, and the smallest safe copy change.
-
Investigate notification copy truncation across layouts and previews
Investigate notification copy truncation by tracing source text, rendering limits, localization, accessible name, preview, and destination context.
-
Verify notification copy across narrow screens and previews
Verify notification copy truncation with event, actor, resource, action, narrow layout, preview, localization, and accessible text that retain essential context.
-
Learn from notification copy truncation and missing context
Learn from notification copy truncation by recording lost meaning, layout boundaries, and one repeatable content review for future notification messages.