Personas¶
Personas represent the archetypal users of Loryth. They guide product decisions by grounding features in real user needs, constraints, and motivations.
How to Use Personas¶
- Feature prioritization: Check which personas benefit from a proposed feature
- User stories: Reference personas by name in "As a..." statements
- PRDs: Link target personas in the requirements document
- Design reviews: Ask "Would {persona} understand this?" during UI reviews
Persona Summary¶
| Persona | Priority | Technical Comfort | Self-Hosting Reality | Primary Services |
|---|---|---|---|---|
| The Self-Hosting Tinkerer | Primary | Expert | Bare-metal Docker on home server | KB, Wallet, Issues, Grocery, AI |
| The Mindful Planner | Primary | Moderate | Managed hosting (DigitalOcean/Railway) | Journal, Grocery, Wallet, KB |
| The Household Coordinator | Secondary | Low | Someone else set it up; mobile only | Grocery, Wallet, Issues, KB, Notifications |
| The Plugin Developer | Tertiary | Expert | Local dev environment only | AI, KB, Issues, CMS, all APIs |
Coverage¶
These four personas collectively:
- Span the technical spectrum from non-technical mobile user to OSS contributor
- Cover all self-hosting realities from bare-metal to "my partner set it up"
- Touch all 9 services across their combined usage
- Match the vision doc's audience: Primary personas align with "privacy-conscious individuals with technical interests"; the Secondary persona represents the "broader audiences" expansion goal