Over the last few months, we’ve been speaking with product designers at some of the world’s most exciting companies to understand their processes and pain points.
Two key ideas came up again and again:
- When designers and engineers are on the same page, we’re able to deliver better experiences for our users.
- When we integrate real content, real data and real use cases into our designs, we make better decisions, faster.
These findings didn’t surprise us. We’re certain that the best product decisions happen when designers are able to communicate seamlessly with collaborating engineers, product managers, writers, marketers, salespeople; everyone.
And design tooling has made leaps and bounds in this direction over the last five years. The design process has become more accessible and understood, with collaboration living in the heart of our toolkit.
But for all the gains in collaboration, there are still hard limits on what we as designers are able to produce within our everyday design tool. Without meticulously sewing together prototypes or writing code, the limit is how true-to-life our designs can actually be.
The consequence of this is a vast gap between the static designs we produce and the code our users actually interact with.
We want to empower designers with access to tools that typically require an engineer's hand to build.
But rather than pushing designers into coding tools, what if we pull the power of code into Figma? The layer beneath the interface. The logic and content that drives a product’s behaviour.