But this tool is related to that ui/ux version of Sketch (but with/for React), and not the mis-named Sketch (that was for React)?
Naming is fun.
11–20 of 100 posts
But this tool is related to that ui/ux version of Sketch (but with/for React), and not the mis-named Sketch (that was for React)?
Naming is fun.
Hi HN! Super excited to open source this — I'm trying my best to bring design & engineering closer together at Airbnb (and in the world), this has been a super useful project. I'll be hanging out in this thread all day if you have any questions / want to flame me :)
How was React Sketch.app influenced by your blog post from June 2016: Declarative Design Tools ( http://www.jon.gold/2016/06/declarative-design-tools/ )?
- René etc is more conceptual - it’s obviously not a practical day-to-day tool
- React Sketch.app solves the problems in our org that I can do something about, but also lets you do combinatorial/permutational exploration (see the GIFs in the intro!) because _it’s just javascript_.
Both embrace the paradigm of UI-as-a-function-of-data, and really are indebted to the mark that Guillermo left on my brain with https://rauchg.com/2015/pure-ui
So, to be clear, a month ago there was an announcement about an app called Sketch (renamed to Snack now apparently) that was a playground for React code, but people said it was a bad name choice because Sketch is already a ui/ux dev/design tool in this space. But this tool is related to that ui/ux version of Sketch (but with/for React), and not the mis-named Sketch (that was for React)? Naming is fun.
This will come really handy, thank you. I'm trying to build a better infrastructure at work; do you have anything written up about how you work at Airbnb? Your "bring design & engineering closer together" mission sounds like what I'm trying to accomplish, would like to read/chat more about it.
Design Ops (the org that contains my team - Design Tools) - http://airbnb.design/designops-airbnb/
The Way We Build (head of design @alexoid talking about our process) - http://airbnb.design/the-way-we-build/
Building a Visual Language (on our design system) http://airbnb.design/building-a-visual-language/
Earlier quoted context omitted.
Sounds intriguing, but I'm also a little confused about the flow of "code that generates sketch files"... what is the purpose of Sketch in all this? I would think programs like Sketch are useful in general because they give designers a nice way to design things without adding the extra layers of abstraction that code brings (i.e. they can just draw things with a mouse instead of writing instructions that tell the com…
"why not just look at the rendering in a web browser" This is a good question — I’m a technical-leaning designer so I’m partial to just using browser-based tools. I think things like Deco and Expo Snack are wonderful. That said, I’m specifically looking at improving the efficiency of designers’ workflows without changing them. My team is part of DesignOps at Airbnb, maybe useful to consider it analogously to DevOps.…
So, to be clear, a month ago there was an announcement about an app called Sketch (renamed to Snack now apparently) that was a playground for React code, but people said it was a bad name choice because Sketch is already a ui/ux dev/design tool in this space. But this tool is related to that ui/ux version of Sketch (but with/for React), and not the mis-named Sketch (that was for React)? Naming is fun.
- react-dom
- react-native
- react-vr
- react-hardware
- react-blessed
- react-three
- react-aframe
etc
it felt like the right thing to do was a descriptive "this is what it is" name rather than a "marketing name" that would be more confusing.
This will come really handy, thank you. I'm trying to build a better infrastructure at work; do you have anything written up about how you work at Airbnb? Your "bring design & engineering closer together" mission sounds like what I'm trying to accomplish, would like to read/chat more about it.
We haven't written nearly as much as we'd like, but here are some you might like: Design Ops (the org that contains my team - Design Tools) - http://airbnb.design/designops-airbnb/ The Way We Build (head of design @alexoid talking about our process) - http://airbnb.design/the-way-we-build/ Building a Visual Language (on our design system) http://airbnb.design/building-a-visual-language/
Hi HN! Super excited to open source this — I'm trying my best to bring design & engineering closer together at Airbnb (and in the world), this has been a super useful project. I'll be hanging out in this thread all day if you have any questions / want to flame me :)
Sounds intriguing, but I'm also a little confused about the flow of "code that generates sketch files"... what is the purpose of Sketch in all this? I would think programs like Sketch are useful in general because they give designers a nice way to design things without adding the extra layers of abstraction that code brings (i.e. they can just draw things with a mouse instead of writing instructions that tell the com…
It has a Sketch plugin that does a rather competent job of converting Sketch layers/groups into components. (For example, you can prefix a Sketch group with "c:", and React Studio will interpret it as a component.)
Here is a live video demonstrating the Sketch -> React Studio -> React code workflow: https://www.youtube.com/watch?v=Rfd7zmlFZw8 (It's in realtime with detailed explanations, so it runs about 40 minutes.)
Disclaimer: I wrote a pile of code for React Studio.
So, to be clear, a month ago there was an announcement about an app called Sketch (renamed to Snack now apparently) that was a playground for React code, but people said it was a bad name choice because Sketch is already a ui/ux dev/design tool in this space. But this tool is related to that ui/ux version of Sketch (but with/for React), and not the mis-named Sketch (that was for React)? Naming is fun.
Yeah, about that.
Are you saying that the "React Sketch.app" in the title is/should/will be "React Snack.app?"
So, to be clear, a month ago there was an announcement about an app called Sketch (renamed to Snack now apparently) that was a playground for React code, but people said it was a bad name choice because Sketch is already a ui/ux dev/design tool in this space. But this tool is related to that ui/ux version of Sketch (but with/for React), and not the mis-named Sketch (that was for React)? Naming is fun.
So, to be clear Yeah, about that. Are you saying that the "React Sketch.app" in the title is/should/will be "React Snack.app?"