Live data from Hacker News

Painting with Code: Introducing our new open source library React Sketch.app

airbnb.design

51–60 of 100 posts

Re: Painting with Code: Introducing our new open source library React Sketch.app

#51

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.

I asked something similar when AirBnb announced Lottie, and the team (Jon Gold included) replied with great insights. I hope you find this helpful: https://news.ycombinator.com/item?id=13547053

Re: Painting with Code: Introducing our new open source library React Sketch.app

#52
post #50

What is a "Sketch document"? I didn't see a link or explanation in that page.

Sketch is vector based design tool for designing UI and Sketch document is the format that it uses to save those designs. https://www.sketchapp.com/

Thanks!

Re: Painting with Code: Introducing our new open source library React Sketch.app

#53

Earlier quoted context omitted.

To help clarify why this is a big deal, I'd like to share why I've been so excited about this project... [tl;dr] - This is the first tool I'm aware of that actually allows you to generate both API docs and design tools from the same source. Static documentation is a lie waiting to happen. Once docs are even slightly out of date, people lose trust and eventually abandon them. On the engineering side of the dev/design…

That seems like it has some value for super large teams. I guess the thing I'm having a hard time wrapping my head around is the workflow for a tool like this. My current understanding is that you'd need: 1.) Design your thing in Sketch 2.) Code your thing in a text editor 3.) Port your code over to this new tool to see it rendered in Sketch? Like I said. There's some value there (accounting for the changes between 1…

I work on the design system side. In size of Airbnb, you need some kind of design system, since the product fairly large, its changing every week, it's built for 4-6 platforms at the same time by dozens different teams and designers. Without a system the product design and therefore the product becomes chaotic and inconsistent over time.

I do think that design systems can be helpful for smaller, or even 1 person teams as well. It helps you to apply meaningful constrains for your design and reuse common components across the product to shorten development times.

With the library we have both designers and developers can construct completely new views or modifications fairly fast. https://twitter.com/karrisaarinen/status/849733176150773761

Where the React-Sketchapp comes in is help us to keep the system up to date for designers, and in the future build other tools that can help the design workflow.

Re: Painting with Code: Introducing our new open source library React Sketch.app

#55
post #18

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…

To go the other way -- generating React code from Sketch -- you can use React Studio: https://reactstudio.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://w…

The idea behind React Studio is awesome.

I think it would be super cool if React Studio could automatically create a GraphQL api based on the structure of the component data.

We are already doing small experiments in this direction at Graphcool (for example graphql-up https://www.graph.cool/graphql-up/)

Do you think anyone at Reract Studio would be interested in talking more about this? They can ping me at soren@graph.cool :-)

Re: Painting with Code: Introducing our new open source library React Sketch.app

#58
post #24
post #14

Earlier quoted context omitted.

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/

This is great, thanks Jon. I've been struggling to find good workflows for integrating design and engineering (especially when there is a disparity in maturity of the processes for each party). I think there is definitely a gap in the "literature" for this topic and will be eager to follow any other progress you can share.

Would recommend joining the Design Systems Slack [1] and attending the Clarity conference [2] to meet like-minded folks!

[1] https://twitter.com/jina/status/713173129263067136 [2] https://www.clarityconf.com/

Re: Painting with Code: Introducing our new open source library React Sketch.app

#59
post #55
post #18

Earlier quoted context omitted.

To go the other way -- generating React code from Sketch -- you can use React Studio: https://reactstudio.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://w…

The idea behind React Studio is awesome. I think it would be super cool if React Studio could automatically create a GraphQL api based on the structure of the component data. We are already doing small experiments in this direction at Graphcool (for example graphql-up https://www.graph.cool/graphql-up/ ) Do you think anyone at Reract Studio would be interested in talking more about this? They can ping me at soren@gra…

Sounds really great, I'll pass on your contact info!
Post reply on HN