top of page

Prototype:

A prototype is a representation of your product which you can use for troubleshooting during the initial stages of development. Through a prototype, the entire team can get an idea about the product’s flow and user experience, and how different elements interact with each other.

If you wonder what a prototype of Spotify looks like, here is a link

Types of the prototype - 

​

1. FEASIBILITY PROTOTYPES 

  • For prototyping new technology (ex. updated algorithm).

  • Engineer writes just enough code to see if it's feasible.

  • Helps understand technical risk, often related to performance.

2. LOW-FIDELITY USER PROTOTYPES

  • Essentially an interactive wireframe (doesn't look real). 

  • Created by interactive designers to test the workflow. 

  • Simulates process to identify usability issues early. 

3. HIGH-FIDELITY USER PROTOTYPES

  • Realistic looking, working simulation. 

  • Good for communicating a proposed product to stakeholders. 

  • Used in defensive user testing, not to see if they'll like it, but to learn if they won't. 

4. LIVE-DATA PROTOTYPES

  • Very limited implementation created by developers to actually prove it works. 

  • Has access to real data and is sent real live traffic. 

  • Hasn't been "productized" (no test automation, SEO, localization, etc). 

​

Tools for creating a prototype - Figma, Balsamiq, Atomic, Adobe XD, Framer X, InVision, UXPin, Webflow, Principle

bottom of page