Ok, so far, I’ve worked all day with the new Framer and it’s really sweet. The product strategy is brilliant and it makes Framer and (coding generally) more accessible to designers. That’s a huge plus. At my company, I’m the only designer and proud advocate of Framer. Initially, people were like “wtf is Framer?!” Now Stakeholders love it and we can’t imagine our company without it. Our hiring descriptions in my department now request that Candidates have some experience with the product.
It allows us to test and validate our ideas remarkably quick. It responds to my need as a Designer in very intuitive and thoughtful way. It will remain my weapon of choice for mobile prototyping.
I must admit, the new design mode is a little ‘foreign’ to me. For example, if I create a layer in code mode, I expect to see it represented in the design view, but it’s not. Whereas if I create the layer directly in design you can see it reflected in the object hierarchy in code. It’s weird that stuff I create in code-mode isn’t visible in design mode. Moreover, the convention of relabelling a layer for the purpose of targeting is … interesting but weird.
I’m sure over time I’ll become accustomed to using design-mode`…but Sketch(as of now remains my tool of choice). Having said that, I’m about to ask what may sound like a silly and arguably subjective question. If I build my prototypes programmatically, not using design mode, but rather dragging and dropping sketch assets into my project…and then I toggle to Design Mode, it’s a complete empty state…Is that ok?
Would I be correct in assuming that if you’re workflow doesn’t involve the new Design feature whatsoever, Prototyping in Framer remains largely the same as it did in v89?