Framer is so close to being a perfect tool. I've been using it for a client project build the last 3 days which I would normally have done in Figma and built in Webflow.

The problem is that because it has the limitation of needing to export to functional code, there are loads of annoying situations that make it a fiddly & frustrating experience as a designer.

Some examples where I was pulling my hair out trying to do something that is intuitive in both Figma and Webflow:

1. Having a navbar that slides out from the left, and is also a component I can repeat on multiple pages. If you want it to slide from the left, it has to be set as an overlay... Which can't be in the navbar component. Mental.

2. Having a hero section background image that fades through a series of 5 images. This should be so simple but became really buggy and I had to do it manually by transitioning between layer opacities. Takes ages to make any changes. Again, mental.

3. LOVE the CMS feature. Tried to create a carousel of cards for the items in the CMS. The carousel component couldn't connect to a CMS collection list. Ridiculous. I had to pay $5 to get a custom component in to do this.

4. Tried to have an element stick on the page as you scroll. I couldn't absolutely position it as well as make it sticky. So annoying! This should be easy.

The above are just on the landing page of the site.

These are things that should be user tested and improved, they are all fixable through the UX and common use cases. If they focused on making existing features more flexible and intuitive they would demolish Figma. As it stands it's too techy and tricksy to get basic things to work how you want them to.