Skip to content
Limin Zheng

Design & Presentation

UI/UX prototypes

Turn a bounded flow or page idea into a reviewable prototype.

Choose this when
Choose this to review screen/flow design and states; choose Website implementation & browser tools for a working web utility that processes actual inputs.
Scope unit
A bounded user journey, screens and states
Possible delivery format
Prototype link or HTML/ZIP package

A brief-first task can still need diagnosis: unreadable scans, an existing design system, or private authenticated journeys.

Prepare a brief →

You send · You receive

What to send

  • Target users and key tasks
  • Pages, primary flows, edge states and product constraints
  • Target screens, references and existing design system
  • Whether you need a clickable prototype or a specific native design format

Start by describing the materials you already have; missing details can be added when we agree the scope. Before work begins, we will confirm the materials, permissions and working conditions needed for your specific task.

Possible outputs

  • Page/flow designs and agreed interaction prototype
  • HTML prototype or agreed design files
  • States, responsive behavior and developer handoff notes

Key check

Agreed screens, states and clickable journeys are demonstrable.

Verifiable acceptance · 3
  • Agreed primary flow can be walked through
  • Scoped loading, error or permission states appear
  • Critical layouts are checked at specified widths

Hypothetical brief & output structure

Illustration · hypothetical

Illustrative example — not a completed client order

The request

Design a clickable three-screen registration and onboarding flow, including errors.

Sample artifacts

  • onboarding-prototype/clickable preview
  • flow-notes.pdfscreen and state notes

File names are illustrative

Other tasks of this kind

  • Make a clickable mobile prototype for personal spending, including empty and error states.
Output structure / test path

Test flow: start → form → finish; include scoped empty/error/loading states

Write a brief from this example →

Scope boundaries

Prototype is not production app; native Figma components/design systems require explicit scope and verification.

Not included by default

  • Production backend, live payments or user accounts
  • An entire design system unless separately scoped
  • Promising native Figma components without validation

What affects the quote

Pages, interaction states, responsive targets and delivery format.

Actual project references

  • Pianology ↗

    Independent product

    Product definition and building experience; does not guarantee current availability or paying users.

  • AllGood ↗

    Independent product

    Privacy-first product structure and delivery practice, not privacy or security certification.

Self-directed work and published projects demonstrate relevant practice. They are not paid-client delivery records or guarantees for this task.

Start with a short note

Three answers are enough. I will reply with what else is needed and whether a diagnosis comes first. You get a quote before any work starts.

Prepare a brief →

UI/UX prototypes

Start with a short note

Three answers are enough. I will reply with what else is needed and whether a diagnosis comes first. You get a quote before any work starts.

What to send
  • Target users and key tasks
  • Pages, primary flows, edge states and product constraints
  • Target screens, references and existing design system
  • Whether you need a clickable prototype or a specific native design format
Illustration · hypothetical

Illustrative example — not a completed client order

The request

Design a clickable three-screen registration and onboarding flow, including errors.

Example inputs

  • User goal, three-screen scope and approved copy
  • Breakpoints, references and important error states

To start, it helps to mention

  • Which user flow and roughly how many screens/states should be demonstrated?
  • Is a clickable prototype enough, or is a native editable design file required?

Confirm before work begins: Main journeys, permitted design system, target devices and acceptance path

Public/de-identified information only. Private access requires separate authorization.

Open email draft →

Preview the text
Services brief — V03 UI/UX prototypes

First contact does not require a complete specification. Unknown fields may be blank or marked unknown.

What do you want to end up with?


What do you already have?


When do you need it? Any budget range?

Select and copy the brief manually if scripting or clipboard access is unavailable.

Public email is a contact starting point. This site has no booking, payment or file-upload service. zhenglimin.design@gmail.com

← Back to category
Prepare a brief →