• Michael Dorian Bach, over 3 years ago

    Because moving to React is completely opposite of what the original goal was. Additionally, they completely abandoned the code editor. Want to try to "sketch" something? You have to now deal with the weight of React and even edit the code in a separate editor and import the component in. That's a workflow more a kin to building what you already know you want to build (final components) versus trying to figure out what you want to make. I would wager the move to React was purely driven by the desire to have this "design store". Reacts component and packaging paradigm lends itself well to this.

    We will consider Framer for that aspect of the workflow, but what I'm arguing is its a totally different product now.

    3 points
    • Linton Ye, over 3 years ago

      This is an interesting insight.

      I'd argue though that moving to React is not equal to requiring designers to build "production-ready" components. What prevents you to just build some prototypes, throw them away and rebuild them?

      IMHO it's not that much of a workflow shift. You just get a new tool to create elements: code. (To be absolutely accurate, in old Framer, you could create elements with code, but it's just not as prominent as in X)

      No matter if it's via direct manipulation or code, you can either build what you already know you want to build, or figure out what you want to make. It depends on the context and your goal. In many cases, code is a more powerful and even more convenient tool for exploring ideas, if you know how to do it.

      The bottom line is, you get a new tool at your disposal. You can choose what works the best.

      There's definitely added overhead with extra React knowledge requirement and separate editor etc. It's a tradeoff. The question is whether it's worth it.

      IMHO the answer is yes. Not to mention the other benefits of knowing React as a designer.

      0 points