Whoa. Is it just me, or did the bar of entry for prototyping with framer just get lowered significantly?
Hi all! We're super excited to finally share this with you all. Earlier this year, we introduced Auto-Code, an all-new way to design with Framer. Today we're releasing the next part, Auto-Code Animation. A new feature that allows you to visually manipulate and fine-tune animations. We really hope you like it. :-)
This looks awesome! Makes me want to try it. :) I've been testing many prototyping tools and all of them have something that I don't like or some key features are missing.
Been working in Framer all day. Auto-Code Animation is a welcomed addition!
This is really cool! Great job team and congrats with the ship :)
So excited to see this shipped!
A good addition. While I can understand how many would like Framer, and I applaud the work of the Framer team, I still have two issues.
I dislike the lack of cross-platform compatibility. A small group of designers and developers don't seem to understand that the world at large isn't Apple only. I may be on a Mac, but others on my team, and that I work with are not. There are Linux, Windows, and even Chrome OS users that I work with. And yes...I know there is an open source "library", but it's not the same thing.
It's also a weird premise to code a prototype without being able to export most of the code. Why not just code a real prototype, and adapt the output? It would take roughly the same amount of time, and then you have a MVC that can transition to a MVP instead of just having a prototype.
For #2, I've found that going straight to production coding style (MVC or whatever) is harmful to my prototypes. It forces me to make more than just design decisions, now I have to make software architecture decisions too. This takes longer and I find myself less willing to throw everything away and try a different route, which IMO is essential to good design.
Framer lets me focus on only the UI and interactions. I don't have to care about writing good code or deal with browser bugs or which MVC framework to pick. It's a separation of concerns that has proved very useful.
+1 to Weston's comment. Not having to think about the DOM, browser compatibility, browser performance, etc allows me to stay focussed and creative as a designer. It's the same reason why designers are encouraged to sketch out their ideas before going straight to high fidelity mocks. Regarding #1, you've got to start somewhere, right? The Framer team is doing kick ass work, but they're still a small crew. We're going through a grass roots, mini-renaissance of sorts for designer tools. Most of these new tools are being innovated by small independent teams; if they spread themselves too thin, it's gonna be that much harder to create anything of substance and value... Have you thought about running Mac OS in a VM? I know, VMs suck compared to native, but it's an option if you're desperate.
Nooo, my license lapsed after v72.