逐字稿 🔗
WEBVTT
Kind: captions
Language: en
00:00:03.929 --> 00:00:11.780
[music]
00:00:40.240 --> 00:00:41.870
>> Hey, good to see you. Thanks for coming.
00:00:41.880 --> 00:00:43.270
This is another episode of Wireframe
00:00:43.280 --> 00:00:44.830
brought to you by Design Systems House.
00:00:44.840 --> 00:00:47.110
I'm your host Danny Yamato and today
00:00:47.120 --> 00:00:49.190
we're going to be talking about motion
00:00:49.200 --> 00:00:50.750
systems and I'm very excited to talk
00:00:50.760 --> 00:00:52.630
about this. I have lots of thoughts and
00:00:52.640 --> 00:00:54.230
in order to do so I have a very special
00:00:54.240 --> 00:00:56.230
guest. It's Ryan Smith. Ryan, thank you
00:00:56.240 --> 00:00:57.830
so much for being on the show. Let
00:00:57.840 --> 00:00:58.830
everybody know who you are and what
00:00:58.840 --> 00:01:00.030
you're all about.
00:01:00.040 --> 00:01:01.710
>> Hi, and it's well, thank you. Thank you
00:01:01.720 --> 00:01:03.150
for having me.
00:01:03.160 --> 00:01:05.270
Yeah, my name is Ryan Smith.
00:01:05.280 --> 00:01:08.430
I'm a senior design systems engineer at
00:01:08.440 --> 00:01:11.270
South West. And I've been doing
00:01:11.280 --> 00:01:14.590
professional development for over 15
00:01:14.600 --> 00:01:15.630
years.
00:01:15.640 --> 00:01:16.310
Um
00:01:16.320 --> 00:01:17.630
And so
00:01:17.640 --> 00:01:19.070
in terms of like motion, I've always
00:01:19.080 --> 00:01:21.110
been a I've always enjoyed doing motion
00:01:21.120 --> 00:01:22.910
and motion work and I try to do it as
00:01:22.920 --> 00:01:24.470
much as I can within my job, but I'm
00:01:24.480 --> 00:01:27.590
definitely an engineer first.
00:01:27.600 --> 00:01:29.750
And so yeah, as it comes to motion and
00:01:29.760 --> 00:01:31.750
design systems, I've been
00:01:31.760 --> 00:01:33.790
sort of approaching it from that angle
00:01:33.800 --> 00:01:35.910
which has been really fun. So, yeah, I'm
00:01:35.920 --> 00:01:36.990
excited to talk about this. This is
00:01:37.000 --> 00:01:38.150
going to be a really good conversation.
00:01:38.160 --> 00:01:40.230
>> Yeah, yeah. I mean, I saw you post on
00:01:40.240 --> 00:01:41.830
LinkedIn that you were working on, you
00:01:41.840 --> 00:01:43.350
know, this this design systems and
00:01:43.360 --> 00:01:45.510
motions thing and
00:01:45.520 --> 00:01:47.470
you know, I've I I actually So, I talk
00:01:47.480 --> 00:01:49.070
about it in my book Miseen Mode a little
00:01:49.080 --> 00:01:51.390
bit about how I would potentially go
00:01:51.400 --> 00:01:55.190
about the motion. But in my day-to-day
00:01:55.200 --> 00:01:56.990
work talking about design systems, I
00:01:57.000 --> 00:01:59.962
usually put motion at like the bottom of
00:01:59.972 --> 00:02:02.962
priority, you know, because there's so
00:02:02.972 --> 00:02:06.002
many other problems in experience design
00:02:06.012 --> 00:02:08.162
that are not being solved that I find to
00:02:08.172 --> 00:02:10.562
Load full transcript
be more important than motion. But,
00:02:10.572 --> 00:02:14.002
granted, I mean, if you are doing well
00:02:14.012 --> 00:02:15.682
in user experience design and have
00:02:15.692 --> 00:02:17.122
solved the majority of those problems
00:02:17.132 --> 00:02:19.682
already, then it's an opportunity to go
00:02:19.692 --> 00:02:21.322
on to the next thing. And I do think
00:02:21.332 --> 00:02:24.162
South Left as a
00:02:24.172 --> 00:02:27.042
as a company has solved a great deal of
00:02:27.052 --> 00:02:28.562
the design system problems over the
00:02:28.572 --> 00:02:30.082
years that it's that it's been around.
00:02:30.092 --> 00:02:32.562
So, I think this is a great opportunity
00:02:32.572 --> 00:02:34.322
for you to solve,
00:02:34.332 --> 00:02:36.602
you know, the problems that people
00:02:36.612 --> 00:02:38.122
otherwise don't have the problems to
00:02:38.132 --> 00:02:39.156
solve, you know.
00:02:39.166 --> 00:02:39.922
>> [snorts]
00:02:39.932 --> 00:02:41.682
>> Yeah, absolutely. Yeah, and I think
00:02:41.692 --> 00:02:45.002
that's um but being positioned at South
00:02:45.012 --> 00:02:47.522
Left and the work that that we've done
00:02:47.532 --> 00:02:49.522
as a company, especially in the design
00:02:49.532 --> 00:02:51.362
system space, that's a great that's a
00:02:51.372 --> 00:02:52.922
great point cuz that's kind of
00:02:52.932 --> 00:02:54.602
that's kind of what uh led me to the
00:02:54.612 --> 00:02:57.122
opportunity to explore this this piece.
00:02:57.132 --> 00:02:58.802
Cuz I've always enjoyed motion and
00:02:58.812 --> 00:03:01.082
throughout my career I've you know, I I
00:03:01.092 --> 00:03:02.682
I studied it in you know, high school,
00:03:02.692 --> 00:03:04.882
college, and and I had sometimes
00:03:04.892 --> 00:03:06.442
throughout my career where I got to do
00:03:06.452 --> 00:03:08.962
some motion work, but um but being
00:03:08.972 --> 00:03:10.842
mostly a developer, you know, I just get
00:03:10.852 --> 00:03:12.482
to look for opportunities to incorporate
00:03:12.492 --> 00:03:14.482
motion in products or sites that I'm
00:03:14.492 --> 00:03:16.282
building if it's not already called out.
00:03:16.292 --> 00:03:17.722
I'll always say like, "Hey, maybe for
00:03:17.732 --> 00:03:19.282
this experience we can put some motion
00:03:19.292 --> 00:03:21.562
in there." And I had an idea for a long
00:03:21.572 --> 00:03:23.922
time. Um this I mean, it goes back years
00:03:23.932 --> 00:03:26.922
ago kind of before the AI stuff was was
00:03:26.932 --> 00:03:29.002
you know, was in play and you know,
00:03:29.012 --> 00:03:31.322
before even things like Shadsy and were
00:03:31.332 --> 00:03:33.122
were becoming more popular where, you
00:03:33.132 --> 00:03:34.762
know, we would have component libraries
00:03:34.772 --> 00:03:36.482
that we would work with at South Left at
00:03:36.492 --> 00:03:38.042
South Left that we would kind of develop
00:03:38.052 --> 00:03:40.562
for ourselves and
and I would talk to TJ
00:03:40.572 --> 00:03:41.762
and say, "Well, I want to make one
00:03:41.772 --> 00:03:42.922
that's like a motion." You know, it
00:03:42.932 --> 00:03:44.162
could be like unbranded, but I want to
00:03:44.172 --> 00:03:45.882
make like a set of components that
00:03:45.892 --> 00:03:47.282
benefit well from motion that we could
00:03:47.292 --> 00:03:49.762
always just kind of reach for. Um and
00:03:49.772 --> 00:03:50.842
that's something I thought about for a
00:03:50.852 --> 00:03:52.722
while, but I never had a whole lot of
00:03:52.732 --> 00:03:55.122
opportunity to, you know, to go too far
00:03:55.132 --> 00:03:57.602
into it. But as you get into the AI
00:03:57.612 --> 00:03:59.922
space that we are now and you talk about
00:03:59.932 --> 00:04:02.282
like the work you've done with with um
00:04:02.292 --> 00:04:04.124
design systems and just working with AI
00:04:04.134 --> 00:04:05.364
in general. I think one of the cool
00:04:05.374 --> 00:04:07.644
things about working with artificial
00:04:07.654 --> 00:04:09.404
intelligence is that it it kind of
00:04:09.414 --> 00:04:11.804
forces you to take that step back and
00:04:11.814 --> 00:04:13.364
re-evaluate
00:04:13.374 --> 00:04:14.964
how things are going to figure out where
00:04:14.974 --> 00:04:16.964
you can work with it. And that's only,
00:04:16.974 --> 00:04:18.804
you know, I think that we we had that
00:04:18.814 --> 00:04:21.404
great philosophy at Southwest that just
00:04:21.414 --> 00:04:23.404
we look at AI as an empowering tool.
00:04:23.414 --> 00:04:25.364
It's just like any other tool we use and
00:04:25.374 --> 00:04:26.284
we have the knowledge and the
00:04:26.294 --> 00:04:28.004
experience. So, how do we want to use
00:04:28.014 --> 00:04:29.764
it? How do we want to work with it? And
00:04:29.774 --> 00:04:31.044
so, when you take that step back and you
00:04:31.054 --> 00:04:32.244
figure out where you want to work with
00:04:32.254 --> 00:04:33.884
it and then as you start to get into
00:04:33.894 --> 00:04:35.844
working with it, you naturally start to
00:04:35.854 --> 00:04:37.724
see how much it can empower you and
00:04:37.734 --> 00:04:39.884
creative areas where you can try to push
00:04:39.894 --> 00:04:42.404
the boundaries. And so, you start to
00:04:42.414 --> 00:04:44.244
look for like, "Well, where where where
00:04:44.254 --> 00:04:45.844
where do we need improvement? Where are
00:04:45.854 --> 00:04:47.204
things that are lacking that we could
00:04:47.214 --> 00:04:49.244
then try to like solve problems or where
00:04:49.254 --> 00:04:50.804
can this fit in?" And so, that was a
00:04:50.814 --> 00:04:52.524
natural point for me to be able to kind
00:04:52.534 --> 00:04:54.524
of revisit this motion where I was like,
00:04:54.534 --> 00:04:55.684
"Oh, I've always wanted to do this."
00:04:55.694 --> 00:04:57.284
Like, let's let's dive really far into
00:04:57.294 --> 00:04:59.884
the motion. So, I started creating the
00:04:59.894 --> 00:05:02.004
system that
00:05:02.014 --> 00:05:05.004
this motion design system that I use
00:05:05.014 --> 00:05:06.764
I've used it in multiple production
00:05:06.774 --> 00:05:08.444
sites and and I've carried it from
00:05:08.454 --> 00:05:10.284
project to project. And it's just it's
00:05:10.294 --> 00:05:12.684
just my personal philosophy and the way
00:05:12.694 --> 00:05:15.604
that I've approached motion. So, it it's
00:05:15.614 --> 00:05:17.844
a code-first system because I'm a
00:05:17.854 --> 00:05:18.524
developer.
00:05:18.534 --> 00:05:19.244
>> Yep.
00:05:19.254 --> 00:05:22.204
>> Um but yeah, it focuses, you know, going
00:05:22.214 --> 00:05:24.204
through the the tiers
00:05:24.214 --> 00:05:26.044
of tier one and tier two tokens and
00:05:26.054 --> 00:05:28.244
primitives and semantics and then up
00:05:28.254 --> 00:05:31.004
through, you know, for tier three AI I
00:05:31.014 --> 00:05:32.444
have something that I I call
00:05:32.454 --> 00:05:33.804
choreography tokens.
00:05:33.814 --> 00:05:34.204
>> Mhm.
00:05:34.214 --> 00:05:36.844
>> Um and then there's AI intent and some
00:05:36.854 --> 00:05:38.804
reduced motion. That's like a high-level
00:05:38.814 --> 00:05:40.564
overview. I want to give you a chance to
00:05:40.574 --> 00:05:42.044
talk here for a second cuz I can just go
00:05:42.054 --> 00:05:43.213
go go.
00:05:43.223 --> 00:05:43.404
>> [laughter]
00:05:43.414 --> 00:05:44.844
>> But I want to hear some of your thoughts
00:05:44.854 --> 00:05:46.284
on this too cuz I'm just rambling.
00:05:46.294 --> 00:05:48.324
>> Yeah, absolutely. Yeah, I mean again I I
00:05:48.334 --> 00:05:50.484
I I wanted to talk about this in
00:05:50.494 --> 00:05:51.804
particular again because I've I've
00:05:51.814 --> 00:05:53.694
thought a little bit about it and just
00:05:53.704 --> 00:05:55.604
[snorts] you know, this is our actually
00:05:55.614 --> 00:05:57.604
Ryan and I's first you know, meeting
00:05:57.614 --> 00:05:59.284
together because I just saw this on
00:05:59.294 --> 00:06:00.244
LinkedIn and I was like, "We got to
00:06:00.254 --> 00:06:01.684
talk." So,
00:06:01.694 --> 00:06:02.924
you know, some of the stuff that I'm
00:06:02.934 --> 00:06:04.845
going to say to you that the audience
00:06:04.855 --> 00:06:06.485
might already know about because I talk
00:06:06.495 --> 00:06:09.765
about this a lot, but a large part of
00:06:09.775 --> 00:06:11.245
what I
00:06:11.255 --> 00:06:13.845
advocate for is to describe with
00:06:13.855 --> 00:06:16.725
intention. Right? And talking about Miz
00:06:16.735 --> 00:06:18.725
on mode and and semantic tokens, I have
00:06:18.735 --> 00:06:21.645
a very strict definition of what
00:06:21.655 --> 00:06:24.685
semantic means from a from a token
00:06:24.695 --> 00:06:26.885
standpoint. So much so that I actually
00:06:26.895 --> 00:06:29.125
don't even really use the word semantic
00:06:29.135 --> 00:06:31.405
to describe tokens anymore. I
describe
00:06:31.415 --> 00:06:33.525
it as intense as opposed to semantic
00:06:33.535 --> 00:06:35.965
tokens. And I do that specifically
00:06:35.975 --> 00:06:38.285
because there's so much
00:06:38.295 --> 00:06:40.685
um disagreement with what semantic
00:06:40.695 --> 00:06:43.325
tokens are that I don't want to be
00:06:43.335 --> 00:06:45.485
involved in that conversation because
00:06:45.495 --> 00:06:48.165
that takes away from like the
00:06:48.175 --> 00:06:50.405
expectation that I have for this
00:06:50.415 --> 00:06:53.245
particular tier of tokens. So, I speak
00:06:53.255 --> 00:06:55.005
of them as intense. Like these are
00:06:55.015 --> 00:06:56.405
intense that you're going to, you know,
00:06:56.415 --> 00:06:57.645
encode. But
00:06:57.655 --> 00:06:59.885
just to kind of cross the bridge, we
00:06:59.895 --> 00:07:01.365
could talk semantic in terms of, you
00:07:01.375 --> 00:07:03.445
know, that definition and then be a
00:07:03.455 --> 00:07:05.645
little loose with it. And [snorts] the
00:07:05.655 --> 00:07:08.685
the thing about the semantic tokens has
00:07:08.695 --> 00:07:10.605
always I have a, you know, a kind of a
00:07:10.615 --> 00:07:12.525
framework for that as well where there's
00:07:12.535 --> 00:07:14.765
this idea of um
00:07:14.775 --> 00:07:17.645
purpose, priority, and uh property. So,
00:07:17.655 --> 00:07:20.285
purpose would be like action or surface
00:07:20.295 --> 00:07:21.845
or text. And then your priority is
00:07:21.855 --> 00:07:23.965
primary, secondary, things like that. Uh
00:07:23.975 --> 00:07:24.885
and then you have foreground,
00:07:24.895 --> 00:07:27.245
background, and, you know, border colors
00:07:27.255 --> 00:07:29.445
or font family or what have you. So,
00:07:29.455 --> 00:07:31.125
there's your like, you know, parts of a
00:07:31.135 --> 00:07:33.605
token name. And
00:07:33.615 --> 00:07:35.365
thinking about motion,
00:07:35.375 --> 00:07:38.965
you know, the the the property is fairly
00:07:38.975 --> 00:07:40.605
um straightforward, right? Because that
00:07:40.615 --> 00:07:42.325
property is effectively what it affects.
00:07:42.335 --> 00:07:44.205
We're talking about things like duration
00:07:44.215 --> 00:07:46.325
and timing and stuff like that. So, it's
00:07:46.335 --> 00:07:48.605
very CSS driven. So, like there are
00:07:48.615 --> 00:07:51.925
answers there. But when it comes to the
00:07:51.935 --> 00:07:53.565
other sections, then
00:07:53.575 --> 00:07:55.565
you know, I can be, you know, kind of um
00:07:55.575 --> 00:07:57.245
flexible in this. But the other sections
00:07:57.255 --> 00:07:59.525
about what um
00:07:59.535 --> 00:08:02.365
represents the the purpose and the
00:08:02.375 --> 00:08:04.005
priority,
00:08:04.015 --> 00:08:07.847
that's where I found that motion gets a
00:08:07.857 --> 00:08:11.407
little bit hard to um
00:08:11.417 --> 00:08:15.047
to to to describe with intention. Right?
00:08:15.057 --> 00:08:18.087
Cuz what I see
a lot of the times is a
00:08:18.097 --> 00:08:20.287
feeling of motion. Oh, I don't feel like
00:08:20.297 --> 00:08:21.727
this should be this. I should feel
00:08:21.737 --> 00:08:23.727
should be this. And that sounds more
00:08:23.737 --> 00:08:25.407
like a primitive token to me. I don't
00:08:25.417 --> 00:08:27.207
want it to be this shade of red. I want
00:08:27.217 --> 00:08:29.327
it to be this shade of red. Right? So,
00:08:29.337 --> 00:08:33.247
the feeling of motion I don't do a lot
00:08:33.257 --> 00:08:34.487
of work in it. I don't want to have a
00:08:34.497 --> 00:08:36.247
lot of opinions on cuz people will have
00:08:36.257 --> 00:08:38.127
opinions about it and that's fine. But
00:08:38.137 --> 00:08:41.247
what I do is I want to create the proxy
00:08:41.257 --> 00:08:43.567
that gets it to the UI and figure out
00:08:43.577 --> 00:08:45.807
what that structure is. So,
00:08:45.817 --> 00:08:48.287
tell me a little bit about the semantic
00:08:48.297 --> 00:08:50.487
layer for your your system. I'm very
00:08:50.497 --> 00:08:51.847
interested in that.
00:08:51.857 --> 00:08:54.647
>> Yeah, absolutely. Well, I I I love all
00:08:54.657 --> 00:08:55.607
of those things that you were just
00:08:55.617 --> 00:08:56.807
saying because I
00:08:56.817 --> 00:08:58.967
I think that the intent and I'm okay
00:08:58.977 --> 00:09:01.367
with calling it intent as well because
00:09:01.377 --> 00:09:03.207
or you know, named intent usage intent
00:09:03.217 --> 00:09:04.567
however you want to describe it, but I
00:09:04.577 --> 00:09:07.087
think that that's a huge
00:09:07.097 --> 00:09:10.807
um factor in how we build these systems
00:09:10.817 --> 00:09:14.007
specifically in this agentic age because
00:09:14.017 --> 00:09:17.847
you need that intent to improve when
00:09:17.857 --> 00:09:20.007
you're when you're working with with
00:09:20.017 --> 00:09:21.367
agents and when you're working with you
00:09:21.377 --> 00:09:24.447
know, in this AI environment, you need
00:09:24.457 --> 00:09:25.087
um
00:09:25.097 --> 00:09:27.687
a good shared vocabulary and some real
00:09:27.697 --> 00:09:29.287
good direction and intent for it to be
00:09:29.297 --> 00:09:31.127
able to produce good results. That's a
00:09:31.137 --> 00:09:32.727
lot of the work that you do you know,
00:09:32.737 --> 00:09:36.287
yeah. Yeah. So, um So, I like that and
00:09:36.297 --> 00:09:37.927
that's part of what I've considered you
00:09:37.937 --> 00:09:39.287
know, throughout the whole process. So,
00:09:39.297 --> 00:09:41.567
even in the in the tier the tier one and
00:09:41.577 --> 00:09:42.887
the tier two. So, whether you would call
00:09:42.897 --> 00:09:45.167
them semantic or um whatever name you'd
00:09:45.177 --> 00:09:47.727
like to do. Um I think if I could even
00:09:47.737 --> 00:09:49.287
take one step back before we get to the
00:09:49.297 --> 00:09:51.487
the tier two
00:09:51.497 --> 00:09:53.527
even at the tier one level your
00:09:53.537 --> 00:09:55.847
durations and your easings, I think that
00:09:55.857 --> 00:09:58.047
there's two things there. So, just
00:09:58.057 --> 00:09:59.527
duration and easing some example you can
00:09:59.537 --> 00:10:01.767
also you can tokenize you know, delays
00:10:01.777 --> 00:10:03.727
or distances and I think there's
00:10:03.737 --> 00:10:05.847
benefits to those as well. But um you
00:10:05.857 --> 00:10:07.127
know, duration and easing make up the
00:10:07.137 --> 00:10:09.847
core of of of motion you know, motion
00:10:09.857 --> 00:10:12.688
intent as as general. And so,
00:10:12.698 --> 00:10:13.368
um
00:10:13.378 --> 00:10:15.488
even then, I think that when I approach
00:10:15.498 --> 00:10:17.808
the motion in the design system at at
00:10:17.818 --> 00:10:19.048
these
00:10:19.058 --> 00:10:21.208
primitive levels and then building into
00:10:21.218 --> 00:10:23.328
the semantic layers, I the goal of the
00:10:23.338 --> 00:10:26.168
system in in this is again, this is my
00:10:26.178 --> 00:10:27.768
opinion cuz
00:10:27.778 --> 00:10:29.448
everyone will be opinionated on motion,
00:10:29.458 --> 00:10:31.248
but the way I like to approach it is
00:10:31.258 --> 00:10:33.168
having a system that there's there's
00:10:33.178 --> 00:10:34.248
kind of two things I take into
00:10:34.258 --> 00:10:35.648
consideration. Making sure you have
00:10:35.658 --> 00:10:38.568
enough tokens to be able to express
00:10:38.578 --> 00:10:40.568
motion that is both
00:10:40.578 --> 00:10:43.248
narrative and storytelling, but then
00:10:43.258 --> 00:10:45.048
also functional. And I think that that's
00:10:45.058 --> 00:10:46.448
a big piece of it. You know, when you're
00:10:46.458 --> 00:10:48.488
building user interfaces as opposed to
00:10:48.498 --> 00:10:50.208
like motion design often like videos or
00:10:50.218 --> 00:10:51.568
something where it's all kind of
00:10:51.578 --> 00:10:52.968
storytelling.
00:10:52.978 --> 00:10:54.528
You know, when you're building a user
00:10:54.538 --> 00:10:57.048
interface, your motion is is
00:10:57.058 --> 00:10:58.608
communicating to your user and it's
00:10:58.618 --> 00:11:00.328
anchoring them and it's it's responding
00:11:00.338 --> 00:11:01.528
to them. It's helping the site feel
00:11:01.538 --> 00:11:03.968
responsive. And I I like to think of
00:11:03.978 --> 00:11:05.848
that as like functional motion. So,
00:11:05.858 --> 00:11:08.008
making sure you have enough durations
00:11:08.018 --> 00:11:10.608
and easings to support that kind of
00:11:10.618 --> 00:11:12.688
motion is important.
00:11:12.698 --> 00:11:13.808
And
00:11:13.818 --> 00:11:15.408
that goes because like if you're on
00:11:15.418 --> 00:11:16.768
desktop,
00:11:16.778 --> 00:11:18.368
when you hover over
00:11:18.378 --> 00:11:20.568
a button or anything, you know, a link,
00:11:20.578 --> 00:11:21.968
whatever it might be, you know, that
00:11:21.978 --> 00:11:23.448
that hover interaction is a type of
00:11:23.458 --> 00:11:26.008
motion. And in my opinion, you don't
00:11:26.018 --> 00:11:27.368
usually you don't want that to take
00:11:27.378 --> 00:11:30.408
like, you know, 1.2 seconds for that
00:11:30.418 --> 00:11:31.928
interaction, right? You want it to be
00:11:31.938 --> 00:11:33.768
quicker and you want it to be
00:11:33.778 --> 00:11:36.048
more responsive. And so, it's being able
00:11:36.058 --> 00:11:37.848
to have this nice like ladder of
00:11:37.858 --> 00:11:39.408
durations that you can reach for at
00:11:39.418 --> 00:11:42.248
different levels. And then the big thing
00:11:42.258 --> 00:11:45.008
that I think with like easing curves,
00:11:45.018 --> 00:11:46.008
and I promise we're going to get into
00:11:46.018 --> 00:11:47.248
the semantic layers. Thanks for sticking
00:11:47.258 --> 00:11:48.053
with me.
00:11:48.063 --> 00:11:48.168
>> [laughter]
00:11:48.178 --> 00:11:48.648
>> No problem.
00:11:48.658 --> 00:11:50.448
>> The easing is like I think it's it's
00:11:50.458 --> 00:11:52.888
good at the duration level to I pick I
00:11:52.898 --> 00:11:54.888
pick names like
00:11:54.898 --> 00:11:56.648
I chose names like
00:11:56.658 --> 00:11:59.768
quick, short, medium, long. And kind of
00:11:59.778 --> 00:12:01.328
almost like t-shirt sizing, but I did
00:12:01.338 --> 00:12:02.568
that on purpose and it goes to this
00:12:02.578 --> 00:12:04.968
bigger this bigger idea of the shared
00:12:04.978 --> 00:12:07.008
vocabulary which really comes in when it
00:12:07.018 --> 00:12:09.408
when it is both for humans, but also for
00:12:09.418 --> 00:12:11.888
AI usage. And I think like easing is the
00:12:11.898 --> 00:12:14.169
same way. you know, you can might have
00:12:14.179 --> 00:12:15.609
your standard curve that's like a
00:12:15.619 --> 00:12:17.489
standard S curve that could be your
00:12:17.499 --> 00:12:19.929
default, but then I say, you know,
00:12:19.939 --> 00:12:22.769
instead of instead of using, you know,
00:12:22.779 --> 00:12:25.529
ease in and ease out curves,
00:12:25.539 --> 00:12:27.849
call them entrance and exit and speak to
00:12:27.859 --> 00:12:30.289
their intent. And because especially if
00:12:30.299 --> 00:12:33.089
you're a developer that is maybe less
00:12:33.099 --> 00:12:34.969
familiar and you're having to reach for
00:12:34.979 --> 00:12:36.889
things and you see a token that's like
00:12:36.899 --> 00:12:39.729
ease out. You might you might think
00:12:39.739 --> 00:12:41.929
like, okay, well, it's like I'm easing
00:12:41.939 --> 00:12:43.529
out. So, that's what I want I'm exiting.
00:12:43.539 --> 00:12:45.649
I want to out, you know, but that's the
00:12:45.659 --> 00:12:47.809
opposite, right? You want you entrances
00:12:47.819 --> 00:12:49.729
should ease out. And so, but you can
00:12:49.739 --> 00:12:52.569
remove that by just choosing a name that
00:12:52.579 --> 00:12:55.249
really speaks to that intent. And that
00:12:55.259 --> 00:12:56.449
works for, you know, you
mentioned it
00:12:56.459 --> 00:12:57.969
works for artificial intelligence as
00:12:57.979 --> 00:13:00.009
well. So,
00:13:00.019 --> 00:13:02.489
then I like to, you know,
00:13:02.499 --> 00:13:04.409
in this system I the way I built it up
00:13:04.419 --> 00:13:08.369
from there is I've my my named intent is
00:13:08.379 --> 00:13:12.809
relatively um straightforward at the the
00:13:12.819 --> 00:13:15.009
tier two level or the semantic level. I
00:13:15.019 --> 00:13:19.449
it's I I just use like motion use hover,
00:13:19.459 --> 00:13:21.569
motion use focus,
00:13:21.579 --> 00:13:23.729
motion disclosure in, motion disclosure
00:13:23.739 --> 00:13:25.329
out. They're they're pretty
00:13:25.339 --> 00:13:27.049
straightforward at that level. I but I
00:13:27.059 --> 00:13:28.449
think but what they do then is they're
00:13:28.459 --> 00:13:29.849
obviously they're referencing back to
00:13:29.859 --> 00:13:32.169
the primitives. So, one of the things
00:13:32.179 --> 00:13:34.409
that you see in the patterns that that
00:13:34.419 --> 00:13:36.409
creates is like when you're doing
00:13:36.419 --> 00:13:38.929
entrances and exits, the entrance is
00:13:38.939 --> 00:13:42.889
always um longer than the exit because
00:13:42.899 --> 00:13:44.609
when you're having an entrance that
00:13:44.619 --> 00:13:47.169
comes in, you might do like a medium
00:13:47.179 --> 00:13:48.889
entrance. And so, by combining that
00:13:48.899 --> 00:13:51.209
medium duration, which is a little bit
00:13:51.219 --> 00:13:53.609
longer in in its in its length, with the
00:13:53.619 --> 00:13:55.089
ease out curve, it makes the content
00:13:55.099 --> 00:13:57.809
feel like it's landing softly.
00:13:57.819 --> 00:13:59.649
Um it's still responsive. It's still
00:13:59.659 --> 00:14:01.489
quick, but it's but it it but it gives
00:14:01.499 --> 00:14:03.689
it that subtle beat to land. And then
00:14:03.699 --> 00:14:05.049
when people, let's say this is an
00:14:05.059 --> 00:14:06.849
accordion, right? Then if you close it,
00:14:06.859 --> 00:14:07.889
you want it to get out of the way
00:14:07.899 --> 00:14:11.369
quickly. So, your exit curves and your
00:14:11.379 --> 00:14:14.649
exit your exit curves pair with uh that
00:14:14.659 --> 00:14:17.731
is always one rung shorter than your
00:14:17.741 --> 00:14:20.211
entrances and that helps it feel soft
00:14:20.221 --> 00:14:22.251
enter and quick delete. And so I think
00:14:22.261 --> 00:14:23.691
as you look through the system and you
00:14:23.701 --> 00:14:25.051
see those named intents and you see
00:14:25.061 --> 00:14:27.451
those patterns, it kind of it kind of
00:14:27.461 --> 00:14:28.971
creates this system that describes
00:14:28.981 --> 00:14:31.931
itself. And I think that that's really
00:14:31.941 --> 00:14:33.891
really really really really important
00:14:33.901 --> 00:14:35.771
when it comes to working with
00:14:35.781 --> 00:14:38.051
AI for motion.
00:14:38.061 --> 00:14:40.491
Um and before I dive into that, want to
00:14:40.501 --> 00:14:42.611
see did I do we answer your question or
00:14:42.621 --> 00:14:43.411
do we?
00:14:43.421 --> 00:14:47.251
>> Um yes, very very briefly uh
00:14:47.261 --> 00:14:49.011
basically cuz I'm I'm very interested in
00:14:49.021 --> 00:14:50.531
the composition of the semantic layer
00:14:50.541 --> 00:14:52.491
for you, but because you started with
00:14:52.501 --> 00:14:53.891
tier one.
00:14:53.901 --> 00:14:55.385
Um
00:14:55.395 --> 00:14:55.491
>> [snorts]
00:14:55.501 --> 00:14:58.131
>> it you were going off on the tier one is
00:14:58.141 --> 00:14:59.651
uh thing and explaining the the the
00:14:59.661 --> 00:15:02.651
scales that you've created in there. And
00:15:02.661 --> 00:15:04.571
you said something in there that I think
00:15:04.581 --> 00:15:07.971
is really important to kind of like
00:15:07.981 --> 00:15:11.731
um to highlight, which was the shared
00:15:11.741 --> 00:15:15.331
language piece. Okay. Because from my
00:15:15.341 --> 00:15:17.331
standpoint, the primitive tokens, this
00:15:17.341 --> 00:15:20.011
is one of my hot takes that I like. Uh
00:15:20.021 --> 00:15:22.851
the primitive tokens are effectively
00:15:22.861 --> 00:15:26.211
unnecessary in a design system. Hot
00:15:26.221 --> 00:15:29.691
take, okay? Now, the reason why people
00:15:29.701 --> 00:15:31.771
want primitive tokens is the shared
00:15:31.781 --> 00:15:35.171
language, okay? Because otherwise, like
00:15:35.181 --> 00:15:37.731
it doesn't really matter if the value
00:15:37.741 --> 00:15:40.211
that's assigned to your semantic token
00:15:40.221 --> 00:15:41.691
is and we'll go back to color for a
00:15:41.701 --> 00:15:43.291
minute just to make it easy. It doesn't
00:15:43.301 --> 00:15:45.491
matter if it's a hex code or a primitive
00:15:45.501 --> 00:15:47.731
token, it's still the same value. It's
00:15:47.741 --> 00:15:52.851
just that saying the hex code #FF5563
00:15:52.861 --> 00:15:56.971
is not as easy as saying uh red 500,
00:15:56.981 --> 00:15:59.371
right? That's a the shared language that
00:15:59.381 --> 00:16:01.091
it makes it much easier, have a much
00:16:01.101 --> 00:16:02.251
more uh
00:16:02.261 --> 00:16:05.331
more um obvious context about what that
00:16:05.341 --> 00:16:07.491
value is meant to represent so that it
00:16:07.501 --> 00:16:09.731
can be used in in the tier two semantic
00:16:09.741 --> 00:16:12.851
layer where it's appropriate. So, when
00:16:12.861 --> 00:16:15.451
it comes to um
00:16:15.461 --> 00:16:17.771
kind of uh uh
00:16:17.781 --> 00:16:20.452
um recommending uh the the approach of
00:16:20.462 --> 00:16:23.492
the primitive layer, I generally
00:16:23.502 --> 00:16:25.932
don't do anything about it myself. I
00:16:25.942 --> 00:16:29.292
leave that to organizations
00:16:29.302 --> 00:16:31.012
with guidance, of course, and saying,
00:16:31.022 --> 00:16:32.172
"Hey, you could do it this way, that
00:16:32.182 -->
00:16:33.852
way, or whatever." But, I don't really
00:16:33.862 --> 00:16:35.772
like to personally have opinions about
00:16:35.782 --> 00:16:37.732
what that is. Um
00:16:37.742 --> 00:16:40.012
you know, uh because there's a lot of uh
00:16:40.022 --> 00:16:41.332
you know, kind of writings about it.
00:16:41.342 --> 00:16:43.252
Now, I think for motion, because there
00:16:43.262 --> 00:16:46.572
isn't a lot out there, that people
00:16:46.582 --> 00:16:48.772
absolutely do need more guidance about
00:16:48.782 --> 00:16:52.612
what a motion scale, or t-shirt size, or
00:16:52.622 --> 00:16:54.692
whatever you like to call it, does look
00:16:54.702 --> 00:16:56.212
like, because there isn't a lot out
00:16:56.222 --> 00:16:57.772
there. So, I think that recommendation
00:16:57.782 --> 00:17:00.412
from your standpoint does make sense to
00:17:00.422 --> 00:17:02.932
just help them you know, these
00:17:02.942 --> 00:17:05.292
organizations uh that want to use
00:17:05.302 --> 00:17:07.612
motion, kind of get them into the groove
00:17:07.622 --> 00:17:10.132
of, "Okay, if you know, I know color, I
00:17:10.142 --> 00:17:12.572
know topography, uh what does it now
00:17:12.582 --> 00:17:14.252
look like for motion from the scale
00:17:14.262 --> 00:17:16.292
factor, so I can I can communicate
00:17:16.302 --> 00:17:17.772
motion." So,
00:17:17.782 --> 00:17:18.652
um
00:17:18.662 --> 00:17:19.812
so, I think, you know, there's this
00:17:19.822 --> 00:17:22.252
there's a spot for the scale in there,
00:17:22.262 --> 00:17:25.212
which I will concede the the hotter take
00:17:25.222 --> 00:17:28.612
uh from before. Now, the the second
00:17:28.622 --> 00:17:30.452
tier, right? There's semantic tier that
00:17:30.462 --> 00:17:33.052
that we like to talk about. Um I want to
00:17:33.062 --> 00:17:35.532
make sure that I'm clear about the
00:17:35.542 --> 00:17:37.412
actual token naming convention. I'm
00:17:37.422 --> 00:17:38.972
going to be a little bit um
00:17:38.982 --> 00:17:40.932
you know, specific on there. So, I think
00:17:40.942 --> 00:17:43.932
you mentioned uh token names such as
00:17:43.942 --> 00:17:47.452
motion use in and motion disclosure out.
00:17:47.462 --> 00:17:48.892
Was that accurate?
00:17:48.902 --> 00:17:50.452
>> Yeah, disclosure in, disclosure out.
00:17:50.462 --> 00:17:50.692
Yeah.
00:17:50.702 --> 00:17:52.892
>> Okay. Yeah. Uh well, there was a Was
00:17:52.902 --> 00:17:55.372
there a use before that? Use in? Or was
00:17:55.382 --> 00:17:57.412
Did I hear that wrong? Okay. So, what is
00:17:57.422 --> 00:18:00.412
What is the use mean?
00:18:00.422 --> 00:18:02.572
>> Um
00:18:02.582 --> 00:18:04.172
that you know, that's a great question.
00:18:04.182 --> 00:18:06.292
Uh the use is just the way that I
00:18:06.302 --> 00:18:09.052
situated it as I was building it. And it
00:18:09.062 --> 00:18:10.692
seemed to
00:18:10.702 --> 00:18:12.452
speak to it when I was working with it
00:18:12.462 --> 00:18:14.372
with AI. It helped it to understand. I
00:18:14.382 --> 00:18:16.732
mean, it's just sort of kind of got its
00:18:16.742 --> 00:18:19.212
way. The token is like motion use
00:18:19.222 --> 00:18:22.733
disclosure in, or motion use hover.
00:18:22.743 --> 00:18:24.733
But I think that that piece doesn't
00:18:24.743 --> 00:18:27.093
necessarily need to be there.
00:18:27.103 --> 00:18:28.333
I think that it could definitely just
00:18:28.343 --> 00:18:31.133
be, you know, motion hover or whatever
00:18:31.143 --> 00:18:33.333
you you had some really good
00:18:33.343 --> 00:18:37.013
ideas in in how you approach your naming
00:18:37.023 --> 00:18:40.053
and your intent. And I think ultimately,
00:18:40.063 --> 00:18:44.493
you know, my my goal with
00:18:44.503 --> 00:18:47.413
in in working with motion is is to just
00:18:47.423 --> 00:18:50.773
try to explore areas that we can improve
00:18:50.783 --> 00:18:53.613
it. And and I hope that the ideas that,
00:18:53.623 --> 00:18:55.453
you know, anyone, because it is such an
00:18:55.463 --> 00:18:58.053
opinionated topic and because people do
00:18:58.063 --> 00:19:00.293
have their own conventions, I feel like
00:19:00.303 --> 00:19:02.573
the the principles or the naming or
00:19:02.583 --> 00:19:05.413
things like that can they can be adapted
00:19:05.423 --> 00:19:07.573
to whatever person is working on. I
00:19:07.583 --> 00:19:08.493
mean,
00:19:08.503 --> 00:19:10.813
it doesn't have to be
00:19:10.823 --> 00:19:13.093
super strict at that level. I think what
00:19:13.103 --> 00:19:16.693
matters more is that you're just
00:19:16.703 --> 00:19:18.253
establishing that sort of shared
00:19:18.263 --> 00:19:20.893
vocabulary, not just for humans, but
00:19:20.903 --> 00:19:22.773
especially for AI consumers. I think
00:19:22.783 --> 00:19:24.493
that that's a big piece.
00:19:24.503 --> 00:19:25.093
>> Mhm.
00:19:25.103 --> 00:19:25.413
>> So.
00:19:25.423 --> 00:19:27.213
>> Well, I I prefer strict.
00:19:27.223 --> 00:19:27.813
>> [laughter]
00:19:27.823 --> 00:19:28.453
>> Well, that
00:19:28.463 --> 00:19:30.253
>> I prefer strict. That's That's my jam.
00:19:30.263 --> 00:19:32.093
Yeah, that's that's my jam.
00:19:32.103 --> 00:19:33.973
>> to design systems and it and adherence
00:19:33.983 --> 00:19:35.053
and stuff. I mean, that's, you know,
00:19:35.063 --> 00:19:36.573
that's good and especially for for
00:19:36.583 --> 00:19:38.413
e-vows and all those as well as you try
00:19:38.423 --> 00:19:39.853
to like think about how you would work
00:19:39.863 --> 00:19:40.693
through that. So.
00:19:40.703 --> 00:19:44.613
>> Yeah. Yeah. So so I want to talk more
00:19:44.623 --> 00:19:46.453
about the thinking behind it. And and
00:19:46.463 --> 00:19:47.893
again, some some things that I do
00:19:47.903 --> 00:19:50.173
mention in is on mode talking about
00:19:50.183 --> 00:19:53.453
motion cuz you know, when I was
00:19:53.463 --> 00:19:56.893
developing the the
architecture for Miz
00:19:56.903 --> 00:19:58.773
on mode and what that means for tokens
00:19:58.783 --> 00:20:01.493
and token naming, it was very important
00:20:01.503 --> 00:20:05.133
to me to to go back to design principles
00:20:05.143 --> 00:20:07.493
and the purpose of why we do the things
00:20:07.503 --> 00:20:09.253
that we do, the intent. That's been the
00:20:09.263 --> 00:20:11.373
purpose. So
00:20:11.383 --> 00:20:13.453
a couple of things pop out to me when it
00:20:13.463 --> 00:20:15.213
comes to motion.
00:20:15.223 --> 00:20:17.173
One of the things that pops out to me
00:20:17.183 --> 00:20:20.333
comes to motion is attention, okay?
00:20:20.343 --> 00:20:23.575
Where we will use motion to grab
00:20:23.585 --> 00:20:26.135
attention to items inside of our
00:20:26.145 --> 00:20:28.215
interface. So that, you know, this is
00:20:28.225 --> 00:20:30.055
very common for, you know, things like
00:20:30.065 --> 00:20:31.855
toasts, right? Where the toast will be a
00:20:31.865 --> 00:20:33.535
small message that appears potentially
00:20:33.545 --> 00:20:35.695
in the bottom of the screen. And if
00:20:35.705 --> 00:20:37.015
because it's a small message on
00:20:37.025 --> 00:20:39.735
potentially a large monitor, you want to
00:20:39.745 --> 00:20:41.455
draw attention
00:20:41.465 --> 00:20:44.655
to that thing in the moment. So instead
00:20:44.665 --> 00:20:46.895
of it just kind of appearing in in
00:20:46.905 --> 00:20:49.295
space, you potentially want to provide
00:20:49.305 --> 00:20:52.255
some motion to show that hey, I'm going
00:20:52.265 --> 00:20:53.615
to draw some attention to this. You
00:20:53.625 --> 00:20:55.855
probably want to look at this
00:20:55.865 --> 00:20:58.895
to to you know, move forward in in this
00:20:58.905 --> 00:21:00.895
this thing. Could you also do that with
00:21:00.905 --> 00:21:02.495
color? Absolutely, right? Something
00:21:02.505 --> 00:21:04.135
that's suddenly orange at the bottom of
00:21:04.145 --> 00:21:06.095
the screen or red, you will also
00:21:06.105 --> 00:21:08.615
probably pay attention to, but there is
00:21:08.625 --> 00:21:11.375
that you know, feeling of the motion
00:21:11.385 --> 00:21:14.455
that helps it you know, come in a little
00:21:14.465 --> 00:21:17.175
bit easier than just kind of appearing
00:21:17.185 --> 00:21:18.535
out of nowhere. Kind of gives a little
00:21:18.545 --> 00:21:19.735
bit more
00:21:19.745 --> 00:21:20.815
I'll say
00:21:20.825 --> 00:21:24.295
attention and the the
00:21:24.305 --> 00:21:26.335
giving it attention. Basically saying
00:21:26.345 --> 00:21:30.335
that like I'm giving it more um uh
00:21:30.345 --> 00:21:32.895
what's the word? Like uh
00:21:32.905 --> 00:21:34.975
a touch a human touch to the thing that
00:21:34.985 --> 00:21:36.855
it isn't just like an oversight kind of
00:21:36.865 --> 00:21:40.135
thing. So there's there's that piece of
00:21:40.145 --> 00:21:44.415
motion that I would capture in an intent
00:21:44.425 --> 00:21:46.855
and a semantic thing. So if we are
00:21:46.865 --> 00:21:49.495
trying to say hey, this thing needs to
00:21:49.505 --> 00:21:52.095
grab attention, um this is the the
00:21:52.105 --> 00:21:55.535
intent this this tier two semantic token
00:21:55.545 --> 00:21:58.175
for motion that you would attach to this
00:21:58.185 --> 00:21:59.895
to show that it's going to have. And
00:21:59.905 --> 00:22:03.055
then whatever values represent that
00:22:03.065 --> 00:22:04.775
attention-grabbing
00:22:04.785 --> 00:22:07.255
motion would be then applied via tier
00:22:07.265 --> 00:22:09.855
one through tier two. So that's one of
00:22:09.865 --> 00:22:14.095
the pieces. The other piece that I have
00:22:14.105 --> 00:22:14.815
um
00:22:14.825 --> 00:22:19.735
learned in motion design is the weight
00:22:19.745 --> 00:22:23.295
of something. Right? So when something
00:22:23.305 --> 00:22:26.416
that's very large comes into
00:22:26.426 --> 00:22:29.096
uh frame, maybe a panel or even a modal,
00:22:29.106 --> 00:22:30.856
there's a little bit of weight that
00:22:30.866 --> 00:22:33.016
comes to it that kind of is a slower
00:22:33.026 --> 00:22:35.296
kind of motion that comes in there that
00:22:35.306 --> 00:22:37.856
just shows that this is a heavier, more
00:22:37.866 --> 00:22:39.256
more uh
00:22:39.266 --> 00:22:41.616
you know, weighty or dense kind of thing
00:22:41.626 --> 00:22:42.816
that's going to come in and you're going
00:22:42.826 --> 00:22:44.616
to probably spend a little bit of time
00:22:44.626 --> 00:22:46.296
in here. Meanwhile, maybe something
00:22:46.306 --> 00:22:47.576
that's a little bit
00:22:47.586 --> 00:22:50.496
lighter or or or smaller might zip in a
00:22:50.506 --> 00:22:52.536
little faster just because of the size
00:22:52.546 --> 00:22:53.496
of it
00:22:53.506 --> 00:22:55.136
um overall. It's probably a little weird
00:22:55.146 --> 00:22:57.016
for something really small to kind of
00:22:57.026 --> 00:22:59.176
slowly lumber its way in. It just
00:22:59.186 --> 00:23:03.016
doesn't feel right, right? So so um
00:23:03.026 --> 00:23:06.496
that as an intention is also interesting
00:23:06.506 --> 00:23:08.336
in terms of saying, "My intention is is
00:23:08.346 --> 00:23:10.856
that there is a weighted feel behind
00:23:10.866 --> 00:23:13.776
this that you needs to convey uh this is
00:23:13.786 --> 00:23:16.096
important through through density or
00:23:16.106 --> 00:23:17.776
something like that." The really
00:23:17.786 --> 00:23:20.216
interesting thing about that
00:23:20.226 --> 00:23:21.536
feeling
00:23:21.546 --> 00:23:26.736
is that there might be a relationship
00:23:26.746 --> 00:23:30.336
from the size of the UI element
00:23:30.346 --> 00:23:33.136
to the motion being applied to it.
00:23:33.146 --> 00:23:39.336
And now we get into how a token might be
00:23:39.346 --> 00:23:42.656
influenced by the layout. And I did a
00:23:42.666 --> 00:23:45.256
very large
exploration on this just for
00:23:45.266 --> 00:23:47.416
for corner rounding. Just corner
00:23:47.426 --> 00:23:49.216
rounding, there's a relationship for
00:23:49.226 --> 00:23:50.896
when you want to turn rounding on to get
00:23:50.906 --> 00:23:53.336
those concentric rounding pieces, that's
00:23:53.346 --> 00:23:56.536
very ingrained with the layout. So if
00:23:56.546 --> 00:23:59.696
you talk about weight in a system like
00:23:59.706 --> 00:24:02.376
this, there is potentially some
00:24:02.386 --> 00:24:05.976
influence on the layout and whether or
00:24:05.986 --> 00:24:08.376
not you want motion to exist, the
00:24:08.386 --> 00:24:10.456
effectively a flag that says, "Please
00:24:10.466 --> 00:24:12.816
make this move." Um you could
00:24:12.826 --> 00:24:14.616
potentially say, "Okay, we want to make
00:24:14.626 --> 00:24:17.016
this move." And it already knows how to
00:24:17.026 --> 00:24:21.416
move just by how big it is. So
00:24:21.426 --> 00:24:23.931
I guess marinate on that for a minute.
00:24:23.941 --> 00:24:24.456
>> [laughter]
00:24:24.466 --> 00:24:27.416
>> I I like this a lot. This is you know,
00:24:27.426 --> 00:24:29.778
this is speaking to the big I love this
00:24:29.788 --> 00:24:32.138
conversation all around and this is why
00:24:32.148 --> 00:24:34.857
I I really like the opportunity. So,
00:24:34.867 --> 00:24:36.177
thank you again for having me on here
00:24:36.187 --> 00:24:38.937
because it's great as a developer or
00:24:38.947 --> 00:24:39.937
someone that's a little bit more
00:24:39.947 --> 00:24:41.898
developer focused to talk to someone
00:24:41.908 --> 00:24:43.297
that's that's, you know, more design
00:24:43.307 --> 00:24:44.857
focused. This is where I love this
00:24:44.867 --> 00:24:46.497
conversation because
00:24:46.507 --> 00:24:49.537
I I think part of what you're speaking
00:24:49.547 --> 00:24:52.497
to is part of what why I I wanted to do
00:24:52.507 --> 00:24:54.937
this this exploration in the in the
00:24:54.947 --> 00:24:56.617
whole in in the first place which is
00:24:56.627 --> 00:24:57.658
because
00:24:57.668 --> 00:25:00.457
capturing motion is is hard.
00:25:00.467 --> 00:25:00.658
>> Yeah.
00:25:00.668 --> 00:25:03.258
>> There's so many considerations to this.
00:25:03.268 --> 00:25:06.537
And I I you see you mentioned something
00:25:06.547 --> 00:25:08.138
before about the feeling.
00:25:08.148 --> 00:25:08.497
>> Right.
00:25:08.507 --> 00:25:10.857
>> And that's actually I I I started to
00:25:10.867 --> 00:25:12.337
write an article and actually the title
00:25:12.347 --> 00:25:13.857
of the article was how do you
00:25:13.867 --> 00:25:15.737
systematize a feeling?
00:25:15.747 --> 00:25:18.138
And um and I think it only is amplified,
00:25:18.148 --> 00:25:19.658
not to keep going back to the AI, but
00:25:19.668 --> 00:25:21.258
that's a big piece of, you know, the
00:25:21.268 --> 00:25:22.977
modern workflows, especially as a
00:25:22.987 --> 00:25:24.937
developer. Um but I think it's also
00:25:24.947 --> 00:25:26.457
that's also amplified when you're
00:25:26.467 --> 00:25:27.737
talking about working with with
00:25:27.747 --> 00:25:29.617
artificial intelligence because
00:25:29.627 --> 00:25:31.898
artificial intelligence can't visualize.
00:25:31.908 --> 00:25:33.258
And so, how do you take something that's
00:25:33.268 --> 00:25:35.138
visual and something that's a feeling
00:25:35.148 --> 00:25:37.537
and it and just and have it be able to
00:25:37.547 --> 00:25:39.417
work with something to produce good
00:25:39.427 --> 00:25:41.778
results when it can't it can't see the
00:25:41.788 --> 00:25:43.697
way we can, right? Um but we can talk
00:25:43.707 --> 00:25:44.857
about that in a second. I think what
00:25:44.867 --> 00:25:47.258
you're getting at is um
00:25:47.268 --> 00:25:50.697
like how to describe, you know,
00:25:50.707 --> 00:25:52.378
and this is a great example like you
00:25:52.388 --> 00:25:54.537
brought up the idea of weight and like
00:25:54.547 --> 00:25:56.337
the the idea of when you do approach it
00:25:56.347 --> 00:25:58.057
as the weight of something should
00:25:58.067 --> 00:26:00.457
influence the motion. And I think maybe
00:26:00.467 --> 00:26:02.258
this is why this is part of the reason
00:26:02.268 --> 00:26:04.457
why I'm so excited to continue to
00:26:04.467 --> 00:26:07.378
explore motion in design systems because
00:26:07.388 --> 00:26:09.857
I think that there comes
00:26:09.867 --> 00:26:11.097
a time
00:26:11.107 --> 00:26:13.057
where the
00:26:13.067 --> 00:26:16.177
tokens that we have naming and and
00:26:16.187 --> 00:26:19.857
intent definitely take you far
00:26:19.867 --> 00:26:21.617
and it can help create that shared
00:26:21.627 --> 00:26:23.658
vocabulary which is a huge piece.
00:26:23.668 --> 00:26:23.937
>> Mhm.
00:26:23.947 --> 00:26:26.138
>> And I think that, you know, technology
00:26:26.148 --> 00:26:27.817
and the way that you eventually execute
00:26:27.827 --> 00:26:29.778
it, there's a lot of of room there.
00:26:29.788 --> 00:26:31.417
Things are very um
00:26:31.427 --> 00:26:33.019
like we we can do a lot with just like
00:26:33.029 --> 00:26:36.099
CSS for example. Um, but I think that
00:26:36.109 --> 00:26:37.979
maybe one of the reasons
00:26:37.989 --> 00:26:41.779
that motion is so is become such a
00:26:41.789 --> 00:26:43.819
uh, back burner or an afterthought for a
00:26:43.829 --> 00:26:45.259
lot of people is because it's hard to
00:26:45.269 --> 00:26:46.739
come up with these considerations and
00:26:46.749 --> 00:26:49.059
how you work with it. And also because I
00:26:49.069 --> 00:26:51.259
think that most systems, even more
00:26:51.269 --> 00:26:53.539
advanced ones like, uh, or or ones that
00:26:53.549 --> 00:26:54.779
you would consider more advanced like,
00:26:54.789 --> 00:26:56.459
you know, Google's material or IBM's
00:26:56.469 --> 00:26:58.539
carbon, they do have some
considerations
00:26:58.549 --> 00:27:00.739
for motion, but it's it's largely it's
00:27:00.749 --> 00:27:02.939
key value pairs, right? These these
00:27:02.949 --> 00:27:05.539
tokens that we're talking about are are
00:27:05.549 --> 00:27:07.699
largely just these key value pairs. And
00:27:07.709 --> 00:27:09.339
then when you come to a certain level,
00:27:09.349 --> 00:27:11.539
that can only take you so far. And then
00:27:11.549 --> 00:27:13.819
you rely on notes or documentation to
00:27:13.829 --> 00:27:16.099
try to express when to use it. So part
00:27:16.109 --> 00:27:18.939
of what I've been really excited to to
00:27:18.949 --> 00:27:22.139
to explore with this topic is I want to
00:27:22.149 --> 00:27:24.379
help bridge this gap between design and
00:27:24.389 --> 00:27:26.859
development on how you capture this
00:27:26.869 --> 00:27:30.059
motion. And so I I've been working with
00:27:30.069 --> 00:27:33.179
this idea, um, that I there are these
00:27:33.189 --> 00:27:37.099
custom you can, you know, in the DTCG
00:27:37.109 --> 00:27:39.259
structure standard you can define custom
00:27:39.269 --> 00:27:41.979
tokens. So I've you know, I use these
00:27:41.989 --> 00:27:43.619
custom tokens called choreography
00:27:43.629 --> 00:27:46.339
tokens. And the idea that I have with
00:27:46.349 --> 00:27:48.819
these choreography tokens is that it's
00:27:48.829 --> 00:27:51.059
going to help push us beyond the bounds
00:27:51.069 --> 00:27:53.219
of what those key values can do. And it
00:27:53.229 --> 00:27:55.619
kind of takes it beyond just this simple
00:27:55.629 --> 00:27:57.779
pair and it makes it more of a blueprint
00:27:57.789 --> 00:27:59.419
for the motion together. And I think
00:27:59.429 --> 00:28:01.779
that that could be because I'm thinking
00:28:01.789 --> 00:28:03.539
of this from a development standpoint.
00:28:03.549 --> 00:28:06.579
And how would I take your considerations
00:28:06.589 --> 00:28:08.459
of weight and how it plays in and how
00:28:08.469 --> 00:28:09.819
would I apply that? And I think that
00:28:09.829 --> 00:28:11.819
that is what we would look to capture
00:28:11.829 --> 00:28:13.939
inside one of these sort of blueprint
00:28:13.949 --> 00:28:16.499
choreography tokens is
00:28:16.509 --> 00:28:19.659
it still references back to the other
00:28:19.669 --> 00:28:21.219
tiers. Where you're always referencing
00:28:21.229 --> 00:28:23.739
back to whether it's, you know, tier
00:28:23.749 --> 00:28:25.099
two. Even if you want to skip tier one,
00:28:25.109 --> 00:28:26.619
that's fine, you know. It's always it's
00:28:26.629 --> 00:28:28.659
always hearkening back to say,
00:28:28.669 --> 00:28:29.979
you know, here's how the motion should
00:28:29.989 --> 00:28:31.739
go. But what these choreography tokens
00:28:31.749 --> 00:28:34.780
let you do is capture
00:28:34.790 --> 00:28:37.700
more complex emotion than just a simple
00:28:37.710 --> 00:28:40.060
key value. So, it allows you to say,
00:28:40.070 --> 00:28:41.820
we'll take a modal for example, cuz that
00:28:41.830 --> 00:28:45.340
was one of your wait. Um I think and
00:28:45.350 --> 00:28:46.780
again, people could be opinionated on
00:28:46.790 --> 00:28:48.260
this, but I like I think when you work
00:28:48.270 --> 00:28:51.380
with a modal, it's nice to
00:28:51.390 --> 00:28:53.300
it creates a sort of elevated motion
00:28:53.310 --> 00:28:55.140
experience if you have the scrim coming
00:28:55.150 --> 00:28:57.140
first or some sort of overlay for the
00:28:57.150 --> 00:28:58.820
background and then the modal comes I'm
00:28:58.830 --> 00:29:00.540
going to go opposite of myself and then
00:29:00.550 --> 00:29:02.500
the modal comes out afterwards, right?
00:29:02.510 --> 00:29:04.060
And so,
00:29:04.070 --> 00:29:04.860
um
00:29:04.870 --> 00:29:07.500
so that you can make arguments in how
00:29:07.510 --> 00:29:09.340
you in code wise how you would go
00:29:09.350 --> 00:29:11.940
through executing that, but in a lot of
00:29:11.950 --> 00:29:13.860
cases when you're structuring your code,
00:29:13.870 --> 00:29:14.980
those are going to likely be two
00:29:14.990 --> 00:29:16.700
separate elements. Some people might say
00:29:16.710 --> 00:29:18.220
you can use CSS pseudo elements, but
00:29:18.230 --> 00:29:19.940
again, that will only take you so far.
00:29:19.950 --> 00:29:21.740
So, if you're you're talking about
00:29:21.750 --> 00:29:23.860
multiple elements with coordinated
00:29:23.870 --> 00:29:25.900
motion between them where maybe the
00:29:25.910 --> 00:29:27.260
scrim's lighter, so it comes in, but
00:29:27.270 --> 00:29:28.700
then the modal's heavier, so it takes
00:29:28.710 --> 00:29:30.020
longer.
00:29:30.030 --> 00:29:32.100
It's it's the idea in this choreography
00:29:32.110 --> 00:29:35.300
token of using your shared vocabulary,
00:29:35.310 --> 00:29:37.620
but creating this this sort of blueprint
00:29:37.630 --> 00:29:38.700
to say
00:29:38.710 --> 00:29:40.620
you know, and this now you created this
00:29:40.630 --> 00:29:42.420
choreography token that's like, you
00:29:42.430 --> 00:29:46.500
know, modal like choreography modal in
00:29:46.510 --> 00:29:48.500
or choreography modal entrance, whatever
00:29:48.510 --> 00:29:51.260
you might like to call it. And then you
00:29:51.270 --> 00:29:53.740
capture I want
00:29:53.750 --> 00:29:56.300
I want the scrim to come in at you know,
00:29:56.310 --> 00:29:59.020
a quick entrance and then I want a short
00:29:59.030 --> 00:30:01.740
delay and then I want the modal come in
00:30:01.750 --> 00:30:03.180
at a medium entrance. And I think that
00:30:03.190 --> 00:30:05.380
that right there to try to land the
00:30:05.390 --> 00:30:07.620
plane back to your like weight ideas
00:30:07.630 --> 00:30:09.620
that I think that whether you call it
00:30:09.630 --> 00:30:11.380
weight or whatever the consideration is
00:30:11.390 --> 00:30:12.700
there, that's where you fit that in,
00:30:12.710 --> 00:30:14.300
right? You can say, well, the modal's
00:30:14.310 --> 00:30:18.180
heavier and so it should have this type
00:30:18.190 --> 00:30:20.140
of of motion to go with it. It should
00:30:20.150 --> 00:30:23.260
have this this particular token. Um I
00:30:23.270 --> 00:30:24.660
think you can
00:30:24.670 --> 00:30:26.380
you can capture that within the
00:30:26.390 --> 00:30:27.900
choreography.
00:30:27.910 --> 00:30:28.420
>> Okay.
00:30:28.430 --> 00:30:29.420
>> I'm going to pause it for a second.
00:30:29.430 --> 00:30:31.300
>> Okay. So,
00:30:31.310 --> 00:30:32.500
I'm getting something very interesting
00:30:32.510 --> 00:30:34.700
in that because it's reminding me of
00:30:34.710 --> 00:30:36.942
some of the work that I used to do in
00:30:36.952 --> 00:30:39.742
After Effects and and Premiere many many
00:30:39.752 --> 00:30:43.142
years ago back in like the late 90s and
00:30:43.152 --> 00:30:45.102
working on a timeline.
00:30:45.112 --> 00:30:48.422
And knowing how to work on a timeline
00:30:48.432 --> 00:30:51.462
really helped me out when working with
00:30:51.472 --> 00:30:54.662
CSS keyframes later on because if you
00:30:54.672 --> 00:30:57.622
can visualize a CSS keyframe as a
00:30:57.632 --> 00:31:01.022
timeline, it's a lot easier to work with
00:31:01.032 --> 00:31:03.142
when when you can do that visualization.
00:31:03.152 --> 00:31:06.622
So, what this choreography is sounding
00:31:06.632 --> 00:31:09.182
like to me and this is probably a little
00:31:09.192 --> 00:31:10.942
different from what what what you might
00:31:10.952 --> 00:31:12.102
be
00:31:12.112 --> 00:31:14.542
doing exactly. But,
00:31:14.552 --> 00:31:15.982
what it sounds like to me is you're
00:31:15.992 --> 00:31:18.022
trying to capture
00:31:18.032 --> 00:31:19.622
what is what I would normally call a
00:31:19.632 --> 00:31:21.022
timeline
00:31:21.032 --> 00:31:23.942
for something for for because that
00:31:23.952 --> 00:31:26.302
timeline is going to have potentially
00:31:26.312 --> 00:31:28.502
several elements at play
00:31:28.512 --> 00:31:31.182
that all needs to kind of work together
00:31:31.192 --> 00:31:36.102
to to finish out in a final form, right?
00:31:36.112 --> 00:31:38.382
So, you have a starting kind of area,
00:31:38.392 --> 00:31:40.382
you have an ending area, and you have
00:31:40.392 --> 00:31:42.382
these elements that were all kind of
00:31:42.392 --> 00:31:44.142
come in and come out and move in these
00:31:44.152 --> 00:31:45.461
different ways and these different
00:31:45.471 --> 00:31:47.382
durations and easing patterns and stuff
00:31:47.392 --> 00:31:49.302
like that, but all happen across this
00:31:49.312 --> 00:31:52.062
one timeline and you want to capture
00:31:52.072 --> 00:31:54.542
that in a [snorts] way that
00:31:54.552 --> 00:31:57.622
has reusable pieces to it, right? So, if
00:31:57.632 --> 00:32:00.102
we wanted to say that you know, when
00:32:00.112 --> 00:32:02.142
when you know, something comes in and
00:32:02.152 --> 00:32:04.062
comes out like this disclosure and
00:32:04.072 --> 00:32:06.662
disclosure out, we can effectively put
00:32:06.672 --> 00:32:08.022
that token
00:32:08.032 --> 00:32:10.342
into the timeline on this particular
00:32:10.352 --> 00:32:12.862
element and it knows how to work with
00:32:12.872 --> 00:32:15.702
the rest of things that it's related to.
00:32:15.712 --> 00:32:17.822
So, you effectively are trying to make
00:32:17.832 --> 00:32:19.702
relational
00:32:19.712 --> 00:32:21.461
kind of tokens now, right? Is that's
00:32:21.471 --> 00:32:22.542
basically I think where we're getting
00:32:22.552 --> 00:32:23.342
at?
00:32:23.352 --> 00:32:24.782
>> Yeah, yeah. That's a that's a good way
00:32:24.792 --> 00:32:26.102
to think of it.
00:32:26.112 --> 00:32:28.582
I think that with sort of just like the
00:32:28.592 --> 00:32:29.942
disclosure and disclosure out and
00:32:29.952 --> 00:32:31.422
applying it to an element, I still think
00:32:31.432 --> 00:32:33.382
that you can have your system or your
00:32:33.392 --> 00:32:35.742
code base to reach for those tier two
00:32:35.752 --> 00:32:36.702
for a lot of things.
00:32:36.712 --> 00:32:37.182
>> Mhm.
00:32:37.192 --> 00:32:40.783
>> Um I think where the the choreography
00:32:40.793 --> 00:32:42.583
would be kind of the tier three level of
00:32:42.593 --> 00:32:44.823
like way you know component specific.
00:32:44.833 --> 00:32:46.263
That's the way I view it at least is
00:32:46.273 --> 00:32:49.823
like this it would be the idea that
00:32:49.833 --> 00:32:52.183
a modal, you know, this is why I think
00:32:52.193 --> 00:32:53.903
it's it's useful to that idea of
00:32:53.913 --> 00:32:56.303
functional motion and why it fits nicely
00:32:56.313 --> 00:32:58.743
into a system and to a design system
00:32:58.753 --> 00:33:00.903
because if you have a modal component,
00:33:00.913 --> 00:33:03.303
let's say you're building not even so so
00:33:03.313 --> 00:33:04.703
let's say it's not a website but it's a
00:33:04.713 --> 00:33:06.183
it's a dashboard or it's an application
00:33:06.193 --> 00:33:08.263
where you have things like drop downs
00:33:08.273 --> 00:33:09.543
and
00:33:09.553 --> 00:33:11.263
you know, modals and drawers that are
00:33:11.273 --> 00:33:13.463
more common than perhaps on a website.
00:33:13.473 --> 00:33:16.223
You you can you can
00:33:16.233 --> 00:33:21.183
capture the motion behavior of that of
00:33:21.193 --> 00:33:22.863
what a modal should do across the
00:33:22.873 --> 00:33:25.543
product in that sort of you know, blue
00:33:25.553 --> 00:33:27.623
printed choreography token and which I
00:33:27.633 --> 00:33:28.903
would be like a you know, like I think
00:33:28.913 --> 00:33:30.903
it'd be like a tier three token because
00:33:30.913 --> 00:33:33.663
it's it's related to a component. And so
00:33:33.673 --> 00:33:35.783
you would say like
00:33:35.793 --> 00:33:37.743
yeah, so the you
know, modal you would
00:33:37.753 --> 00:33:41.343
have a modal choreography modal in or
00:33:41.353 --> 00:33:42.623
choreography modal out. You can call
00:33:42.633 --> 00:33:44.703
them entrance or exits. Again, that that
00:33:44.713 --> 00:33:46.743
naming thing I think is
00:33:46.753 --> 00:33:49.263
is there's always
00:33:49.273 --> 00:33:50.743
there's always room for that in in the
00:33:50.753 --> 00:33:52.783
naming of it to to be you know, whatever
00:33:52.793 --> 00:33:54.583
works best for the for the team that's
00:33:54.593 --> 00:33:57.743
building it. But yeah, you know,
00:33:57.753 --> 00:33:59.143
modals and drawers and toast
00:33:59.153 --> 00:34:01.263
notifications. I think that those are
00:34:01.273 --> 00:34:03.503
great use cases for it and I think that
00:34:03.513 --> 00:34:06.143
it there's there are it's still sort of
00:34:06.153 --> 00:34:08.623
component based but
00:34:08.633 --> 00:34:10.663
it doesn't have to be
00:34:10.673 --> 00:34:12.623
coordinated
00:34:12.633 --> 00:34:14.863
with across multiple elements. It could
00:34:14.873 --> 00:34:17.103
be a single element too. So sometimes
00:34:17.113 --> 00:34:20.023
what you have, you know, it's CSS I
00:34:20.033 --> 00:34:21.063
don't want to get too far in the weeds
00:34:21.073 --> 00:34:22.423
cuz you know, you can make arguments
00:34:22.433 --> 00:34:24.143
that maybe you could work something out
00:34:24.153 --> 00:34:26.583
in CSS, maybe you couldn't. The thing
00:34:26.593 --> 00:34:28.463
you know, two things keep advancing and
00:34:28.473 --> 00:34:30.703
the cool thing about development is that
00:34:30.713 --> 00:34:32.143
there's usually more than one way to
00:34:32.153 --> 00:34:33.583
solve the problem which is what kind of
00:34:33.593 --> 00:34:35.463
makes it so much fun.
00:34:35.473 --> 00:34:36.103
Um
00:34:36.113 --> 00:34:39.343
and but like multi-phase animation too.
00:34:39.353 --> 00:34:42.424
So not just not just coordinating multi
00:34:42.434 --> 00:34:45.104
elements or like staggering cards in a
00:34:45.114 --> 00:34:47.384
grid that loads together or list items,
00:34:47.394 --> 00:34:49.024
but even just like we'll say like a
00:34:49.034 --> 00:34:51.664
switch, like a like a toggle switch you
00:34:51.674 --> 00:34:53.864
know, input field. If you wanted it to
00:34:53.874 --> 00:34:56.584
be more playful and have that you know,
00:34:56.594 --> 00:34:57.824
those motion principles that you're
00:34:57.834 --> 00:34:59.584
talking about of like
00:34:59.594 --> 00:35:01.184
when you mention things like weight, you
00:35:01.194 --> 00:35:02.744
know, that that really
00:35:02.754 --> 00:35:04.384
plays into like
00:35:04.394 --> 00:35:05.624
motion
00:35:05.634 --> 00:35:07.024
uh foundation principles and how the
00:35:07.034 --> 00:35:08.664
principles of animation and things like
00:35:08.674 --> 00:35:10.784
that. And so, with those principles of
00:35:10.794 --> 00:35:12.424
innovation, you have things like
00:35:12.434 --> 00:35:15.424
anticipation and then hold and then
00:35:15.434 --> 00:35:16.944
delay and and you know, you have your
00:35:16.954 --> 00:35:18.624
anticipations and your delays and your
00:35:18.634 --> 00:35:20.504
movements and your travel and your your
00:35:20.514 --> 00:35:22.104
bounce back. And so, that would be like
00:35:22.114 --> 00:35:25.144
multi-phase, right? And sometimes you
00:35:25.154 --> 00:35:26.664
can make that work with CSS, sometimes
00:35:26.674 --> 00:35:28.664
you can't. And so, where what what
00:35:28.674 --> 00:35:30.904
becomes interesting about the the
00:35:30.914 --> 00:35:33.144
choreography level
00:35:33.154 --> 00:35:35.264
is that it it starts to cross into this
00:35:35.274 --> 00:35:37.304
area where we're going to be trying to
00:35:37.314 --> 00:35:39.944
capture more complex motion and then
00:35:39.954 --> 00:35:42.424
handing it off to the developer in a way
00:35:42.434 --> 00:35:44.064
where then they could take a look at and
00:35:44.074 --> 00:35:47.304
say if you know, either this is a a CSS
00:35:47.314 --> 00:35:49.504
done token or this is done through like
00:35:49.514 --> 00:35:52.704
a small web animations API JavaScript
00:35:52.714 --> 00:35:55.344
runtime. But also, what I think is is
00:35:55.354 --> 00:35:57.184
interesting about the idea of the
00:35:57.194 --> 00:35:59.464
choreography tokens or this sort of
00:35:59.474 --> 00:36:01.464
blueprint is that it can be because it's
00:36:01.474 --> 00:36:04.024
just a JSON formatted token, it can be
00:36:04.034 --> 00:36:05.984
platform agnostic. So, if you are
00:36:05.994 --> 00:36:09.544
building something like an an uh iOS
00:36:09.554 --> 00:36:12.064
application where you would be working
00:36:12.074 --> 00:36:13.664
in something like Swift with different
00:36:13.674 --> 00:36:16.264
motion considerations available to you
00:36:16.274 --> 00:36:17.944
on the Apple platform like springs and
00:36:17.954 --> 00:36:21.664
stuff, you can still utilize these this
00:36:21.674 --> 00:36:24.144
idea of capturing motion as a blueprint,
00:36:24.154 --> 00:36:25.704
but it can be adapted into your
00:36:25.714 --> 00:36:28.464
development environment. So,
00:36:28.474 --> 00:36:28.904
yeah.
00:36:28.914 --> 00:36:29.224
>> Okay.
00:36:29.234 --> 00:36:30.744
>> Oh, but there Oh, one other thing I
00:36:30.754 --> 00:36:31.344
wanted
00:36:31.354 --> 00:36:33.624
>> to throw in there. Sorry, cuz I I I I
00:36:33.634 --> 00:36:34.664
wanted to say it earlier and it slipped
00:36:34.674 --> 00:36:37.064
my brain. One of the things about this,
00:36:37.074 --> 00:36:38.864
I like the idea of what you said about
00:36:38.874 --> 00:36:41.384
it kind of capturing a timeline. And and
00:36:41.394 --> 00:36:43.544
I do that's a good way of putting it
00:36:43.554 --> 00:36:45.626
like you cuz you are kind of saying
00:36:45.636 --> 00:36:47.346
like, here are the elements that would
00:36:47.356 --> 00:36:48.746
be
involved. Like, here's the scrim,
00:36:48.756 --> 00:36:51.506
here's the modal element, and here's how
00:36:51.516 --> 00:36:53.186
they should work. Scrim first, this
00:36:53.196 --> 00:36:56.186
entrance, this exit, delay, then this,
00:36:56.196 --> 00:36:57.386
you know, you are kind of laying out a
00:36:57.396 --> 00:37:00.146
timeline. But, what I've also built into
00:37:00.156 --> 00:37:02.346
these choreography tokens that I'm
00:37:02.356 --> 00:37:03.506
really
00:37:03.516 --> 00:37:05.066
happy with that I think has a lot of
00:37:05.076 --> 00:37:07.386
merit is each one of these blueprint and
00:37:07.396 --> 00:37:10.026
choreography tokens contains within it
00:37:10.036 --> 00:37:12.586
AI intent that helps it to understand
00:37:12.596 --> 00:37:14.746
when the agent might reach for it, such
00:37:14.756 --> 00:37:16.586
as a modal or disclosure if you're using
00:37:16.596 --> 00:37:18.386
it to build it. But, more importantly to
00:37:18.396 --> 00:37:21.826
me, it contains reduced motion
00:37:21.836 --> 00:37:24.666
considerations in the blueprint. So,
00:37:24.676 --> 00:37:27.026
you're essentially saying, here's how a
00:37:27.036 --> 00:37:29.706
modal should behave,
00:37:29.716 --> 00:37:31.226
but here's how it should behave under
00:37:31.236 --> 00:37:33.626
reduced motion. And it's captured within
00:37:33.636 --> 00:37:36.266
one single token. So, cuz I think, you
00:37:36.276 --> 00:37:38.906
know, reduced motion doesn't mean no
00:37:38.916 --> 00:37:41.106
motion. It just means the reduced,
00:37:41.116 --> 00:37:44.706
right? So, if you have something like,
00:37:44.716 --> 00:37:46.306
let's say a
00:37:46.316 --> 00:37:48.106
on the example of the motion design
00:37:48.116 --> 00:37:50.226
systems.org site that I I have out
00:37:50.236 --> 00:37:51.546
there,
00:37:51.556 --> 00:37:53.346
you know, I use the list example for
00:37:53.356 --> 00:37:55.266
this because if you had a couple items
00:37:55.276 --> 00:37:57.146
in a list that are like animating up,
00:37:57.156 --> 00:37:58.706
right? Um
00:37:58.716 --> 00:37:59.906
and they they might animate in, they
00:37:59.916 --> 00:38:01.346
might animate out. There's some movement
00:38:01.356 --> 00:38:03.266
to it. But, then under reduced motion,
00:38:03.276 --> 00:38:05.946
that same token becomes a fade in and a
00:38:05.956 --> 00:38:07.946
fade out. And I think that that's
00:38:07.956 --> 00:38:09.906
important if we are going to be going
00:38:09.916 --> 00:38:11.746
down this rabbit hole of how do we
00:38:11.756 --> 00:38:14.066
systematize motion, you need to consider
00:38:14.076 --> 00:38:16.066
reduced motion the whole way through.
00:38:16.076 --> 00:38:18.426
And and it's considered in this system
00:38:18.436 --> 00:38:20.266
from from all the from all the different
00:38:20.276 --> 00:38:21.986
tokens all the way through into here.
00:38:21.996 --> 00:38:23.666
And it lets you, as you're developing
00:38:23.676 --> 00:38:25.626
this motion experience, say, here's how
00:38:25.636 --> 00:38:27.386
I think this motion should behave for
00:38:27.396 --> 00:38:29.866
the for the UI, and here's how it should
00:38:29.876 --> 00:38:32.746
adapt itself if the person prefers
00:38:32.756 --> 00:38:34.786
reduced motion. And I think that that's
00:38:34.796 --> 00:38:36.906
a pretty cool angle of it as well.
00:38:36.916 --> 00:38:38.866
>> It is. And you know what? It it just
00:38:38.876 --> 00:38:41.506
goes to show how thoughtful you've been
00:38:41.516 --> 00:38:43.706
on this particular
00:38:43.716 --> 00:38:45.466
topic in particular, right? Cuz the
00:38:45.476 --> 00:38:48.387
reduced motion thing is a great
00:38:48.397 --> 00:38:50.427
uh kind of point to bring up here cuz
00:38:50.437 --> 00:38:51.747
absolutely when we're talking about
00:38:51.757 --> 00:38:53.947
motion and providing it to users, you
00:38:53.957 --> 00:38:57.547
also must talk about how you are going
00:38:57.557 --> 00:38:59.787
to uh handle reduced motion for those
00:38:59.797 --> 00:39:01.707
folks who who do not want the
00:39:01.717 --> 00:39:05.467
the motion uh to be so dramatic. And for
00:39:05.477 --> 00:39:06.947
many um
00:39:06.957 --> 00:39:09.227
applications who are even just
00:39:09.237 --> 00:39:10.867
considering it in the first place cuz
00:39:10.877 --> 00:39:12.947
lots of applications don't care about
00:39:12.957 --> 00:39:15.347
reduced motion. Lots of them, right? But
00:39:15.357 --> 00:39:17.307
in an area where they are caring about
00:39:17.317 --> 00:39:19.707
it, uh they do so in a very limited
00:39:19.717 --> 00:39:22.627
fashion. Um such even myself included
00:39:22.637 --> 00:39:23.787
because again, I don't deal with a lot
00:39:23.797 --> 00:39:25.627
of motion. But
00:39:25.637 --> 00:39:28.587
what I do end up putting into much of
00:39:28.597 --> 00:39:31.067
the work that does have motion is a
00:39:31.077 --> 00:39:34.027
basic catch-all situation, right? Which
00:39:34.037 --> 00:39:35.747
effectively says, "Okay, if there's
00:39:35.757 --> 00:39:39.427
reduced motion, then reduce the um
00:39:39.437 --> 00:39:41.947
duration down to something very
00:39:41.957 --> 00:39:43.387
uh very small." Right? You don't put it
00:39:43.397 --> 00:39:45.587
at zero, but you put it at a very small
00:39:45.597 --> 00:39:48.107
um because the zeros might break the
00:39:48.117 --> 00:39:50.227
actual result of of some of these these
00:39:50.237 --> 00:39:52.627
animations. So, you want to reduce the
00:39:52.637 --> 00:39:54.827
duration for these things uh to
00:39:54.837 --> 00:39:57.027
something small, potentially do a linear
00:39:57.037 --> 00:39:58.787
ease, things like that. So, there's
00:39:58.797 --> 00:40:00.467
there's um
00:40:00.477 --> 00:40:02.427
best practices if you're going to do a
00:40:02.437 --> 00:40:06.067
blanket uh reduced motion kind of rule,
00:40:06.077 --> 00:40:07.947
but I think there's something really
00:40:07.957 --> 00:40:13.347
nice about the the thoughtfulness of um
00:40:13.357 --> 00:40:14.867
saying
00:40:14.877 --> 00:40:17.427
reduced motion is another mode that
00:40:17.437 --> 00:40:20.347
could be influenced on the experience,
00:40:20.357 --> 00:40:21.787
right? Cuz I talk about modes in here
00:40:21.797 --> 00:40:23.227
about like, you know, you can do high
00:40:23.237 --> 00:40:25.027
contrast, light, dark mode. I mean,
00:40:25.037 --> 00:40:27.387
these are all user preferences that are
00:40:27.397 --> 00:40:28.427
potentially going to affect the
00:40:28.437 --> 00:40:30.867
experience. Reduced motion is another
00:40:30.877 --> 00:40:32.747
preference that will affect the user
00:40:32.757 --> 00:40:35.947
experience and therefore, we should have
00:40:35.957 --> 00:40:38.947
new values to the semantic layer or the
00:40:38.957 --> 00:40:42.427
component layer that then affects uh the
00:40:42.437 --> 00:40:45.547
motion in ways that that we are
00:40:45.557 --> 00:40:48.827
curating, right? So, having that
00:40:48.837 --> 00:40:51.708
as a facet uh definitely makes sense to
00:40:51.718 --> 00:40:53.508
me and I and you know, really thoughtful
00:40:53.518 --> 00:40:56.108
on that. Um
00:40:56.118 --> 00:40:57.948
There the one of the things I marked out
00:40:57.958 --> 00:40:59.908
on here also is we you talked about it
00:40:59.918 --> 00:41:01.908
earlier and I've also thought about this
00:41:01.918 --> 00:41:05.148
too is the difference between expressive
00:41:05.158 --> 00:41:08.628
and functional motion, right? And the
00:41:08.638 --> 00:41:11.228
thing from much of my
00:41:11.238 --> 00:41:13.628
experience in design tokens outside of
00:41:13.638 --> 00:41:17.588
motion has been all about function.
00:41:17.598 --> 00:41:20.588
Because when we create an experience,
00:41:20.598 --> 00:41:23.028
it's meant to be large when we first
00:41:23.038 --> 00:41:24.628
create it's largely meant to be
00:41:24.638 --> 00:41:26.748
functional. That's where the wireframes
00:41:26.758 --> 00:41:29.588
come from, the IA, all of that research
00:41:29.598 --> 00:41:32.348
and really low-fidelity work comes to
00:41:32.358 --> 00:41:34.508
try to um
00:41:34.518 --> 00:41:37.188
kind of solidify what the what the
00:41:37.198 --> 00:41:39.628
solution of the problem is. And then
00:41:39.638 --> 00:41:41.308
afterwards, we add the form. We do the
00:41:41.318 --> 00:41:43.028
paint job. Here's the color, the
00:41:43.038 --> 00:41:46.348
typography, and expressing ourselves.
00:41:46.358 --> 00:41:47.468
So,
00:41:47.478 --> 00:41:49.588
when it comes to these two kinds of
00:41:49.598 --> 00:41:50.828
motion, the expression and the
00:41:50.838 --> 00:41:53.148
functional,
00:41:53.158 --> 00:41:54.028
are
00:41:54.038 --> 00:41:56.788
are you separating them in terms of the
00:41:56.798 --> 00:41:58.988
way that you are separating maybe
00:41:58.998 --> 00:42:01.068
tokens? Cuz like again, the way that I'm
00:42:01.078 --> 00:42:03.268
thinking about it is is well, you know,
00:42:03.278 --> 00:42:06.068
there's the the the structure is is
00:42:06.078 --> 00:42:07.948
meant to be functional. So, maybe
00:42:07.958 --> 00:42:09.988
there's functional motion that's that's
00:42:09.998 --> 00:42:12.948
embedded into there versus expressive
00:42:12.958 --> 00:42:16.108
motion that's meant to convey a feeling,
00:42:16.118 --> 00:42:19.428
a brand, a a story, right? That's not
00:42:19.438 --> 00:42:21.388
necessarily providing any functional
00:42:21.398 --> 00:42:22.788
means. Again, it's it's going back to
00:42:22.798 --> 00:42:24.228
that attention thing. Like this is not
00:42:24.238 --> 00:42:26.428
meant to necessarily grab attention as
00:42:26.438 --> 00:42:28.348
much as it might be grabbing attention
00:42:28.358 --> 00:42:30.908
just as an artifact of the feeling that
00:42:30.918 --> 00:42:32.708
I want to convey. So,
00:42:32.718 --> 00:42:35.348
are you separating them? Are you keeping
00:42:35.358 --> 00:42:37.668
them the same How are you How are you
00:42:37.678 --> 00:42:39.988
having them coexist?
00:42:39.998 --> 00:42:41.948
>> Yeah, that's a great question. Um I'm I
00:42:41.958 --> 00:42:44.628
have not in this particular system that
00:42:44.638 --> 00:42:46.228
I've worked with so far that I created
00:42:46.238 --> 00:42:48.428
so far, I've not separated them. It's
00:42:48.438 --> 00:42:50.628
just more of um
00:42:50.638 --> 00:42:54.510
reaching for the the values
00:42:54.520 --> 00:42:56.750
that get the that speak to the specific
00:42:56.760 --> 00:42:59.070
job that you're doing. And so,
00:42:59.080 --> 00:43:01.750
um, when it's when I think of uh
00:43:01.760 --> 00:43:03.310
something functional, we talked about
00:43:03.320 --> 00:43:05.390
like hovers and focuses. Those are types
00:43:05.400 --> 00:43:07.310
of motion that and they're extremely
00:43:07.320 --> 00:43:09.670
common, so you want them to be quick and
00:43:09.680 --> 00:43:11.030
responsive and help the site feel
00:43:11.040 --> 00:43:12.110
functional. And I think, you know,
00:43:12.120 --> 00:43:13.950
things like accordions,
00:43:13.960 --> 00:43:15.670
modals, dialogues, toasts, those are
00:43:15.680 --> 00:43:17.990
again, those are functional that those
00:43:18.000 --> 00:43:19.230
those ones actually hold on, maybe I
00:43:19.240 --> 00:43:20.190
shouldn't go to those yet cuz those
00:43:20.200 --> 00:43:21.910
actually kind of cross. You can you can
00:43:21.920 --> 00:43:23.430
you can say that something like a toast,
00:43:23.440 --> 00:43:25.950
for example, is functional but also
00:43:25.960 --> 00:43:27.310
expressive. Um,
00:43:27.320 --> 00:43:29.310
so I think, you know, we'll take an
00:43:29.320 --> 00:43:31.190
accordion, I think, is a good example of
00:43:31.200 --> 00:43:33.830
functional motion, right? And so, it's
00:43:33.840 --> 00:43:36.070
really just my approach to that so far
00:43:36.080 --> 00:43:37.870
has been kind of what we talked about
00:43:37.880 --> 00:43:39.870
earlier. It's just making sure that we
00:43:39.880 --> 00:43:43.430
have good vocabulary. We have enough
00:43:43.440 --> 00:43:45.390
enough tokens to be able to reach for
00:43:45.400 --> 00:43:47.910
the proper duration. So, you you're
00:43:47.920 --> 00:43:50.630
going to reach for I I don't remember my
00:43:50.640 --> 00:43:52.750
I I should. I don't remember my token
00:43:52.760 --> 00:43:54.830
values off the top of my head, but like,
00:43:54.840 --> 00:43:55.710
you know, you're going to reach for
00:43:55.720 --> 00:43:57.510
something like a
00:43:57.520 --> 00:43:59.670
240 milliseconds, 300 milliseconds,
00:43:59.680 --> 00:44:01.070
something along those lines. Like,
00:44:01.080 --> 00:44:02.470
you're going to reach for sort of a more
00:44:02.480 --> 00:44:04.270
of a middle ground
00:44:04.280 --> 00:44:06.350
uh token combined with an entrance
00:44:06.360 --> 00:44:09.110
curve, um, which is again, just the name
00:44:09.120 --> 00:44:10.510
that I would pick for for it. It would
00:44:10.520 --> 00:44:12.070
be an ease out, but again, I think
00:44:12.080 --> 00:44:13.990
calling it entrance is that that's the
00:44:14.000 --> 00:44:15.110
point is that you're giving that
00:44:15.120 --> 00:44:16.830
vocabulary and speaking to the intent.
00:44:16.840 --> 00:44:19.550
So, you know, a medium entrance
00:44:19.560 --> 00:44:22.070
gives that accordion time to come in and
00:44:22.080 --> 00:44:24.510
feel like it settles while still being
00:44:24.520 --> 00:44:26.270
you're still making it feel responsive
00:44:26.280 --> 00:44:28.190
to a user. If it's as a dashboard
00:44:28.200 --> 00:44:29.590
application that you're developing and
00:44:29.600 --> 00:44:30.910
people are going to use it frequently
00:44:30.920 --> 00:44:32.910
and come back, they're not going to get
00:44:32.920 --> 00:44:34.110
they're not going to feel like it's
00:44:34.120 --> 00:44:35.470
lagging as they're clicking around
00:44:35.480 --> 00:44:36.950
quickly if they're using it to get
00:44:36.960 --> 00:44:39.070
things done. And um and that's the same
00:44:39.080 --> 00:44:41.310
principle then way it like when you have
00:44:41.320 --> 00:44:43.230
the exit, you're you're using the
00:44:43.240 --> 00:44:45.950
specific exit curve, uh but with a wrong
00:44:45.960 --> 00:44:47.230
shorter so that it feels like it
00:44:47.240 --> 00:44:48.670
collapses faster and gets out of the
00:44:48.680 --> 00:44:50.510
way. So,
00:44:50.520 --> 00:44:53.110
it's just the way I've approached the
00:44:53.120 --> 00:44:54.671
that sort of functional piece has been
00:44:54.681 --> 00:44:56.591
more so just reaching for the lower
00:44:56.601 --> 00:44:58.951
rungs of the of the duration ladder and
00:44:58.961 --> 00:45:01.391
reaching for the easing curves that
00:45:01.401 --> 00:45:03.911
speak more to, you know, entrances and
00:45:03.921 --> 00:45:05.991
exits or for something like a hover,
00:45:06.001 -->
00:45:08.271
just a standard curve that's kind of the
00:45:08.281 --> 00:45:10.671
same both forward and backwards, right?
00:45:10.681 --> 00:45:11.991
You know, sort of a standard S curve
00:45:12.001 --> 00:45:14.951
easing in and out. And so, um
00:45:14.961 --> 00:45:16.751
that that's where I I think that
00:45:16.761 --> 00:45:18.671
functional fits in. And then when I
00:45:18.681 --> 00:45:21.831
think of storytelling motion,
00:45:21.841 --> 00:45:23.311
uh the the first example that comes to
00:45:23.321 --> 00:45:25.751
mind is is especially as a developer and
00:45:25.761 --> 00:45:28.031
building a lot of of websites, I think,
00:45:28.041 --> 00:45:29.991
you know, uh it's the text reveals,
00:45:30.001 --> 00:45:31.431
right? Which could happen on scroll or
00:45:31.441 --> 00:45:33.671
it could be the page loads and as you're
00:45:33.681 --> 00:45:35.871
looking at your hero element, the text
00:45:35.881 --> 00:45:37.991
comes up from behind the invisible wall
00:45:38.001 --> 00:45:40.351
in the corner, right? That to me, that's
00:45:40.361 --> 00:45:42.671
the expressive or the storytelling
00:45:42.681 --> 00:45:44.831
motion. That is the one that draws the
00:45:44.841 --> 00:45:46.711
attention and and kind of creates that
00:45:46.721 --> 00:45:48.791
sense of hierarchy, um through the
00:45:48.801 --> 00:45:51.511
movement. But it's also that's the piece
00:45:51.521 --> 00:45:54.751
that that can take 1.2 seconds or 1,200
00:45:54.761 --> 00:45:55.831
milliseconds, whatever you want to think
00:45:55.841 --> 00:45:57.271
of it as. Like that's the thing that can
00:45:57.281 --> 00:45:59.671
take longer, right? Uh not not the
00:45:59.681 --> 00:46:01.031
accordion, not the button. That's going
00:46:01.041 --> 00:46:03.631
to feel slow. And so it it really just
00:46:03.641 --> 00:46:06.231
it's almost speaks to that intent
00:46:06.241 --> 00:46:08.991
that that we've talked about just in in
00:46:09.001 --> 00:46:10.431
actual use too. Like it's it's the
00:46:10.441 --> 00:46:13.791
intent of what is this
00:46:13.801 --> 00:46:15.871
elements or doing, you know? Like what
00:46:15.881 --> 00:46:18.111
is the motion behind this and what is
00:46:18.121 --> 00:46:20.151
the intent of that motion? Is it meant
00:46:20.161 --> 00:46:22.151
to be responsive and communicative to
00:46:22.161 --> 00:46:24.231
the to the user or is it meant to just
00:46:24.241 --> 00:46:27.351
kind of provide that atmospheric uh
00:46:27.361 --> 00:46:28.871
attention that we want to draw their
00:46:28.881 --> 00:46:30.871
eye? So I haven't separated them, but
00:46:30.881 --> 00:46:32.311
that's kind of just the way that I've
00:46:32.321 --> 00:46:34.951
I've been approaching it. And and
00:46:34.961 --> 00:46:36.711
to take 2 seconds to go beyond that, I
00:46:36.721 --> 00:46:39.031
think that the idea of the text reveal
00:46:39.041 --> 00:46:40.071
is on
00:46:40.081 --> 00:46:42.071
is one of the other examples too of like
00:46:42.081 --> 00:46:44.511
why I um
00:46:44.521 --> 00:46:46.351
why I wanted to do this too and and try
00:46:46.361 --> 00:46:49.151
to work together um
00:46:49.161 --> 00:46:50.551
and have conversations like this with
00:46:50.561 --> 00:46:52.631
with designers and stuff to learn more
00:46:52.641 --> 00:46:54.231
about this process and and to try to
00:46:54.241 --> 00:46:55.911
help create these choreography tokens
00:46:55.921 --> 00:46:58.473
and ways to improve this handoff. That's
00:46:58.483 --> 00:47:00.632
the That's a big piece of what I was
00:47:00.642 --> 00:47:02.872
hoping to eventually, you know, get
00:47:02.882 --> 00:47:04.513
better at and achieve. And we could talk
00:47:04.523 --> 00:47:06.112
about maybe Figma motion in a little in
00:47:06.122 --> 00:47:09.152
a minute. But, um you know, improving
00:47:09.162 --> 00:47:10.313
the handoff between design and
00:47:10.323 --> 00:47:11.233
development, I think it's going to be a
00:47:11.243 --> 00:47:13.073
big piece of this. And that's kind of
00:47:13.083 --> 00:47:14.513
what a big piece of what drew me to it
00:47:14.523 --> 00:47:16.473
because there's so many times in my
00:47:16.483 --> 00:47:19.513
career, um as a developer, you know,
00:47:19.523 --> 00:47:21.513
motion because it's complicated, it's
00:47:21.523 --> 00:47:24.073
hard to convey, and and it it is often
00:47:24.083 --> 00:47:26.273
thought of as like a polish that you add
00:47:26.283 --> 00:47:27.313
at the end, especially if we're
00:47:27.323 --> 00:47:29.152
storytelling. You get these static
00:47:29.162 --> 00:47:31.073
designs, and then you'll get a comment
00:47:31.083 --> 00:47:32.513
that says like, "Here's your static
00:47:32.523 --> 00:47:34.273
design." And here's a comment that says,
00:47:34.283 --> 00:47:36.632
"Oh, for this particular piece,
00:47:36.642 --> 00:47:39.112
um we would like the text to animate in.
00:47:39.122 --> 00:47:41.152
Um and here are two or three web
00:47:41.162 --> 00:47:43.033
reference sites that we saw that we
00:47:43.043 --> 00:47:44.912
really like the way they do it." And so,
00:47:44.922 --> 00:47:47.793
as a developer, you're you're it it's
00:47:47.803 --> 00:47:51.273
it's always falling on on you to reverse
00:47:51.283 --> 00:47:54.833
engineer what has been done or, you
00:47:54.843 --> 00:47:56.912
know, rely on picking the right areas to
00:47:56.922 --> 00:47:58.793
try to recreate this motion experience.
00:47:58.803 --> 00:48:00.592
And I think that what a part of the goal
00:48:00.602 --> 00:48:02.112
here is that I'm hoping that there's a
00:48:02.122 --> 00:48:03.833
way that the team can work together, but
00:48:03.843 --> 00:48:06.392
we can also empower the designers more
00:48:06.402 --> 00:48:08.152
to say, "Here's the cute motion
00:48:08.162 --> 00:48:10.753
experience I've created as the designer,
00:48:10.763 --> 00:48:12.953
and I've captured it in a token.
00:48:12.963 --> 00:48:14.592
Just use this token. You
don't have to
00:48:14.602 --> 00:48:16.313
reverse engineer anything. You don't
00:48:16.323 --> 00:48:17.273
have to make sure you're picking it
00:48:17.283 --> 00:48:19.672
right. Just like, here it is." And And,
00:48:19.682 --> 00:48:21.513
you know, now every type of motion
00:48:21.523 --> 00:48:22.473
throughout the product or the
00:48:22.483 --> 00:48:24.193
application can behave the same.
00:48:24.203 --> 00:48:24.953
>> Yeah.
00:48:24.963 --> 00:48:25.833
You know,
00:48:25.843 --> 00:48:27.392
bringing up that
00:48:27.402 --> 00:48:28.553
kind of ending part that you were
00:48:28.563 --> 00:48:30.313
mentioning about about, you know, trying
00:48:30.323 --> 00:48:31.432
to re
00:48:31.442 --> 00:48:33.273
reverse engineer
00:48:33.283 --> 00:48:35.513
uh and the complexity of it. One of the
00:48:35.523 --> 00:48:37.553
things that I was writing down here
00:48:37.563 --> 00:48:41.392
uh was value curation, okay? Because
00:48:41.402 --> 00:48:43.872
when we talk about other tokens, usually
00:48:43.882 --> 00:48:45.473
what it ends up being is that you have,
00:48:45.483 --> 00:48:47.553
you know, some token, you assign a value
00:48:47.563 --> 00:48:49.273
to it, and then
00:48:49.283 --> 00:48:51.912
it's effectively done. That's it, right?
00:48:51.922 --> 00:48:55.513
There isn't a lot of um relationships.
00:48:55.523 --> 00:48:56.313
And we talked a little bit about
00:48:56.323 --> 00:48:57.672
relationships before in the timeline
00:48:57.682 --> 00:48:59.193
situation, but there isn't a lot of
00:48:59.203 --> 00:49:00.674
relationships that are happening. Maybe
00:49:00.684 --> 00:49:02.034
you have the background and foreground
00:49:02.044 --> 00:49:04.874
relationship for accessibility purposes.
00:49:04.884 --> 00:49:07.594
Uh maybe you have relationship with font
00:49:07.604 --> 00:49:09.074
and the font size and the font weight
00:49:09.084 --> 00:49:09.954
and all that kind of stuff for your
00:49:09.964 --> 00:49:11.453
headings. But
00:49:11.463 --> 00:49:11.994
>> [snorts]
00:49:12.004 --> 00:49:13.954
>> when it comes to motion,
00:49:13.964 --> 00:49:17.114
there's a lot more relationships going
00:49:17.124 --> 00:49:21.834
on, right? So, what does a curation
00:49:21.844 --> 00:49:25.674
exercise look like, right? When when you
00:49:25.684 --> 00:49:27.114
know, for again, going back to a color
00:49:27.124 --> 00:49:28.714
for a minute, when you are curating the
00:49:28.724 --> 00:49:30.114
foreground, you're also curating the
00:49:30.124 --> 00:49:32.074
background together, so that you know
00:49:32.084 --> 00:49:33.954
you have that contrast, right? When you
00:49:33.964 --> 00:49:35.674
are doing some textiles, you you have
00:49:35.684 --> 00:49:36.834
the font family you're probably going to
00:49:36.844 --> 00:49:38.034
use, you're going to curate the font
00:49:38.044 --> 00:49:39.674
size, line height to go and work
00:49:39.684 --> 00:49:42.874
together. It's only a few tokens. So,
00:49:42.884 --> 00:49:45.394
when it comes to the to these things,
00:49:45.404 --> 00:49:47.394
there's a lot more. So, tell me a little
00:49:47.404 --> 00:49:49.354
bit about the the exercise of curation
00:49:49.364 --> 00:49:50.234
there.
00:49:50.244 --> 00:49:53.954
>> Oh, that's a good That's a good one. Um
00:49:53.964 --> 00:49:54.994
Ooh.
00:49:55.004 --> 00:49:58.554
Uh I think that
00:49:58.564 --> 00:49:59.554
I don't know if I have a good answer for
00:49:59.564 --> 00:50:00.354
that. I'm going to have to think about
00:50:00.364 --> 00:50:02.194
this for a second, cuz I think the
00:50:02.204 --> 00:50:04.874
exercise of curating it
00:50:04.884 --> 00:50:08.754
comes down to
00:50:08.764 --> 00:50:11.154
the ultimate goal of the system and and
00:50:11.164 --> 00:50:12.434
the product or the project that you're
00:50:12.444 --> 00:50:13.714
working on. I think that's where those
00:50:13.724 --> 00:50:16.194
considerations come into play. And and
00:50:16.204 --> 00:50:17.754
what's interesting
00:50:17.764 --> 00:50:19.434
I I think this is still kind of help
00:50:19.444 --> 00:50:20.954
answer the question. This is how I This
00:50:20.964 --> 00:50:22.594
is at least how I think of it. I I think
00:50:22.604 --> 00:50:24.394
that there are
00:50:24.404 --> 00:50:27.194
that sort of functional piece of motion
00:50:27.204 --> 00:50:29.074
or um
00:50:29.084 --> 00:50:30.954
uh you know,
00:50:30.964 --> 00:50:34.354
I think that there are
00:50:34.364 --> 00:50:36.474
like that is something that I don't see
00:50:36.484 --> 00:50:40.794
changing as much as as something like
00:50:40.804 --> 00:50:43.194
the storytelling or or the feel of it.
00:50:43.204 --> 00:50:44.554
Like if you're if you're building
00:50:44.564 --> 00:50:45.914
something for like a luxury site where
00:50:45.924 --> 00:50:47.394
you want things to be more slow or
00:50:47.404 --> 00:50:49.554
gentle, I think that that's where more
00:50:49.564 --> 00:50:52.594
of the curation piece of like the feel
00:50:52.604 --> 00:50:55.234
comes together. And I And I have I the
00:50:55.244 --> 00:50:57.234
way that I think of it is that you know,
00:50:57.244 --> 00:50:59.154
a lot of things like the hovers, there
00:50:59.164 --> 00:51:00.714
might be a little bit of curation there,
00:51:00.724 --> 00:51:02.715
but I feel like you would always want to
00:51:02.725 --> 00:51:05.235
reach for something that maybe is
00:51:05.245 --> 00:51:07.195
speaking to something
00:51:07.205 --> 00:51:09.155
faster and and more responsive for those
00:51:09.165 --> 00:51:10.315
pieces.
00:51:10.325 --> 00:51:12.235
Um but what that process looks like,
00:51:12.245 --> 00:51:14.755
that's a great question. I think
00:51:14.765 --> 00:51:17.075
this could be a good uh
00:51:17.085 --> 00:51:19.075
segue into talking about like what Figma
00:51:19.085 --> 00:51:21.075
motion brings to the table. Like I think
00:51:21.085 --> 00:51:23.315
that playing playing around with Figma
00:51:23.325 --> 00:51:25.075
motion that that came out not that long
00:51:25.085 --> 00:51:27.075
ago could be a great way a great
00:51:27.085 --> 00:51:29.675
exercise of curating what you think you
00:51:29.685 --> 00:51:31.035
want those
00:51:31.045 --> 00:51:31.915
uh what do you think you want that
00:51:31.925 --> 00:51:33.235
motion feel to look like.
00:51:33.245 --> 00:51:35.795
>> So you're you're you're kind of kind of
00:51:35.805 --> 00:51:38.555
picturing that you kind of really need
00:51:38.565 --> 00:51:40.875
some sort of interface to help the
00:51:40.885 --> 00:51:44.075
curation exercise occur because there's
00:51:44.085 --> 00:51:46.915
so many moving pieces quite literally
00:51:46.925 --> 00:51:48.875
uh that are going into you trying to
00:51:48.885 --> 00:51:50.675
figure out how this motion is supposed
00:51:50.685 --> 00:51:52.195
to be captured
00:51:52.205 --> 00:51:54.635
uh from, you know, the the easing value,
00:51:54.645 --> 00:51:58.075
duration value, the the um
00:51:58.085 --> 00:52:00.915
elements involved, how long uh that that
00:52:00.925 --> 00:52:02.915
timeline is, and when when it happens on
00:52:02.925 --> 00:52:05.035
the if it for the orchestration there's
00:52:05.045 --> 00:52:07.355
so because again talking about the the
00:52:07.365 --> 00:52:09.555
relationship piece, there's so many
00:52:09.565 --> 00:52:13.555
parts to the choreography that making a
00:52:13.565 --> 00:52:15.915
change to any one of them
00:52:15.925 --> 00:52:19.835
may affect the larger orchestration
00:52:19.845 --> 00:52:22.675
that's that's occurring, right? And to
00:52:22.685 --> 00:52:25.035
do that like again from a color
00:52:25.045 --> 00:52:27.435
standpoint, going into a token value and
00:52:27.445 --> 00:52:29.755
changing the color usually very benign,
00:52:29.765 --> 00:52:30.955
right? And you're not it's not really
00:52:30.965 --> 00:52:32.195
going to do too much. Okay, maybe you
00:52:32.205 --> 00:52:34.075
get a little bit of accessibility ding,
00:52:34.085 --> 00:52:36.235
not a big deal. But
00:52:36.245 --> 00:52:40.155
for you to go into a JSON file, try to
00:52:40.165 --> 00:52:43.955
change a choreography token,
00:52:43.965 --> 00:52:46.035
sounds like you're you might be in a
00:52:46.045 --> 00:52:48.235
world of hurt without a UI that's
00:52:48.245 --> 00:52:50.835
describing exactly what's going on.
00:52:50.845 --> 00:52:54.195
>> Um sort of. I think that um yeah, that's
00:52:54.205 --> 00:52:56.635
a good question. So
00:52:56.645 --> 00:52:58.475
yeah, I I see
00:52:58.485 --> 00:52:59.075
um
00:52:59.085 --> 00:53:00.995
and maybe I I I get it. Ding, light
00:53:01.005 --> 00:53:02.915
bulb. Okay, bring that bring that light
00:53:02.925 --> 00:53:06.557
bulb back from my head from earlier. Um
00:53:06.567 --> 00:53:08.477
Yeah, well do think when you're at that
00:53:08.487 --> 00:53:09.997
level that that some sort of
00:53:10.007 --> 00:53:11.597
visualization
00:53:11.607 --> 00:53:13.557
to help with that motion process is it's
00:53:13.567 --> 00:53:16.357
helpful. Um it's still the choreography
00:53:16.367 --> 00:53:17.637
tokens like we mentioned, they still
00:53:17.647 --> 00:53:20.917
reach back through. And so, um should
00:53:20.927 --> 00:53:23.757
you change any of the, you know, uh
00:53:23.767 --> 00:53:25.197
design system
00:53:25.207 --> 00:53:26.477
tokens,
00:53:26.487 --> 00:53:27.877
you know, earlier up. Like let's say
00:53:27.887 --> 00:53:30.237
that you decide that your your quick
00:53:30.247 --> 00:53:32.717
motion goes from 100 milliseconds to 80
00:53:32.727 --> 00:53:34.597
milliseconds, you change that everything
00:53:34.607 --> 00:53:36.117
it does accordingly, right? The beauty
00:53:36.127 --> 00:53:37.677
of design systems.
00:53:37.687 --> 00:53:38.357
Um
00:53:38.367 --> 00:53:39.357
but
00:53:39.367 --> 00:53:42.397
when it comes to then like visualizing
00:53:42.407 --> 00:53:43.997
like how
00:53:44.007 --> 00:53:46.477
uh a modal might be moving or a drawer
00:53:46.487 --> 00:53:48.717
or something like a if you wanted to do
00:53:48.727 --> 00:53:52.077
that example of like the the the switch
00:53:52.087 --> 00:53:54.397
that goes back and forth. Yeah, so that
00:53:54.407 --> 00:53:56.317
process
00:53:56.327 --> 00:53:57.557
I mean, the way that I've approached it
00:53:57.567 --> 00:53:59.877
is either with some sort of timeline or
00:53:59.887 --> 00:54:02.437
or with artificial intelligence is how
00:54:02.447 --> 00:54:04.277
I've gone through the curation of it. I
00:54:04.287 --> 00:54:06.597
I think I know
00:54:06.607 --> 00:54:08.357
you know, I think I I take the approach
00:54:08.367 --> 00:54:09.797
for the most part where like if I'm
00:54:09.807 --> 00:54:13.517
working with something like a
00:54:13.527 --> 00:54:16.197
So, I did this again code first was my
00:54:16.207 --> 00:54:18.397
approach as a developer. And so, what I
00:54:18.407 --> 00:54:20.237
did was I built this system and then as
00:54:20.247 --> 00:54:21.117
I was
00:54:21.127 --> 00:54:24.477
whatever project I'm using it in, um
00:54:24.487 --> 00:54:27.077
things like accordions, you know, I will
00:54:27.087 --> 00:54:28.957
just I'm able to see it in the in the
00:54:28.967 --> 00:54:30.997
project because I I it's there. It
00:54:31.007 --> 00:54:32.877
exists on the page that I'm developing.
00:54:32.887 --> 00:54:34.357
And so, if I need like feel like I need
00:54:34.367 --> 00:54:36.637
to adjust it, then I could just go and
00:54:36.647 --> 00:54:37.957
say, you know, okay, let's actually
00:54:37.967 --> 00:54:39.757
let's bring this to
00:54:39.767 --> 00:54:41.397
uh a long entrance instead of a medium
00:54:41.407 --> 00:54:43.037
cuz I wanted to have a little bit of a
00:54:43.047 --> 00:54:44.477
of a different feel for this type of
00:54:44.487 --> 00:54:46.797
project. So, I guess I always have that
00:54:46.807 --> 00:54:49.477
type of visualization
with me. Um
00:54:49.487 --> 00:54:49.757
>> Well,
00:54:49.767 --> 00:54:50.277
>> And then
00:54:50.287 --> 00:54:51.237
>> I think it makes sense because you're
00:54:51.247 --> 00:54:52.597
talking about the component tokens,
00:54:52.607 --> 00:54:53.637
right? Like I mean, the these are
00:54:53.647 --> 00:54:54.957
effectively component tokens and
00:54:54.967 --> 00:54:57.037
therefore affecting components directly.
00:54:57.047 --> 00:54:59.797
And in which case then you have uh you
00:54:59.807 --> 00:55:01.157
know, significant control on that
00:55:01.167 --> 00:55:03.037
component. Cuz again, the the
00:55:03.047 --> 00:55:05.917
visualization part really is just you in
00:55:05.927 --> 00:55:07.797
a sandbox, storybook, whatever you want
00:55:07.807 --> 00:55:09.518
to call it, that says, [snorts] "Okay,
00:55:09.528 --> 00:55:10.438
we're going to be able to tweak it
00:55:10.448 --> 00:55:11.638
because I'm sitting at this component
00:55:11.648 --> 00:55:12.998
right now, right?"
00:55:13.008 --> 00:55:15.078
>> Yeah. Yeah, and I think that that from
00:55:15.088 --> 00:55:16.678
So,
00:55:16.688 --> 00:55:19.558
where um this is one of my my thoughts
00:55:19.568 --> 00:55:20.718
is that, you know, from a design
00:55:20.728 --> 00:55:22.718
perspective, maybe that's where Figma
00:55:22.728 --> 00:55:24.758
motion could be a nice tool to fit in.
00:55:24.768 --> 00:55:26.678
Um I'm also a big fan of things like
00:55:26.688 --> 00:55:30.038
Rive, uh but those are different. Um I I
00:55:30.048 --> 00:55:32.118
still use I use Rive a lot. I think that
00:55:32.128 --> 00:55:33.398
they're across the line where you would
00:55:33.408 --> 00:55:35.518
put design where you put motion into a
00:55:35.528 --> 00:55:37.918
system for components that we use it,
00:55:37.928 --> 00:55:40.558
but I still think that um
00:55:40.568 --> 00:55:42.118
something like an
00:55:42.128 --> 00:55:45.078
uh a custom I love doing I love taking
00:55:45.088 --> 00:55:47.798
uh people's logos and making like a
00:55:47.808 --> 00:55:49.438
custom loader out of that. Like if they
00:55:49.448 --> 00:55:50.998
have like a word mark or symbol, turning
00:55:51.008 --> 00:55:52.598
it into a logo, that's something that I
00:55:52.608 --> 00:55:54.278
still think is best fit in something
00:55:54.288 --> 00:55:56.358
like Rive, personally. Like I think
00:55:56.368 --> 00:55:57.558
taking it into Rive, work on the
00:55:57.568 --> 00:55:59.718
timeline, and then just make that that
00:55:59.728 --> 00:56:01.878
loader its own little Rive canvas
00:56:01.888 --> 00:56:04.278
element. Um I still think that some
00:56:04.288 --> 00:56:06.438
things like that um have benefit to go
00:56:06.448 --> 00:56:08.838
to other software. Um
00:56:08.848 --> 00:56:09.398
but yeah.
00:56:09.408 --> 00:56:11.398
>> Yeah, that makes sense to me. Um we're
00:56:11.408 --> 00:56:12.638
coming close to the end of time over
00:56:12.648 --> 00:56:15.518
here, um but I I I just thought of one
00:56:15.528 --> 00:56:17.958
more question, um maybe it might be a
00:56:17.968 --> 00:56:20.878
little uh hopefully it's short, but
00:56:20.888 --> 00:56:22.718
prior art,
00:56:22.728 --> 00:56:25.398
is there any not not necessarily in
00:56:25.408 --> 00:56:27.318
design token land, because again mo-
00:56:27.328 --> 00:56:30.078
motion is fairly scarce when it comes to
00:56:30.088 --> 00:56:31.278
design tokens, for at least from my
00:56:31.288 --> 00:56:33.198
perspective, my history of looking at
00:56:33.208 --> 00:56:35.118
the stuff, but prior art when it comes
00:56:35.128 --> 00:56:37.518
to describing
00:56:37.528 --> 00:56:40.718
animation, motion, things like that,
00:56:40.728 --> 00:56:43.798
have you seen anything out there like
00:56:43.808 --> 00:56:45.198
that that are again are outside of
00:56:45.208 --> 00:56:46.958
design tokens that might be helping
00:56:46.968 --> 00:56:49.318
inform how you describe these things on
00:56:49.328 --> 00:56:51.158
your side?
00:56:51.168 --> 00:56:52.798
>> Yeah, like how you approach motion?
00:56:52.808 --> 00:56:55.638
>> Yeah, yeah, how you naming and and and
00:56:55.648 --> 00:56:56.998
things like that. Anything that's that
00:56:57.008 --> 00:56:58.678
you've seen out there so far?
00:56:58.688 --> 00:57:00.878
>> Well, naming is a good one. I'm not a
00:57:00.888 --> 00:57:02.718
whole lot in naming. I feel like that
00:57:02.728 --> 00:57:04.518
always ends up coming
00:57:04.528 --> 00:57:06.518
Yeah, people will have their
00:57:06.528 --> 00:57:08.838
their naming conventions and
00:57:08.848 --> 00:57:10.359
personally as a developer, I think that
00:57:10.369 --> 00:57:11.799
that's fine. Whatever works best for
00:57:11.809 --> 00:57:14.119
them, you know, naming is fine. Um you
00:57:14.129 --> 00:57:16.199
know, motion animation principles, I
00:57:16.209 --> 00:57:18.719
think there is um
00:57:18.729 --> 00:57:21.159
the 12 principles of UX motion.
00:57:21.169 --> 00:57:21.599
>> Mhm.
00:57:21.609 --> 00:57:23.759
>> Um there's an article that's out there
00:57:23.769 --> 00:57:26.239
and I'm I'm going to
00:57:26.249 --> 00:57:27.719
catch flak cuz I don't remember his name
00:57:27.729 --> 00:57:28.479
off the top of my head.
00:57:28.489 --> 00:57:29.679
>> I don't remember the name either. No,
00:57:29.689 --> 00:57:30.999
you got it. You're okay. We're all We're
00:57:31.009 --> 00:57:32.534
all bad here. Sorry, folks.
00:57:32.544 --> 00:57:32.919
>> [laughter]
00:57:32.929 --> 00:57:34.159
>> But yeah, that's like you know, that's a
00:57:34.169 --> 00:57:36.839
good That's a good one um to to think
00:57:36.849 --> 00:57:38.439
about um
00:57:38.449 --> 00:57:39.999
So, I think you know, there are some
00:57:40.009 --> 00:57:42.279
resources, but actually I agree with you
00:57:42.289 --> 00:57:43.679
that
00:57:43.689 --> 00:57:45.399
part of the interesting journey of of
00:57:45.409 --> 00:57:48.159
exploring motion as I've been
trying to
00:57:48.169 --> 00:57:49.759
get ideas or trying to think through
00:57:49.769 --> 00:57:52.039
things is I have been looking around at
00:57:52.049 --> 00:57:53.679
articles and research and and you you
00:57:53.689 --> 00:57:55.399
know, there really isn't a whole lot.
00:57:55.409 --> 00:57:55.759
>> Right.
00:57:55.769 --> 00:57:57.839
>> There isn't a whole lot that speaks to
00:57:57.849 --> 00:57:59.759
specifically the things that we're
00:57:59.769 --> 00:58:02.279
trying to to look into. So, maybe that's
00:58:02.289 --> 00:58:03.239
a good thing, maybe that's a bad thing.
00:58:03.249 --> 00:58:04.639
Maybe we're on to something, maybe not.
00:58:04.649 --> 00:58:05.879
I don't know, but
00:58:05.889 --> 00:58:06.679
>> Maybe.
00:58:06.689 --> 00:58:08.839
>> what I do think is really interesting,
00:58:08.849 --> 00:58:09.999
the last thing I'll talk on. I don't
00:58:10.009 --> 00:58:11.399
really have anything to plug, so maybe
00:58:11.409 --> 00:58:12.519
we'll take the last minute to talk about
00:58:12.529 --> 00:58:12.839
this
00:58:12.849 --> 00:58:13.159
>> Sure.
00:58:13.169 --> 00:58:16.439
>> is working with AI motion. Working with
00:58:16.449 --> 00:58:18.719
AI and motion is is really interesting
00:58:18.729 --> 00:58:21.359
because it become this tool that we can
00:58:21.369 --> 00:58:23.119
that we can leverage, but it can't
00:58:23.129 --> 00:58:24.919
visualize like we can.
00:58:24.929 --> 00:58:25.279
>> Right.
00:58:25.289 --> 00:58:27.679
>> And so, you know, if I told you to close
00:58:27.689 --> 00:58:29.679
your eyes and imagine a
00:58:29.689 --> 00:58:31.559
you know, drop of water falling into a
00:58:31.569 --> 00:58:33.199
glass or something,
00:58:33.209 --> 00:58:34.839
you know, what's interesting is that you
00:58:34.849 --> 00:58:36.199
and I might not even think of the same
00:58:36.209 --> 00:58:37.839
things just even there. Like that's
00:58:37.849 --> 00:58:41.119
again why it's so hard to
00:58:41.129 --> 00:58:42.879
discuss motion and maybe why it's part
00:58:42.889 --> 00:58:44.999
of the reason why it's it's it's
00:58:45.009 --> 00:58:46.679
been put on the back burner because even
00:58:46.689 --> 00:58:48.239
we as human beings might not think of
00:58:48.249 --> 00:58:49.999
the same thing, but AI it can't
00:58:50.009 --> 00:58:51.639
visualize. It's just predicting, right?
00:58:51.649 --> 00:58:53.999
It just goes off of data. And so, that
00:58:54.009 --> 00:58:56.359
is where I think that in this motion
00:58:56.369 --> 00:58:58.359
system that I built and in the approach
00:58:58.369 --> 00:59:00.719
that you pick for motion all the way
00:59:00.729 --> 00:59:03.079
from the token naming and all
00:59:03.089 --> 00:59:05.199
It's just you need to establish that
00:59:05.209 --> 00:59:07.079
data because that's what's going to make
00:59:07.089 --> 00:59:09.919
it work best. As you As we continue to
00:59:09.929 --> 00:59:11.999
get further into this, you know, agentic
00:59:12.009 --> 00:59:14.201
workflows And it it
00:59:14.211 --> 00:59:16.201
continues to become a part of our, you
00:59:16.211 --> 00:59:18.001
know, our processes. It's going to be
00:59:18.011 --> 00:59:20.081
How do you work with it? You you give it
00:59:20.091 --> 00:59:22.401
the data because if you tell it uh I
00:59:22.411 --> 00:59:25.921
want you to create some motion that uh
00:59:25.931 --> 00:59:28.361
you know, feels snappy. Well, what does
00:59:28.371 --> 00:59:29.841
snappy mean, you know?
00:59:29.851 --> 00:59:31.321
>> And then it gives it back and it'll give
00:59:31.331 --> 00:59:33.161
you results and then, you know, it's
00:59:33.171 --> 00:59:35.081
it's it's it's common to want to try to
00:59:35.091 --> 00:59:37.481
describe motion through vocabulary and
00:59:37.491 --> 00:59:39.201
try to describe the feeling. So, you
00:59:39.211 --> 00:59:41.001
might use words like I want this to feel
00:59:41.011 --> 00:59:43.921
snappy. I want it to feel uh oh oh oh,
00:59:43.931 --> 00:59:45.681
what you did right there feels clunky,
00:59:45.691 --> 00:59:47.681
you know? Like, well, what does clunky
00:59:47.691 --> 00:59:48.241
mean?
00:59:48.251 --> 00:59:48.481
>> Yeah.
00:59:48.491 --> 00:59:50.921
>> And and maybe it gets it right, maybe it
00:59:50.931 --> 00:59:52.361
doesn't. Maybe if you're on a higher
00:59:52.371 --> 00:59:55.161
model like Opus, maybe it has a better
00:59:55.171 --> 00:59:56.641
interpretation of that. And if you're on
00:59:56.651 --> 00:59:58.761
something like Sonnet, maybe not. But,
00:59:58.771 --> 01:00:00.881
you can kind of help
01:00:00.891 --> 01:00:03.521
yourself overall by establishing the
01:00:03.531 --> 01:00:05.401
intent in the in the vocabulary because
01:00:05.411 --> 01:00:07.281
what you're doing through the process of
01:00:07.291 --> 01:00:09.041
this entire
01:00:09.051 --> 01:00:10.481
motion design system that we're trying
01:00:10.491 --> 01:00:11.801
to achieve is that you're giving these
01:00:11.811 --> 01:00:14.121
named intent throughout. So, instead of
01:00:14.131 --> 01:00:16.241
saying I want you to give me something
01:00:16.251 --> 01:00:18.121
that feels snappy, you say I want a
01:00:18.131 --> 01:00:20.441
short entrance. I want a medium exit. I
01:00:20.451 --> 01:00:22.921
want I want this. And and you can kind
01:00:22.931 --> 01:00:26.041
of it it has a way to anchor back into
01:00:26.051 --> 01:00:28.001
what those mean. You're giving it those
01:00:28.011 --> 01:00:30.121
data values. And so then, your results
01:00:30.131 --> 01:00:32.161
are going to become greater.
01:00:32.171 --> 01:00:32.561
Um
01:00:32.571 --> 01:00:32.921
>> Mhm.
01:00:32.931 --> 01:00:34.001
>> And the other thing that it's going to
01:00:34.011 --> 01:00:36.641
do that this is my just my now this is
01:00:36.651 --> 01:00:38.121
my ramble from working with AI with
01:00:38.131 --> 01:00:40.321
motion, but the other thing that AI
01:00:40.331 --> 01:00:43.921
sucks at with motion is is is delay. Is
01:00:43.931 --> 01:00:46.161
pausing. Is taking a beat. It doesn't It
01:00:46.171 --> 01:00:48.121
doesn't know. It's so often when you try
01:00:48.131 --> 01:00:50.121
to get it to create motion, it's going
01:00:50.131 --> 01:00:52.161
to It'll make motions back to back to
01:00:52.171 --> 01:00:53.361
back to back to back back and never
01:00:53.371 --> 01:00:55.641
stop. And so you really need to be able
01:00:55.651 --> 01:00:57.201
to say
01:00:57.211 --> 01:00:59.721
do this, then pause, then do this, then
01:00:59.731 --> 01:01:01.761
pause. And so, you know, yeah, I think
01:01:01.771 --> 01:01:03.921
that there's a a lot of fun to explore
01:01:03.931 --> 01:01:05.201
there, too, but
01:01:05.211 --> 01:01:06.961
um thank you so much for having me on
01:01:06.971 --> 01:01:08.361
the show. Thank you so much for chatting
01:01:08.371 --> 01:01:10.041
with me. This is such a fun topic and I
01:01:10.051 --> 01:01:12.081
hope I can talk about it more sometime,
01:01:12.091 --> 01:01:12.401
too.
01:01:12.411 --> 01:01:14.401
>> Yeah, absolutely. And before you think
01:01:14.411 --> 01:01:15.762
that that you have nothing to plug,
01:01:15.772 --> 01:01:18.362
don't you have a motion site that people
01:01:18.372 --> 01:01:20.282
need to check out and stuff? I think
01:01:20.292 --> 01:01:21.442
that's a plug.
01:01:21.452 --> 01:01:23.482
>> If you yeah, if you want to take a look
01:01:23.492 --> 01:01:24.882
at the work motion work that I've done
01:01:24.892 --> 01:01:26.802
and just the exploration so far, I I
01:01:26.812 --> 01:01:27.842
started
01:01:27.852 --> 01:01:29.802
motiondesignsystem.org.
01:01:29.812 --> 01:01:31.922
So that's just it has an example of the
01:01:31.932 --> 01:01:33.362
motion design system that I use. It's
01:01:33.372 --> 01:01:35.202
not the full system. It's just what I
01:01:35.212 --> 01:01:37.362
think is the most important parts.
01:01:37.372 --> 01:01:38.482
Um but yeah, you can actually you can
01:01:38.492 --> 01:01:40.162
contact me through that website if you
01:01:40.172 --> 01:01:41.602
ever want to talk about it. Like if
01:01:41.612 --> 01:01:43.202
anyone's interested, uh find me on
01:01:43.212 --> 01:01:45.002
LinkedIn. Or again, I work at South
01:01:45.012 --> 01:01:46.762
Left. So feel free to reach out to the
01:01:46.772 --> 01:01:48.122
wonderful people at South Left if you
01:01:48.132 --> 01:01:49.602
ever want to work on motion. Man, you
01:01:49.612 --> 01:01:51.562
can get at me through there, too. So.
01:01:51.572 --> 01:01:53.562
>> Sounds good. Well, Ryan, thank you so
01:01:53.572 --> 01:01:54.762
much for being on the show. What a great
01:01:54.772 --> 01:01:57.802
conversation. I'm inspired absolutely uh
01:01:57.812 --> 01:01:59.562
in potentially diving back into motion
01:01:59.572 --> 01:02:00.882
and seeing I can solve some problems
01:02:00.892 --> 01:02:02.722
with you over there. So thank you for
01:02:02.732 --> 01:02:05.002
being on the show and uh and nerding out
01:02:05.012 --> 01:02:05.962
with me.
01:02:05.972 --> 01:02:07.562
>> Absolutely. I I'm excited to see what
01:02:07.572 --> 01:02:09.562
you do with it and it'll be great.
01:02:09.572 --> 01:02:12.442
>> We'll see. Yeah. And thank you for
01:02:12.452 --> 01:02:14.202
watching. But before you go, please help
01:02:14.212 --> 01:02:16.322
out the show by smashing that like and
01:02:16.332 --> 01:02:17.562
subscribe button just to get notified
01:02:17.572 --> 01:02:19.722
next time that we go live. And feel free
01:02:19.732 --> 01:02:21.402
to continue the conversation on the
01:02:21.412 --> 01:02:23.882
official Design Systems House Discord by
01:02:23.892 --> 01:02:25.882
going to discord.ds.house. There's in
01:02:25.892 --> 01:02:27.482
the bottom right there. Play nice in
01:02:27.492 --> 01:02:29.042
those comments and I'll see you on the
01:02:29.052 --> 01:02:31.873
internet. Bye.
01:02:31.883 --> 01:02:39.078
>> [music]
01:02:39.088 --> 01:02:44.973
[music]
01:03:04.633 --> 01:03:06.653