What Changes When Designers Build Products Themselves
1. When you can build directly, scope setting changes first
- When you are designing only on the screen, it is easy to keep adding features, but once you actually implement them, the cost and weight of every idea immediately become visible.
- What makes the product experience clear is not what you add, but what you remove.
- Cut out earlier the features that are interesting but do not contribute to the core experience.
- Instead of reducing the spec after design, you design the scope itself from the beginning.
2. Figma becomes the starting point for validation, not the finished product
- A design that seemed natural on a static screen raises different questions once you make it work in practice.
- As you check the flow after a click and even the failure states, the role of the prototype changes.
- Conditions hidden behind the screen, such as incorrect input, no data, and exceptional cases, come into view.
- The prototype becomes a tool for questioning and fixing the design itself, rather than a deliverable for explanation.
3. Development constraints become a common language for collaboration
- When you directly experience API errors, large images, test data, and Docker and deployment issues, technical constraints no longer remain abstract words.
- The earlier you understand implementation reality, the more concrete your conversations with developers become.
- Rather than stopping at being told whether something is possible, you adjust priorities and order while considering constraints.
- You can discuss more quickly with the team the problems that arise when design meets the real environment.
4. Even as things get faster, design judgment is not automated
- AI can quickly create working outputs, but it does not guarantee consistent details or a good experience.
- Speed and completeness are different, and deciding what is good still remains with the designer.
- You need to find and correct awkward results based on taste and context.
- In the end, the hardest decision is closer to what not to make than to what to make.
