Hey there. It has been a week since @figmadesign's #Schema2021 conference, so as a public service, I thought I would rate all the talks on a scale from 1 to 10.
Opening Keynote by @skuwamoto

Really boring. Who is this guy anyway? Lots of talk about old stuff and I don’t see how it’s relevant.

No charisma. Definitely skippable.

Rating: 0/10 Screenshot of Sho talking about freeform vs structured desig
Guidance over governance by @jenyee_ and @lucaorio_

I loved everything about this talk!

A+ thinking around dealing with contributions from your design team, having fun while working, and a demo of their amazing plugin (Moria) which they use for everything.

Rating: 10/10 Screenshot of Jen and Luca
Mastering the art of code - aligned UI kits by @HonzaTmn

So useful, and chock full of advice on how to set up your design system, as well as how to alert your team to breaking changes.

I learned so much! Tons of useful, directly actionable info.

Rating: 10/10 Screenshot of Jan's talk
Reimagining Atlassian design system, from product to platform by @jenniesyip

Possibly the talk most densely packed with info nuggets.

Super interesting look at the evolution of Atlassian's design system. Great advice at both the tactical and conceptual levels!

Rating: 10/10 Screenshot of Jennie
User-centered design system resources by @jeremydizon, @loonyruni, @myomelette and Joanne Deng

Great information of course, but.. can you believe how good these presenters are? I wish I had presentation skills like this!

Super useful, and super entertaining!

Rating: 10/10 Screenshot of Runi, Michael, Joanne and Jeremy
Design tokens on Asana's Design Systems team by @ainsleywagon, @jina and @IvyCodes

It’s so interesting to see a team of design tokens experts explain every aspect of how they use design tokens at Asana.

Must watch if you want to learn about tokens.

Rating: 10/10 Screenshot of Jina talking about colors
Building custom Figma plugins by @GunuruPrasanna and Kelly Gorr

Super accessible intro to creating plugins in Figma!

Lots of concrete examples of how Microsoft takes advantage of this with their own plugins, many of which are publicly available.

Rating: 10/10 Screenshot of Prasanna talking about Microsoft's plugins
Material You and Figma by @rodydavis and @margeeta

Material is like a meta-design system. You take it, customize it, and then you use THAT for your team. Mind blown.

See how Google thinks about this, and the Figma plugins they built to make it all easier.

Rating: 10/10 Screenshot of Ivy and a color system
Ok. That’s it for my completely objective and fair ratings for these videos.

In all honesty, there is a ton of useful info in these videos so you should check them out here

Uh oh… did I accidentally catch Luca mid nap?
For those of you who had a tinge of doubt about my joke at the start of this thread, let me set the record straight:

Yes, I think my keynote turned out rad, and you should watch it! :-)

I was just being silly but humor on the internet is hard.

Thanks all!

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Sho Kuwamoto

Sho Kuwamoto Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @skuwamoto

12 Oct
I couldn't be more excited about a feature release than this one.

Combining branching with realtime multiplayer was a huge technical and UX challenge, and the team has been relentless in their pursuit of a seamless solution.

1/n
Why is this hard? On an engineering level, writing code for Figma can sometimes feel like a distributed computing problem.

Multiple networked clients are making changes to a single data representation which needs to eventually sync up.

2/n
Now throw into the mix the notion of multiple versions of that data representation, along with user expectations for how you can see the different versions, merge between them, etc.

It's hard to make this all feel seamless, and the team has done a great job!

3/n
Read 4 tweets
4 Mar 20
Earlier today, someone asked how our design and development process works at Figma.

I don't know if this is interesting to anyone, but I ended up writing down our messy, unofficial process in perhaps too much boring detail.

1/n

Phase 0 - brainstorming: We always have way more feature ideas under consideration than we would ever have time to build.

Primarily these come either directly from user requests, or from insights that we get from watching people work.

2/n
Sometimes, people make progress on designs even before features make it onto our roadmap.

Maybe a designer is particularly passionate about something and wants to spend some time thinking about how something could be better. Could also be a PM or an engineer.

3/n
Read 27 tweets
26 Jan 20
I turned 50 today which is surreal. I feel dumb sharing these words but here are some sappy thoughts.
If you ever have a nice thought about someone, tell them. Whether it’s at work or in life, everyone needs to hear nice thoughts.
Try to listen very deeply to what makes you happy. Not the exterior signifiers of happiness, but the true silly stupid emotion. Let yourself have as much of that as you can.
Read 9 tweets
10 Dec 19
A lot of people have been asking why the items in an Auto Layout frame go backwards in @figmadesign.

I usually hesitate to answer seemingly simple questions that end up requiring super long answers, but... here we go!
1/n
For starters, let's consider normal everyday layers. If you select a layer and then duplicate it, do you expect it to go above or below the original item in z-index?

If it goes below, you can't see it, since it's under the original, so it has to above.
2/n
Meanwhile, the layers panel traditionally shows things in an order where higher z-index items go above things with lower z-index. Things have been this way as far back as I can remember.

That means the second layer is shown above the first layer in the layers panel.
3/n
Read 18 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(