What Ben says is true, we have ways to go to make exporting certain pieces easier (spring values, maybe assets or state properties even). But we do look at Framer as a code-based 'design' tool. And a design mindset is very different then an engineering mindset, if that makes sense. Oversimplified example: when you're designing something, you're thinking about how it looks, feels and behaves. When you're engineering something, you're thinking about loading times, data storage, etc. Again: oversimplified, but we do think that while Framer is rooted in code, it is still very much a design tool you use to tinker around in code. Not so much produce it.
What Ben says is true, we have ways to go to make exporting certain pieces easier (spring values, maybe assets or state properties even). But we do look at Framer as a code-based 'design' tool. And a design mindset is very different then an engineering mindset, if that makes sense. Oversimplified example: when you're designing something, you're thinking about how it looks, feels and behaves. When you're engineering something, you're thinking about loading times, data storage, etc. Again: oversimplified, but we do think that while Framer is rooted in code, it is still very much a design tool you use to tinker around in code. Not so much produce it.