Practical reference library
Implementation contracts for onboarding, contextual support and in-app engagement.
Guide 01
Define checklist completion from the underlying product action, not merely a click on the checklist item. Record the user or account, task identity, completion event and checklist version. The interface should reflect the stored state and recover correctly after refresh, sign-out or a change of device.
Read the guide →Guide 02
Test a product tour without a mouse from entry to dismissal. Verify that the trigger is reachable, the current step is understandable, controls work from the keyboard and focus returns to a sensible place when the tour ends. Choose modal or non-modal behavior deliberately; not every tour should trap focus.
Read the guide →Guide 03
Trigger in-app support from a specific unresolved problem, with an eligibility rule, cooldown and clear next action. Use the current page and failure context to offer relevant help. Avoid showing the same prompt repeatedly after dismissal or claiming a problem is solved merely because the help widget was opened.
Read the guide →Guide 04
A daily streak needs an explicit qualifying action, day boundary, timezone policy and recovery rule. Count a qualifying action once for the relevant day, handle delayed events deliberately and explain resets to the user. Test travel, daylight-saving changes and repeated events before attaching rewards to the streak.
Read the guide →Guide 05
An onboarding experiment exposure log connects assignment, actual component display and the later value event. Store these as separate stages. A user assigned to a tour may never see it, and a user who sees it may not activate. Keeping the stages distinct makes implementation failures and outcome analysis easier to diagnose.
Read the guide →