Overview
There is a tendency among developers to build monolithic components that align with big designs. Many developers also tend to name stuff based on what it is, rather than what it’s for. These two combine into Apps that are unreadable, complicated, and tailored. While this might get the app shipped fast, it doesn’t scale.
Using some simple techniques, Ken Easson of Rangle.io will demo how to break down complicated code into simple, readable, and most importantly, reusable and composable components. He’ll introduce a few tools that we use to extract theme, style and typography from Figma, to make extremely scalable and robust components. And, he’ll delve into how to measure the use of components within an application to help you at scale.
Objective
How to structure a design heavy application for readability, composability and simplicity.
Five Things Audience Members Will Learn
- Never write clever code
- How to keep it simple and look smart
- How to refactor a complex component into simple composable atoms
- How to find better names for props
- Some cool tools to make life with Figma easier
Target Audience
Front end developers and designers.
