Prototyping and Design Solutions

Find here all solutions to create wireframes, make prototypes, add animations and interactions for your UX design, follow the latest design trends in 2023, etc.


New practical guides

RICE Prioritization: A Worked Example for Product Teams

Work through RICE scores for three rental-journey improvements, compare uncertain estimates, handle dependencies, and turn the ranking into a practical release decision.

Customer Switch Interviews: Understand Why People Changed Tools

Reconstruct a real customer switch with neutral questions, a decision timeline, and an invoice-tool example that turns research into a testable design hypothesis.

How to Write a Technical Spike Brief from a Prototype

Use a reservation example to turn an uncertain UI promise into a bounded technical spike, with scope, evidence, visible states and a clear next decision.

Progressive Disclosure UX: What to Show and What to Reveal

Design progressive disclosure with a report-export example: visible essentials, optional controls, persistent settings, keyboard behavior and recoverable errors.

How to Plan a UX Research Diary Study

Plan a UX diary study with neutral prompts, clear logging rules and a parcel-collection example. Handle missing entries and turn experience sequences into design questions.

User Story Mapping: Plan a Complete First Release

Build a user story map around a complete outcome. Use a repair-service example to choose a first release, expose dependencies, and explain deferred work.

Feature Request Triage: From Suggestions to Clear Next Actions

Triage feature requests with a worked queue: preserve evidence, separate problems from solutions, assign owners, and respond without promising a release.

Product Analytics Tracking Plan: Define Events Before Development

Create a product analytics tracking plan with clear event triggers, properties, owners, retry rules, and QA cases. Follow a practical learning-app example.

Comparative Prototype Testing: Compare Two Designs Fairly

Compare two prototypes with equivalent tasks, a planned presentation order, behavior notes, and a decision record. Includes a delivery-rescheduling example.

User Research Screener: Questions and Eligibility Rules

Build a user research screener with neutral questions, an eligibility table, access arrangements, and a worked class-booking example.

Booking Hold UX: Explain Expiry and Recheck Availability

Design booking holds with clear expiry, retained form entries, availability checks, and reliable confirmation states. Follow a practical studio-reservation example.

Duplicate-Record Merge UX: Choose Values and Review the Result

Design a duplicate-record merge that shows surviving field values, linked-record consequences, changed data, and a result the reviewer can verify.

Optimistic UI Updates: Make Pending Changes and Rollback Clear

Design optimistic UI updates that distinguish pending and confirmed changes, explain rejection, and preserve a newer choice when responses arrive late.

Query Builder UX: Group AND/OR Conditions and Preview Matches

Use four fictional accounts to compare two AND/OR expressions, then design condition groups, draft filters, applied results and a named saved view.

Scheduled Publishing UX: Versions, Approval and Failed Runs

Follow a fictional announcement from an approved version to a scheduled release, a later draft and a failed attempt, with clear replacement and cancellation rules.

Prototype Risk Matrix: Decide What to Test Before You Polish

Use a prototype risk matrix to prioritize uncertainty, choose a focused prototype slice, and set a clear stop or continue rule before polishing.

Prototype Branch Coverage: Check Alternate Paths Before Review

Audit the success, cancellation, failure, and recovery paths in an interactive prototype with a practical branch coverage checklist.

Prototype Decision Log: Turn Review Comments into Traceable Actions

Turn prototype review comments into traceable questions, evidence, decisions, owners, and versioned follow-up actions.

Prototype Content Stress Test: Design with Realistic Copy and Data

Stress-test a prototype with realistic short, long, translated, empty, and error content before handoff.

Prototype Review Scorecard: Decide What Is Ready for the Next Step

Use a prototype review scorecard to decide whether a flow is ready for research, implementation, or another design iteration.

A mobile bottom sheet offers a location choice above the screen it belongs to.

Design mobile bottom sheets with clear choices, apply and cancel behavior, readable content, and a predictable return to the underlying task.

A start date in September and end date in October form one reporting interval.

Design report date filters with clear start and end dates, apply and cancel behavior, useful validation, and shortcuts that explain the period included.

A shared component is mapped to replacement patterns while one existing use remains an explicit exception.

Retire a shared component with a consumer inventory, behavior mappings, a migration period, and clear removal criteria. Follow a worked message-banner example.

An Align center tooltip over a toolbar is shown beside a separate interactive Layout panel.

Decide when to use a tooltip, what to keep visible, and how hints should behave for hover, keyboard focus, touch layouts, and changing control states.

Two severity judgments are compared against the consequence of a saved request that has not been submitted.

Rate usability problems consistently, resolve reviewer disagreements with evidence, and separate severity from priority using a worked equipment-loan example.

A prototype portfolio story connects the designer's role, an appointment-change decision, and a focused interactive path for a reviewer.

Present a UX portfolio prototype with a clear role, design decision, and reviewer path. Check viewing access, protect project data, and prepare a useful fallback.

First-click study concept showing a materials question beside an arts-course page with practical information and reservation entries.

Plan a first-click test with a neutral task, a realistic starting screen, clear click regions, and a practical way to turn observations into design changes.

Command-palette concept distinguishing opening a project from reviewing a consequential archive action.

Design a command palette with clear action scope, useful search results, predictable keyboard behavior, and deliberate steps for consequential commands.

An asset register moves from an export request to a retrievable document while the user continues working.

Design a background export flow with clear job status, a persistent exports list, useful failure recovery, and download expiry that users can understand.

A speaker proposal with staged sections and a change from workshop to talk carried through to its review page.

Plan multi-step forms with meaningful stages, retained answers, conditional questions, useful errors, and a review step that keeps submission clear.

Saved and proposed role cards show Comment becoming allowed while View, Delete, and the selected-collection boundary stay unchanged.

Design a roles and permissions UI with clear action scope, inherited restrictions, change reviews, and save states. Follow an asset-catalog role example.

Mockitt brand and website update: formerly Wondershare Mockitt, now at mockitt.com.

Wondershare Mockitt is now Mockitt at mockitt.com, bringing prototyping, UI design, whiteboards, flowcharts, AI presentations, and Mockitt AI together.

Customer journey map connecting equipment-booking stages, evidence and a next design action

Create a customer journey map from research evidence. Define the scope, map touchpoints, compare an equipment-booking example, and choose useful next actions.

Service blueprint and customer journey map compared across an event-registration experience

Compare a service blueprint with a customer journey map. Learn what each view answers, map one event in both formats, and choose the next research or design action.

Library service cards arranged into tentative groups, with one card left between categories to show an unresolved relationship.

Prepare a card-sorting study, write clear content cards, capture independent groupings, and turn the evidence into category proposals with a library example.

Named surface, text and action swatches connected to a pottery-class booking card and its spacing.

Build a small design-token vocabulary for color, typography and spacing, map roles to components, and manage themes and handoff with a worked example.

A short path from creating a reading list to adding its first book, with an invitation shown as a later task.

Plan an onboarding UX flow around a useful first task, with required setup, optional routes, contextual help, interrupted sessions and a review example.

An export dialog connected to name, focus and feedback annotations, with a route returning to its opening control.

Document accessibility annotations for names, roles, focus and status feedback, with an export-dialog example and practical design handoff checks.

Employee-help signposts with a route to a laptop charger and a detour showing a return from the wrong category.

Plan a tree test with neutral tasks and clear destination rules, interpret direct and indirect paths, and use the findings to improve category labels.

A K-24 catalogue task path passes an ambiguous Resources sign toward a clearly labelled Dimensions destination.

Run a cognitive walkthrough with a defined novice task, four action-level questions, a worked prototype example and an honest plan for follow-up research.

An English download action and a longer German translation connected to a shipping-document context tag and flexible text frame.

Prepare a UI localization review with complete strings, translator context, locale-state examples and clear design, language and implementation checks.

A parcel reference with collection code 7246 inspected beside a narrow example screen where that code is missing.

Run design QA against an agreed prototype: match the build and state, report reproducible UI differences, triage findings, and verify the correction.

Three fictional supplier records with varied content, a missing phone value, and S-102 linked to a matching detail view.

Create consistent prototype test data with realistic records, long names, missing values, empty states, and reset instructions without using customer exports.

A closed reading-room door, personal and work identity tokens, and an access-request envelope waiting in a Pending tray.

Design access-denied screens that explain account choice, permission requests, pending decisions, and recovery without exposing private information.

An exhibit-draft card beside Archive and Trash drawers, with a restore path and a separate permanent-deletion slot.

Design archive, delete, and restore flows with clear consequences, recovery locations, missing-folder handling, and useful confirmation messages.

Practice task moves from third to second in a four-module course outline, with the remaining modules preserved.

Design list reordering with clear destinations, click and tap alternatives, useful feedback, and recovery. Review a concrete course-order example in Mockitt.

An equipment-loan request moves from requested changes to a revised handover detail and an approval decision.

Design approval workflows with clear decisions, revision history, requested changes, resubmission, and current status. Follow a two-role equipment-loan example.

A recurring London meeting stays at 16:00 while the New York time changes from 11:00 to 12:00 and back across three dates.

Design time zone scheduling with clear local times, recurring-event rules, daylight-saving exceptions, and a London–New York worked example.

Eight workspace projects split into three editable projects and five retained read-only projects at a scheduled plan change.

Design a subscription downgrade flow that explains effective dates, project limits, data access, scheduled changes, and recovery before users commit.

A project invitation moving from a sender to a recipient, with a reviewer role and a wrong-account recovery path.

Design a team invitation flow with clear roles, pending states, account-mismatch recovery, expiry, resend, and a useful destination after acceptance.

Three campaign files with ready, interrupted, and oversized states, each paired with an appropriate next action.

Design file upload UX with clear per-file progress, honest completion states, specific errors, and recovery that preserves files already uploaded.

A supplier CSV with two highlighted field errors beside a review-before-import panel.

Design a CSV import flow with clear field mapping, row-level errors, a recoverable review step, and an explicit rule for what gets imported.

Three selected campaign assets split into two archived items and one protected item that remains unchanged.

Design bulk actions that explain what is selected, what an action affects, and how users recover when only some selected items succeed.

A document draft with saving, saved and failed-save indicators, with publishing shown as a separate action.

Specify autosave feedback that separates local edits from confirmed saves, handles failed requests, and keeps saving a draft distinct from publishing.

An opportunity solution tree connects a training outcome to an approval-information need, three alternatives and a next test.

Build an opportunity solution tree with a worked training-platform example, separate user needs from feature ideas, and choose an assumption to test.

Research notes connect to an owner-clarity theme and a proposed handover panel, while a separate export constraint remains visible.

Work through a research synthesis example that links observations to themes, preserves contradictory evidence, and produces a specific design decision.

How to Run a Product Prototype Feedback Workshop

Learn how to run a product prototype feedback workshop with focused tasks, neutral prompts, observation notes, and decisions your team can test.

Prototype Acceptance Criteria: A Practical Product Design Checklist

Use this practical prototype acceptance criteria checklist to review flows, states, accessibility, content, and handoff readiness.

AI Prototype Prompts: Patterns for Turning Requirements into Screens

Use reusable AI prototype prompt patterns to turn product requirements into reviewable screens, states, and flows with clear human checks.

User Flow vs Wireframe: What to Create First

Compare user flows and wireframes, decide what to create first, and connect both artifacts into a testable product prototype.

Design Review Questions for Product Teams

Use focused design review questions to assess users, flow, accessibility, feasibility, evidence, and the next product decision.