Accessibility as a design quality bar
Accessible web design basics are contrast, focus, names, and reduced motion, treated as part of done. WCAG is the reference. A launch is not a certificate.
By Hanabi
Topic
Product Design
Interface decisions for founders shaping an early product.
When to prototype in Figma and when to design in the browser
Use Figma vs browser prototyping as a split: Figma for structure and options, the browser when type, motion, and real content decide the question.
By Hanabi
Onboarding that respects a busy user's time
User onboarding UX should start with the person's job and show a result before the tour. Accounts and tutorials can wait until that result is real.
By Hanabi
UX writing for teams that do not have a writer
UX writing for startups is the button, the error, and the empty state. Name the action, say what happens next, and cut the mood that hides the fact.
By Hanabi
How to run a design critique in a small team
A design critique process asks whether the work does the job. A founder can host it in thirty minutes if preferences wait until that question is answered.
By Hanabi
Empty states, errors, and the screens teams forget
Empty state design covers the blank screen, the first success, and the failure. Those three teach a product faster than a populated happy path.
By Hanabi
Designing dashboards people can scan
Dashboard UX design is a hierarchy: what changed, what needs a decision, and what can wait. Equal-weight charts make people hunt for the job.
By Hanabi
Fewer screens, a clearer product
Simplify a product interface by merging steps that share a decision and cutting screens that only pass people along. What remains should show the choice.
By Hanabi
How to design an MVP that feels finished
MVP design feels finished when one workflow is polished, including the empty screen, the error, and the success. A wide product with rough edges does not.
By Hanabi
Product design for founders who are also the first user
Product design for startups starts from a split: the founder's own use is evidence, and the next user's job is the spec. Habit is not the whole product.
By Hanabi