Uwarp

UX, UI, and web design checklists

Tool powered by . Uwarp embeds the public checklists; sign-in, Figma plugin, and data handling are on checklist.design.

UX checklist, web design checklist, and UI component reviews on checklist.design—website, flow, and brand lists. Figma plugin on publisher site.

What is Checklist Design?

Checklist Design at checklist.design is a library of practice-focused lists for UX, UI, and web product work—organized by website screens, UI components, user flows, topics, and brand. Teams use it as a website design checklist before launch, a UX checklist during critique, and a web design checklist for marketing and app surfaces. The site is credited to George Hatzis on the public pages and is served via Framer. Uwarp embeds https://www.checklist.design/ so you can review lists next to other tools; we do not operate accounts, the Figma plugin, or any beta products mentioned on the domain.

Popular checklist searches

These intents match how people find checklist.design. Open the embed, pick a list, and walk your real UI states.

  1. Website design checklist: Page-level passes for home, pricing, cart, login, and blog—what makes a good website checklist for shipping quality.
  2. UX checklist and UX design checklist: Cross-cutting UX review items for flows, feedback, and recovery paths before you hand off to engineering.
  3. Web design checklist: Marketing and product web surfaces: navigation, content hierarchy, and goal paths in one repeatable pass.
  4. Design checklist for components: Checklist UI for buttons, modals, tables, toasts, and icons—states, spacing, and edge cases named clearly.
  5. Website creation checklist: From signup to checkout: flow lists that catch missing steps when you stand up a new site or feature.
  6. Topics, brand, and login patterns: Responsiveness, dark mode, copy, voice—and focused pages such as login when you audit auth UX.

What checklist.design offers

Structured lists for common digital product surfaces.

  1. Website checklists: Screen-level reviews for cart, login, pricing, search, and other high-traffic pages.
  2. Component checklists: Cards, drawers, modals, tables, and form controls with state and feedback prompts.
  3. Flow checklists: End-to-end paths such as checkout, password reset, and media upload with error handling.
  4. Topics and brand lenses: Cross-cutting guidance on responsiveness, dark mode, UX copy, logo, and tone.
  5. Figma plugin: Use the advertised Figma plugin from checklist.design to run lists in the canvas.
  6. Optional saved progress: Sign in on the publisher site when you want to save checklist progress—see Privacy on checklist.design.

How to use this embed on Uwarp

A practical review loop for teams.

  1. Pick the right scope: Choose website, component, or flow lists based on whether you are shipping a page, a system, or a journey.
  2. Open staging or production: Walk real loading, empty, success, and error states—not only static mockups.
  3. File gaps with context: Link each miss to a URL, screenshot, and checklist item so fixes stay traceable.
  4. Re-run after fixes: Repeat the same list on release candidates to catch regressions.
  5. Extend with your standards: Add accessibility, legal, and localization requirements your org requires beyond the base lists.
  6. Open full tab if needed: If the iframe is blank, open https://www.checklist.design/ directly—Framer apps can block embeds.

Tips for checklist reviews

Get signal without box-ticking alone.

  1. Pair with user research: Checklists complement usability tests; they do not replace them.
  2. Run accessibility in parallel: Use your WCAG or internal a11y checklist in the same sprint.
  3. Share lists in handoff docs: Link `/checklist-design` so design and engineering use the same vocabulary.
  4. Read Privacy before login: Review About and Privacy on checklist.design before using a work email to save progress.

Who this is for

People who own quality before a release or redesign.

  1. Product designers: Standardize pre-release self-review and design QA with developers.
  2. Engineers: Shared language for states, flows, and component edge cases.
  3. Design leads: A default review baseline in team handbooks.
  4. Agencies: Onboard designers to common web patterns across client work.

Why open Checklist Design on Uwarp

Public checklists beside your other references.

  1. Stable Uwarp path: Link `/checklist-design` in docs; attribution points to checklist.design.
  2. Shared vocabulary: Named sections align critique with real product surfaces.
  3. Uwarp does not operate the product: Accounts, plugin, and hosting are on checklist.design—not Uwarp.

Frequently Asked Questions

Have questions? We have answers.

Related tools

More tools from Educational.

View all Educational