We need to talk about our frontend workflow
Most of us work with designers and other developers on a daily basis. It isn’t always easy to maintain quality and consistency across teams or even features. Collaboration isn’t always easy with spec handovers, component states, achieving pixel perfection, etc.
Design systems have become really popular in the design world in the past couple of years and for good reason. React’s methodology of thinking in components along with recent tools like react-sketchapp make it feasible for designers and developers to work on a single system.
Watch the preview video to get a good idea of the talk: https://youtu.be/R6wsFkl1BN0
Categories this talk fits in:
- Success and failure stories of implementing React and React Native for your use-case
- Front-end architecture patterns and approaches with React.
Things I did not mention in the talk:
- I talk about auth0 a lot, but only to share my experience. There is no mention about it’s products or offering. All the things I talk about are open sourced.
- There are 2 decisions I underplayed in the video,
a. Should you build it from scratch or adopt a library like bluekit? b. What should you use for documentation? react-docgen, storybook, styleguidist, etc?
Building design systems @auth0 ∙ ex @practo ∙ Built bundlesize & cost-of-modules ∙ Makes youtube videos ∙ Co-organises @ReactBangalore ∙ Plays football, Noob surfer/skateboarder