End-to-end flows, not isolated primitives
Patterns show how real products compose multiple mechanics into one launchable experience. Use these pages after the concept layer, when your team wants a working blueprint instead of a definition.
Best forImplementation planning
What you getSDK + API + UX flow
AudienceEngineers + technical PMs
Key takeaways
Quick read- Patterns are cross-cutting by design: they should compose multiple primitives rather than re-explain one primitive in isolation.
- These are the best pages to hand to an engineer after product and PM have aligned on the mechanic.
- Every pattern should link out to the underlying concept pages for depth and to the API reference for exact request shapes.
Library
Browse implementation patterns
Guide cluster
Activation and habit
2 playbooks
Guide cluster
Campaigns and launches
2 playbooks
Still at the planning stage?
Start with the concept layer
If your team is still deciding how a mechanic should behave, the concept pages are the better first stop. Come back here when you want a blueprint to ship.
1 brief to align the room2 mechanics max in version one
What happens next
01
Pick the mechanic
Choose the smallest working system for the brief.
02
Launch without rebuilds
Configure rules and rewards in one place.