# Build your prototype

> [!WARNING]
> **Preview:** This Pre-GA product is subject to the "Pre-GA Offerings Terms" in the [Service Specific Terms](https://cloud.google.com/terms/service-terms#1), offered "as is" with limited support. See the [launch stage
> descriptions](https://cloud.google.com/products#product-launch-stages) for more details."

The key steps in the prototyping phase of developing
Natively Adaptive Interfaces include selecting ideas, determining prototype types, and
iterating based on feedback.

1. Select the ideas to prototype.
   - Review outputs generated in the [*Define and prioritize
     phase*](https://developers.google.com/natively-adaptive-interfaces/design/establish-viewpoint): look back at the features generated.
   - Identify promising features: choose one or a few ideas that seem most promising, feasible, and aligned with the insights gained from the [*Investigate phase*](https://developers.google.com/natively-adaptive-interfaces/design/define-problem-statement) and [*Define and
     prioritize phase*](https://developers.google.com/natively-adaptive-interfaces/design/establish-viewpoint). You don't need to prototype every single feature.
   - Focus on key aspects: decide which specific functionalities or aspects of the features you want to test. You might prototype different parts of the same feature separately.
2. Determine the type of prototype needed.
   - Consider the goal: determine what you want to learn from this prototype. For example, write down the questions you'd want the prototype to answer.
   - Choose the right fidelity to match your learning goals: prototypes can range from very low fidelity ---quick and rough---to medium fidelity---more detailed but still not fully functional.
3. Build just enough.
   - Keep it straightforward and fast: the goal is speed and learning, not perfection. Avoid getting bogged down in details or aesthetics.
   - Focus on functionality for testing: build only the elements necessary to test the specific aspects you've identified.
   - Use available resources: utilize readily available materials and tools to keep costs and time investment low.
   - Don't polish: resist the urge to make it look perfect. The rawness encourages honest feedback about the core concept.
4. Co-create these prototypes.

   Co-design participants should be actively involved in refining and
   building prototypes, bringing their practical knowledge to the
   forefront. For these co-design participants, providing feedback on the
   features being developed is a practical extension of the co-design
   process itself. In addition to providing first-person input, they can
   also help interpret feedback from other participants and suggest
   improvements.
5. Simulate user interactions.

   Test prototypes as your target users would, simulating any modality
   restrictions if necessary. For example, close your eyes to experience a
   video by listening to the automatic audio descriptions that describe the
   visual information in the video).

   > [!NOTE]
   > **Note:** Use these simulations as a secondary means of gathering data, with the primary means being feedback sessions from target users. Simulations can supplement, but not replace, the feedback of target users.

6. Iterate.

   Using the feedback and insights you've gained, refine the design using as
   many cycles of prototyping and testing as you need.

## What's next

- [Key terms](https://developers.google.com/natively-adaptive-interfaces/guides/key-terms)
- [Case study: Build your prototype](https://developers.google.com/natively-adaptive-interfaces/video/build-refine)