Phase: No-Code Prototyping Editor

Phase is a digital design platform that allows designers to prototype animations and micro-interactions, focused on UI/UX design and animation tools for product designers.

Role
Product Designer
Team
Project Manager
Research Engineer
Front-end Engineer
QA Engineer

Challenge of Editor Tools

Unlike typical products with linear workflows, as an editor, Phase allows users to work in any order they choose. Every new feature impacts dozens of existing tools, creating complex dependencies.

The challenge is maintaining system-wide compatibility while supporting unlimited creative freedom.

Design Process

1

User requirements discover

Conduct research to explore and identify user requirement. Define priorities and discuss the task scope with the Product Manager. Document serve as source of truth for the design goals.

[User Requirement]
Conduct research to write precise user requirements
[User Story]
Break down user requirements into product usage scenarios
[Priority]
Define priority of each scenario's for development resource prioritization.
[Complexity]
Record dependencies when scenarios are related to other functions.
[Future]
After discussing with the product team, we'll create a Future section for upcoming functions

2

Design handoff

Create UI mockups and user flows, clearly marking all technical details. Ensure that anyone can understand what needs to be done and what has been changed, regardless of their role.

For each new UI module handoff
User flow & Prototype

3

Rules documentation

In addition to defining interaction logic rules within Figma, a comprehensive functional specification document is also created. This document outlines boundary conditions and rules for all scenarios of user interactions with the feature, making it easier for engineers to implement during development.

[Rules & Choice]
Rules are written as a standalone sentence, ensuring rules are independent to facilitate implementation and verification by engineers
[Example & Note]
When rules are complex, add additional notes or examples to help understand the designer's requirements
[Reason]
Each rule includes the design rationale to help engineers understand or track the reasoning behind discussions
[Complex Choices]
When we have multiple solutions and find it difficult to choose, we will discuss them and document all the options and the reasons for our selection.

4

QA Gherkin review

After handing over to development, all functional specifications will be synced up with QA engineers to enable them to draft Gherkin scenarios. Designers will review the Gherkin to ensure all described conditions and use cases are thoroughly tested.

Gherkin is a script for testing.

Selected works

Prototype Mode in Phase
Trigger area precisely follows the actual path, rather than the element's bounding box
Seamlessly preview the prototype on mobile devices through a QR code scan
One-click share to invite collaborators

Takeaways

Working at Phase—a fast-paced startup with constant iteration—has significantly strengthened my systems thinking abilities. Designing editor features presents unique challenges that go beyond typical product design.

Each project taught me to see beyond individual features and consider the entire ecosystem, making me a more strategic and comprehensive designer.

Other Work