Aglet

Verify quiet-hours delivery and in-app visibility

Verification should prove that a person can tell whether an event is delayed, available for review, or outside the current channel. Test quiet and normal windows, one time-zone boundary, and the in-app path. Keep platform summary or focus behavior outside the claim when unobserved.

Check whether the outcome improved

  1. Check normal timing

    Trigger or review an event outside quiet hours and confirm timestamp, channel, urgency, and in-app visibility align. Record the expected action and label so the normal path is a meaningful control.

  2. Check deferred timing

    Use an event inside the quiet window and verify the product explains delay, retains the event where promised, and resumes or surfaces it at the documented point. Test one time-zone or daylight boundary when in scope.

  3. Review recovery and copy

    Inspect settings, history, badge or status, narrow layout, and a changed urgency path. State tested channels and platform limits. Leave the verification partial if external delivery or Focus behavior cannot be directly observed.

What to carry forward

Verification passes when timing labels, in-app visibility, and event state agree for tested quiet and normal paths. If platform or time-zone coverage is partial, document it. Immediate delivery is not a pass when it defeats the person’s stated quiet-hours choice.

Technical background: Android developer documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow