How to iterate at the speed of light using components β‘
A simple 4 step process that I use 20+ times a day π
If you're like me, you spend a good amount of time tweaking the design of component groups while trying all sorts of different approaches.
But most designers I talk to don't use components until AFTER they pick the final design direction.
I'm here to propose a better way π
But before we get into the details... here are the two goals of this workflow:
1. Create a bunch of iterations side by side for easy comparison
2. Work as efficiently as possible (don't make the same design tweak twice)
Ok now that we got that out of the way... let's dive inπ
1. Duplicate my main frame and select all of the instances of my component.
2. Then run the Master plugin by typing cmd + / + master
3. Drag my main component into the auto layout and delete the duplicate
4. Make any style tweaks that I want to try on the main component!
Running the master plugin automatically creates a new main component and makes all other components an instance of that main component
This way I only have to adjust my style one time and the changes automatically reflect throughout my entire component group.
This allows me to move faaaassstt π¨
In general I'm a big believer in @Julian 's "Creativity Faucet"
Sometimes you have to crank out the bad ideas to get to the good ones. This workflow just speeds up the time it takes me to get through the bad ones π
I try not to think too much. Just duplicate and try the next idea in my mental pipeline. Repeat.
If I am doing UI work I'll crank out 10-20 iterations of something. Then I can take a step back, narrow down my list, and either continue the process or loop in other stakeholders.
I like to think of portfolio projects as a recipe video you'd see onlineπ₯
It starts with a beautiful visual of the finished plate to draw people in.
And then 95% of the video documents how you make the dish from scratch.
Here's a list of questions to help fill in that 95%π
There's been a lot of Q&A around portfolio pieces in @shiftnudge recently. So I decided to compile some question prompts into a bit of a list.
Not every project produces answers to all of these questions. But hopefully, these spark some ideas of your own.
Let's take a look π
TEAM/PROJECT INFO
Who was the project for?
What was your role on the team?
What were you directly responsible for?
How did you collaborate with other team members?
What business context is needed to understand the project?