↵

Introducing Framer Playground(framer.com)

over 3 years ago from David Barker

  • Du HoangDu Hoang, over 3 years ago

    Their whole thesis from the beginning is designer should code.

    Which is a fine thesis, but if I'm gonna code I will do it in the production code base, not in their sandbox pseudo coding/design environment.

    I wonder how long they will stick with this thesis because clearly it isn't working. It has been at least 10 years.

    IMO, they should have build tools to facilitate design implementation on top of real dev environment. That's something coding designer would actually use.

    1 point
    • John PJohn P, over 3 years ago

      Their whole thesis from the beginning is designer should code.

      It's not augmenting your workflow with coding concepts that I have a problem with, it's the belief that designers are expected to pick up the less respected and tedious slack of developer jobs and work using the toolset of developers.

      I bring up 3D software because in 3D software you can use code in many ways.

      • Low level : writing compiled plugins using C++ that extend the entire system, e.g particle engines, rendering engines.
      • Medium level : Using languages like Python to automate or script within the engine,
      • High level : Extremely powerful node based systems or Expression based systems allowing you to wire up multiple components together in a very interactive, interactive and artist driven way.

      Now.... it seems to me the majority of what these prototyping apps are aiming to do could be done with the high level methods, more accessible and more artist/designer driven and doesn't require designers to take on sweeping up developer crumbs.

      and I say all this as a designer who is extremely comfortable coding, I just don't believe other designers should be expected to learn React just to make some buttons change state or panels animate.

      2 points