Where the design community meets.
I think you skirt the question.
In order to use Framer to its full potential, you have to have some coding knowledge. For a designer who doesn't know "coding" Framer is practically useless.
Then again there is problem that code generated cannot be used in production.
Framer might be one of the most comprehensive prototyping tools out there but the entry level is quite high.. and as such inaccessible to a lot of designers.
I would disagree. I am a designer who doesn't know "coding" but I use Framer and it is my prototyping tool of choice.
I find that it is actually really easy to pickup if a bit intimidating at first. The time it takes to learn Framer is much less than Swift and is a great medium between Sketch and actually building production code.
I also find that unlike other prototyping tools Framer has taught me more about code, opening me up to look into learning other languages and making me more comfortable with it, and it has allowed me to discuss design and engineering problems with our dev team in their language.
First you said you don't know coding and then you go on to say it "taught you more about coding" which is a bit a self contradictory.
The question is, why spend hours (or days) building a prototype which cannot be used in production ? Sure you can share some of the "values" with your developers but that is just that! You can also use Facebook's Origami for pretty much everything Framer does without having to do deal with code.
It taught me the basic concepts of code, about parent layers and how developers build the UIs that I design. I still would not consider myself an engineer or someone who truly can code beyond some simple interactions.
I tried Origami, but found that if I was already going to spend so much time understanding the noodling system, I rather work on learning a skill that more translatable outside of just Origami.
Of course whatever allows you to knockout a prototype effectively and communicate your ideas is what matters most at the end of the day. For me that is still Framer.
I'm currently thinking about getting into Framer, but without any coding background I'm a little bit overwhelmed. Especially the necessary indentation of CoffeeScript feels strange at first. I already used Principle and Flinto, which both were far more accessible.
The reason, why I'm looking for something different is, that communicating interactions made in those application proved to be more difficult than expected: Our dev team runs on windows and they have no way to play around with the prototypes themselves. So I send them videos demonstrating the interaction, but for final implementation they of course also need detailed specs. In times where Zeplin/Invision almost got rid of this step, this feels a bit strange. In the end the whole workflow led to subpar implementations most of the time, time and effort put into building the prototypes could have been better used elsewhere.
So my hope for Framer would be, that devs can play around with the prototypes in their browser themselves and get a far better feeling for the interactions by this.
Whats your experience with animation/interaction handoffs?
I recently had the opportunity to use Framer's new handoff system and the devs really appreciated it. But I have also handed them straight up copfescript from Framer and they were able to translate it to production code quite easily.
I also find that using Framer has allowed me to read their code and tweak animations to my liking. I also find devs enjoy working with me more now b/c I communicate with them in a language they can understand and translate to code.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.