A short letter to explain why we’re building Simili.

1min read

Creating software involves at a basic level three things: design, engineering and ideas.

In the early stages, shipping a product usually follows this sequence:

<aside> <img src="/icons/sync-reverse_gray.svg" alt="/icons/sync-reverse_gray.svg" width="40px" /> Ideas → Design → Engineering → Product

</aside>

Over the past years, people working on software have put a lot of effort into translating design to engineering. Design systems like Google’s Material Design and Shopify’s Polaris were born out of symplifying that translation.

<aside> <img src="/icons/checkmark_green.svg" alt="/icons/checkmark_green.svg" width="40px" /> Design → Engineering

</aside>

Yet, we’ve spent very little time on bridging the gap between ideas, and design. Between the moment of ideation and of realization.

<aside> <img src="/icons/circle-dashed_lightgray.svg" alt="/icons/circle-dashed_lightgray.svg" width="40px" /> Ideas → Design

</aside>

The plan is to change that. We believe there is a solution — and it’s time to build it.

Last updated on May 3 2024