Principles
Design principles aren’t rules — they’re answers to recurring arguments. When a decision could go either way, these are the tiebreakers.
1. Structure earns its keep
Use structured UI where it genuinely beats conversation.
For stock tracking and shopping, users need a stable list to edit against. Tapping a +/− button to adjust quantity, or checking a checkbox while grabbing items off a shelf, is faster and less error-prone than describing the action in natural language. The structure is the feature.
When it applies: Any time someone proposes replacing a list, form, or control with a conversational or AI-driven flow — ask whether the structured version actually takes longer or is harder to use. If not, keep the structure.
2. Progressive disclosure
Start with the minimum. Reveal depth only when the user asks for it.
Complex fields belong in an advanced section, collapsed and disabled by default. The onboarding template is the clearest example: users see a simple, friendly setup flow — the full data model is there, but it doesn’t get in the way until it’s needed.
When it applies: Any time a form, page, or component is getting long or overwhelming. Ask what a first-time user actually needs to complete their task. Move everything else behind a toggle, accordion, or secondary action.
3. Earn every field
Every input, label, and metadata field must justify its cognitive cost.
The app can track a lot about each item — unit, dual unit, expiry, vendor, tags, shelf, recipes, notes. That’s powerful for users who want it. But each field costs attention, even when empty. A field that most users never fill in is a field that makes the form feel harder for everyone.
When it applies: Before adding a new field, ask: does this make tracking or shopping meaningfully easier? If it’s edge-case information, it belongs in the advanced section. If almost no one uses it, consider removing it.
4. Home-worthy
The app should feel as comfortable and unpretentious as your own kitchen.
The target mood is warm, casual, efficient, and neat — the way a well-organized pantry feels, not the way an enterprise dashboard feels. This applies to visual design (soft colors, readable type, no unnecessary chrome) and to copy (friendly, direct, occasionally playful — never formal or corporate).
When it applies: When evaluating any design decision — layout density, copy tone, color use, animation — ask: does this feel at home, or does it feel like a spreadsheet? A spreadsheet answer is usually a sign to simplify.