↵

AMA: Framer Team on the all-new Framer and Auto-Code

over 7 years ago from Brittany Gregory, Content Strategist at Framer

  • Alec SibiliaAlec Sibilia, over 7 years ago

    Hey guys, thanks for taking the time. Let me start by saying that as a designer who can write code, so far I'm really enjoying learning Framer. It's been a great way to prototype components quickly without having to set up a dummy app or dirty an existing one. I only have a few questions so far...

    1. Why CoffeeScript? (ES6 would be my dream)

    2. Any plans to allow editing SVG elements' base properties (fill etc.)?

    3. Where do you see Framer 3 years from now?

    2 points
    • Benjamin den BoerBenjamin den Boer, over 7 years ago

      Hey Alec! Thanks — this is always nice to hear. Let's see..

      1. We initially chose CoffeeScript because we believe it has a lot of advantages for people new to scripting: its syntax is relatively flexible, you can omit curly braces, brackets etc. which can make it easier to scan and learn. Writing things like functions and loops is also a little simpler. Basically, we hope it makes it easier for people to start with.

      2. Well, we're exploring SVG layers, yeah — and there's already a lot you can do with SVGs in Framer. This is something that could happen.

      3. Hehe, this is a tricky one to answer. In general, there's still so much more we can do to improve Auto-Code. Everything from making it easier for people to start with Framer, to implementing more advanced / future design tools and components, to improving the sharing experience, etc... there's a lot left to explore. And 3 years is a long time! :-)

      2 points
      • Jorn van Dijk, over 7 years ago

        Short answer to 3: become the best code based design tool. There are so many design problems we can solve with the right mix of code and interface.

        1 point