[00:00] (0.16s)
It's sloth. Yeah. Hello. Do you know
[00:02] (2.24s)
what this thing's called? Yeah. This
[00:04] (4.16s)
section right here. Take a guess. I know
[00:06] (6.40s)
you'll get it wrong because it has the
[00:08] (8.16s)
goofiest name ever. Hero section. It's
[00:10] (10.40s)
called a hero section. I know. I know.
[00:12] (12.64s)
Kind of dumb. It's actually one of the
[00:14] (14.16s)
most important sections on any website.
[00:16] (16.08s)
The reason it's called a hero section is
[00:17] (17.92s)
because just like a hero in a story or
[00:19] (19.76s)
movie, it plays the most critical role
[00:21] (21.44s)
in capturing visitors attention and
[00:23] (23.28s)
drawing them into the content below.
[00:24] (24.80s)
Yeah, that makes sense. Hi guys, I stole
[00:26] (26.64s)
this definition from this blog post for
[00:28] (28.48s)
magic UI because I had no idea why it
[00:30] (30.80s)
was called a hero section either. Now, a
[00:32] (32.40s)
hero section is usually this big area at
[00:34] (34.80s)
the top that contains your main
[00:36] (36.08s)
headline, some supporting text, and
[00:37] (37.76s)
usually a call to action button or a
[00:39] (39.52s)
CTA. Your hero section is supposed to
[00:41] (41.36s)
grab attention and communicate what your
[00:43] (43.12s)
website does in about 3 seconds because
[00:44] (44.96s)
that's how long you have before users
[00:46] (46.64s)
leave. You'll see this section
[00:48] (48.08s)
everywhere. They can have background
[00:49] (49.52s)
images, videos, animations, whatever.
[00:51] (51.60s)
But the job is always the same. hook the
[00:54] (54.00s)
user immediately. The tricky part is
[00:56] (56.40s)
making them work on mobile. So yeah,
[00:57] (57.92s)
hero section, terrible name, important
[00:59] (59.52s)
component, and that's exactly what this
[01:01] (61.36s)
video is about. UI components that are
[01:03] (63.28s)
pretty important. You see them
[01:04] (64.48s)
everywhere, but you probably don't know
[01:06] (66.08s)
the actual names for. I'm going to go
[01:07] (67.52s)
through the essential ones every
[01:08] (68.64s)
programmer should know because honestly,
[01:10] (70.56s)
half of building a good UI is just
[01:12] (72.32s)
knowing what these things are called so
[01:13] (73.76s)
you can Google them properly and of
[01:15] (75.44s)
course copy and steal. I mean, take
[01:17] (77.04s)
inspiration from. Plus, when you're
[01:18] (78.40s)
working with designers or other
[01:19] (79.76s)
developers or I guess nowadays AI,
[01:22] (82.32s)
you're going to need this vocabulary.
[01:23] (83.68s)
You can't just say that spinny thing or
[01:25] (85.60s)
those little dots at the bottom, you
[01:27] (87.04s)
need to know the actual names. And when
[01:28] (88.56s)
I say UI components, it could be
[01:30] (90.32s)
something like a specific HTML element
[01:32] (92.40s)
like a button, an entire section of a
[01:34] (94.24s)
website like the hero section, or just
[01:36] (96.16s)
general components that you see all the
[01:37] (97.60s)
time, but you didn't know had an actual
[01:39] (99.04s)
name. Either way, it's good to know the
[01:40] (100.56s)
names of these components and what they
[01:41] (101.92s)
do. So, let's move on. We'll start with
[01:43] (103.52s)
something simple to warm you up. Let's
[01:45] (105.12s)
go with the navigation bar. You see this
[01:46] (106.96s)
horizontal menu? Oh, by the way, these
[01:48] (108.40s)
components aren't ordered in any
[01:49] (109.92s)
specific way. I'm just going to be
[01:51] (111.20s)
listing them randomly. Yeah, you see
[01:52] (112.72s)
this hor Oh, and if you already know
[01:54] (114.00s)
these UI components, cool. Good for you.
[01:56] (116.16s)
I don't appreciate your existence. So,
[01:58] (118.00s)
you see this horizontal menu at the top?
[01:59] (119.68s)
That's your navigation bar. Or if you
[02:01] (121.12s)
want to sound like a real programmer,
[02:02] (122.96s)
you can call it a navbar. The navbar is
[02:05] (125.20s)
basically your website's table of
[02:06] (126.56s)
contents. It shows the main sections
[02:08] (128.16s)
users can visit, and it usually sits at
[02:10] (130.24s)
the very top, so users always know how
[02:12] (132.08s)
to get around. I mean, I guess
[02:13] (133.36s)
technically you could have it anywhere,
[02:14] (134.96s)
but that might as well be a programming
[02:16] (136.48s)
war crime, so don't do that. But on
[02:18] (138.24s)
mobile devices, it usually collapses
[02:20] (140.16s)
into a hamburger menu. Hamburger. Now,
[02:22] (142.48s)
the hamburger menu is its own UI
[02:24] (144.40s)
component, but it's still a part of the
[02:26] (146.24s)
navbar. It's just packaged differently
[02:27] (147.92s)
for smaller screens. The name is pretty
[02:29] (149.68s)
straightforward. You know, it's called a
[02:30] (150.96s)
navigation bar because it's literally a
[02:32] (152.88s)
bar that helps you navigate. It's a very
[02:34] (154.56s)
simple name. I wish other components
[02:36] (156.16s)
followed that rule. Hey, where are you
[02:37] (157.84s)
going? Do commercial break. Yay. Hey,
[02:43] (163.12s)
hello. I I have this newsletter called
[02:45] (165.68s)
Sol Bites. I I share pretty important I
[02:48] (168.48s)
share some pretty useful programming
[02:50] (170.48s)
information every week to make you a
[02:52] (172.16s)
better programmer. All you have to do is
[02:54] (174.72s)
give me your email. It's free. Yeah, you
[02:57] (177.44s)
should check it out. Now, it's one thing
[02:59] (179.20s)
knowing about these UI components, but
[03:00] (180.96s)
do you know how to make them look good
[03:02] (182.24s)
and not ugly? Probably not, because
[03:04] (184.00s)
you're a programmer. Well, with today's
[03:05] (185.52s)
sponsor, Mobin, you'll finally be able
[03:07] (187.12s)
to create projects that don't hurt
[03:08] (188.72s)
people's eyeballs. Mobin is a platform
[03:10] (190.32s)
that lets you look at popular websites
[03:12] (192.00s)
and mobile apps to help you find
[03:13] (193.28s)
inspiration for your own projects and
[03:14] (194.96s)
make them look good. It has thousands of
[03:16] (196.56s)
examples and it gets updated every
[03:18] (198.08s)
single week. No useless information.
[03:19] (199.84s)
It's quick and easy to use and you'll
[03:21] (201.20s)
always be up to date on UI trends and
[03:22] (202.80s)
best practices. It's used by over 1
[03:24] (204.40s)
million designers and product folks from
[03:26] (206.16s)
companies like Wise, Airbnb, Uber,
[03:28] (208.48s)
Headspace, Meta, Pinterest, and more.
[03:30] (210.56s)
So, you already know Mobin is high
[03:32] (212.00s)
quality. I mean, look how easy it is to
[03:33] (213.44s)
use. We just talked about nav bars,
[03:34] (214.96s)
right? Well, with Mobin, I can do this.
[03:36] (216.88s)
search, navbar, top navigation bar, and
[03:39] (219.76s)
boom, we can see how other companies
[03:41] (221.60s)
designed their navbars for both mobile
[03:43] (223.44s)
apps and websites. And not only can we
[03:45] (225.52s)
see their UI components, but we can also
[03:47] (227.28s)
see specific pages and specific flows,
[03:49] (229.60s)
like when a user creates a new account.
[03:51] (231.12s)
Mobin records the entire process, which
[03:53] (233.20s)
lets you copy, I mean, take inspiration
[03:55] (235.12s)
for your own projects. So, if you'd like
[03:56] (236.64s)
to try Mobin for free and start making
[03:58] (238.64s)
beautiful projects, click the link in
[04:00] (240.08s)
the description to get started.
[04:02] (242.40s)
Commercial breakover. Yay! Breadcrumbs.
[04:05] (245.20s)
All right. You see these little trail of
[04:06] (246.56s)
links here? These are called
[04:07] (247.84s)
breadcrumbs. I'm not lying. I'm not
[04:09] (249.68s)
pulling your willie or anything. Wait,
[04:11] (251.44s)
this one also has a goofy name, but it's
[04:13] (253.36s)
also very important. I swear.
[04:14] (254.80s)
Apparently, the reason why it's called a
[04:16] (256.08s)
breadcrumb is because it's borrowed from
[04:17] (257.92s)
the story of Hansel and Gretle, where
[04:19] (259.52s)
the kids drop a trail of breadcrumbs to
[04:21] (261.20s)
trace their way back home, which is
[04:22] (262.72s)
exactly what this component does. I
[04:24] (264.32s)
stole this from this blog post from VWO
[04:26] (266.72s)
because I had no idea why it was called
[04:28] (268.40s)
a breadcrumb. Breadcrumbs show you
[04:30] (270.08s)
exactly where you are in a website's
[04:31] (271.60s)
hierarchy and how you got there. So if
[04:33] (273.28s)
you're deep in some online store looking
[04:35] (275.12s)
at a specific product, you can see the
[04:36] (276.72s)
path that you've taken. This component
[04:38] (278.24s)
is used everywhere. Google Drive has it.
[04:40] (280.32s)
Your file path uses breadcrumbs.
[04:42] (282.08s)
Shopping websites, mobile apps. If
[04:44] (284.00s)
something has a path, it'll probably
[04:45] (285.44s)
have a breadcrumb. The cool thing, and
[04:47] (287.12s)
the most important thing about this is
[04:48] (288.80s)
each level is clickable, so you can jump
[04:50] (290.72s)
back to any previous level without
[04:52] (292.72s)
hitting the back button a million times.
[04:54] (294.64s)
It's super helpful for navigation. And
[04:56] (296.48s)
on mobile apps, they usually get
[04:58] (298.08s)
condensed or turned into a simple back
[05:00] (300.00s)
arrow because there's not enough space
[05:01] (301.68s)
for the full trail. And most users don't
[05:04] (304.08s)
consciously notice breadcrumbs. I mean,
[05:05] (305.84s)
they'll see them, but I doubt you know
[05:07] (307.28s)
the name for it. If they're missing from
[05:08] (308.72s)
a website, people get lost really fast
[05:10] (310.72s)
or they get annoyed. It's one of those
[05:12] (312.32s)
things that really make navigation feel
[05:14] (314.08s)
more intuitive, so don't forget them.
[05:15] (315.68s)
Testimonial section. You've definitely
[05:17] (317.36s)
seen this section. You know, the ones
[05:18] (318.72s)
that show off the good reviews for a
[05:20] (320.08s)
product. This is called a testimonial
[05:21] (321.76s)
section. It's pretty self-explanatory.
[05:23] (323.52s)
It's a section where you show off what
[05:25] (325.12s)
people are saying about your product.
[05:26] (326.16s)
Now, testimonials usually include the
[05:28] (328.48s)
customer's quote, their photo name,
[05:30] (330.72s)
maybe their job title or company, maybe
[05:32] (332.40s)
their social security and credit card
[05:33] (333.92s)
information, and sometimes you'll see
[05:35] (335.12s)
them in a carousel, maybe a marquee, or
[05:37] (337.36s)
just individual cards. Now, if you plan
[05:39] (339.12s)
on creating a SAS or business, this
[05:41] (341.04s)
section is definitely important. The key
[05:42] (342.72s)
to this section is to make them feel
[05:44] (344.24s)
authentic. Real photos, specific
[05:46] (346.24s)
details, maybe even linking to a full
[05:48] (348.32s)
review. You know, it's a good idea to
[05:49] (349.92s)
not use generic stock photos or vague
[05:52] (352.08s)
reviews like great product. Reviews like
[05:54] (354.08s)
that don't convince anyone. Bento grids.
[05:56] (356.00s)
This component has gotten very popular
[05:57] (357.84s)
because it usually looks better than
[05:59] (359.28s)
just a bunch of rectangles that are the
[06:00] (360.88s)
same size and shape. And as you can tell
[06:02] (362.40s)
by the name, it's inspired by a Japanese
[06:04] (364.16s)
bento box. Bento grids mix different
[06:06] (366.32s)
size sections. Some are tall and narrow.
[06:08] (368.16s)
Some are built like you. Wide and short,
[06:09] (369.92s)
some are square. You'll see bento grids
[06:11] (371.84s)
used for feature showcases, maybe for a
[06:14] (374.24s)
portfolio, maybe some dashboard
[06:16] (376.08s)
summaries. You basically use it when you
[06:18] (378.00s)
want to display different types of
[06:19] (379.20s)
content, but you want to make it look
[06:20] (380.48s)
good. I think this component is great. I
[06:22] (382.56s)
really like how they look. And uh as a
[06:24] (384.24s)
bonus, you can check out bento grids.com
[06:26] (386.24s)
and it gives you a bunch of examples on
[06:27] (387.60s)
bento grids. Oh, they look so good.
[06:29] (389.92s)
Skeleton screens. Okay, this is one of
[06:31] (391.60s)
the most clever loading techniques
[06:33] (393.12s)
you've never heard of, but you've
[06:34] (394.56s)
definitely seen. So instead of just
[06:36] (396.56s)
showing a spinning wheel or a loading
[06:38] (398.72s)
bar, skeleton screens show you the
[06:40] (400.72s)
approximate shape and layout of the
[06:42] (402.48s)
content that's loading. So usually
[06:44] (404.32s)
you're going to see these gray blocks
[06:45] (405.76s)
where the text will be, maybe empty
[06:47] (407.68s)
rectangles where images will load. And
[06:49] (409.36s)
what's interesting is that your brain
[06:51] (411.12s)
thinks it's way faster than staring at a
[06:53] (413.28s)
blank screen or a spinner, even though
[06:54] (414.88s)
the actual loading time is exactly the
[06:56] (416.80s)
same. You've definitely seen these
[06:58] (418.48s)
because pretty much every modern app
[07:00] (420.32s)
uses this. Here, let me show you. If you
[07:01] (421.84s)
go on your YouTube homepage and refresh
[07:03] (423.60s)
the page, it's going to show you a
[07:04] (424.96s)
skeleton screen. It's nice. Pagionation.
[07:06] (426.96s)
You see these rows of numbers at the
[07:08] (428.32s)
bottom? This is called pageionation.
[07:09] (429.84s)
Now, pageionation breaks up large
[07:11] (431.52s)
amounts of content into digestible
[07:13] (433.28s)
chunks. So instead of loading 10,000
[07:15] (435.28s)
search results on one page, crashing
[07:17] (437.04s)
your browser in your computer, you'll
[07:18] (438.48s)
get maybe 20 results per page with the
[07:20] (440.64s)
controls to navigate through them. And
[07:22] (442.00s)
there's a lot of different styles for
[07:23] (443.04s)
these. Sometimes it's just a previous
[07:24] (444.88s)
and next button. Sometimes it'll have a
[07:26] (446.96s)
list of numbers. Sometimes it's that
[07:28] (448.48s)
load more button. And sometimes it's not
[07:30] (450.40s)
even there because of this thing called
[07:31] (451.84s)
infinite scrolling, but they're all
[07:33] (453.28s)
solving the same problem. But more
[07:34] (454.72s)
modern apps seem to go for the infinite
[07:36] (456.16s)
scroll approach. Every site with lots of
[07:37] (457.92s)
content needs pageionation. But most
[07:39] (459.84s)
developers don't think about it until
[07:41] (461.28s)
they have like 500 products and the page
[07:43] (463.36s)
takes 30 seconds to load. So if your
[07:45] (465.12s)
project has a lot of content, make sure
[07:46] (466.56s)
to add pageionation. Accordians, yeah,
[07:48] (468.32s)
it's inspired by the musical instrument
[07:49] (469.84s)
because it expands and contracts. An
[07:51] (471.60s)
accordion lets you hide content behind
[07:53] (473.36s)
clickable headers, so users can click on
[07:55] (475.20s)
it and it'll expand to the content
[07:56] (476.80s)
inside. Accordians are used anytime you
[07:58] (478.88s)
have a lot of information that would
[08:00] (480.08s)
overwhelm users if shown all at once.
[08:02] (482.24s)
And honestly, it's one of the few
[08:03] (483.44s)
components that has a good name. Calling
[08:05] (485.04s)
it an accordion is way better than
[08:06] (486.48s)
calling it that clicky expand thingy
[08:08] (488.08s)
when you're talking to designers. So,
[08:09] (489.60s)
make sure you have those in. Toast. You
[08:11] (491.12s)
see this little pop-up message? This is
[08:12] (492.80s)
called a toast notification. I have no
[08:14] (494.96s)
idea why they decided to name it after a
[08:16] (496.88s)
British delicacy. I don't understand
[08:18] (498.16s)
these names. Just go with it. A toast is
[08:20] (500.16s)
a temporary message that pops up to give
[08:22] (502.16s)
you quick feedback about something that
[08:23] (503.76s)
just happened. Form submitted
[08:25] (505.04s)
successfully. Toast. An error happened.
[08:27] (507.04s)
Toast. There's a lot of different ways
[08:28] (508.40s)
you can create a toast. Usually, you
[08:30] (510.08s)
define the states based on color. So,
[08:31] (511.84s)
green for success, red for errors,
[08:33] (513.76s)
yellow for warnings. The important thing
[08:35] (515.20s)
is that they should appear briefly and
[08:36] (516.64s)
then disappear automatically so they
[08:38] (518.48s)
don't interrupt what you're doing. As
[08:39] (519.92s)
for the position of these toast, the
[08:41] (521.44s)
most popular is probably the top right,
[08:43] (523.28s)
but it's really up to preference. You'll
[08:45] (525.28s)
see them bottom left, the center, it all
[08:47] (527.44s)
depends on the app. And there's also a
[08:48] (528.72s)
variation of toast where they stack if
[08:50] (530.40s)
you get multiple messages. Now that I
[08:52] (532.00s)
talk about this, the name toast actually
[08:53] (533.52s)
makes sense because they pop up like
[08:55] (535.44s)
bread from a toaster. Okay, maybe the
[08:57] (537.04s)
name's not that weird. Modals. This UI
[08:58] (538.64s)
component is very common. It's this
[09:00] (540.48s)
pop-up window that takes over your
[09:02] (542.16s)
screen. You've definitely seen these if
[09:04] (544.32s)
you have an ad blocker, and the name for
[09:06] (546.00s)
this actually makes sense. It's called a
[09:07] (547.68s)
modal because it puts your app in a
[09:09] (549.52s)
different mode. You see how everything
[09:10] (550.96s)
behind it gets darkened and you can't
[09:12] (552.40s)
click on it? That's the key feature of a
[09:14] (554.08s)
modal. It forces you to deal with
[09:15] (555.68s)
whatever is in this pop-up before you
[09:17] (557.36s)
can continue with anything else. Login
[09:19] (559.28s)
forms, confirmations, images, settings.
[09:22] (562.72s)
Basically, anytime an app needs your
[09:24] (564.24s)
full attention for a specific task, a
[09:26] (566.00s)
modal is going to show up. You can
[09:27] (567.36s)
usually close them by clicking the X,
[09:29] (569.76s)
pressing escape, or clicking outside of
[09:31] (571.60s)
the modal. Good modals make it obvious
[09:33] (573.44s)
on how to get out of them, but there's
[09:34] (574.96s)
some modals that make it impossible to
[09:36] (576.96s)
leave because they're so terribly made.
[09:39] (579.04s)
Drop downs. This component is pretty
[09:40] (580.56s)
straightforward for once. It's a UI
[09:42] (582.08s)
component that drops down a list of
[09:44] (584.00s)
options. Drop downs are super common for
[09:46] (586.40s)
things like selectors, sorting, user
[09:48] (588.96s)
account menus, or anytime you need to
[09:50] (590.72s)
pick one option from a list, but you
[09:52] (592.24s)
don't want to show all the choices up
[09:53] (593.68s)
front. You got your basic drop downs for
[09:55] (595.44s)
forms, button dropowns that reveal
[09:57] (597.12s)
action menus, navigation dropdowns that
[09:59] (599.20s)
show submen items. The tricky part about
[10:01] (601.12s)
them is when there's too many options.
[10:02] (602.88s)
Now, there's a variation of a dropown
[10:04] (604.48s)
that's technically a different UI
[10:05] (605.92s)
component, and it's called a combo box.
[10:07] (607.92s)
A combo box is a combination of a
[10:09] (609.76s)
drop-own and a text box, which lets you
[10:11] (611.68s)
type and search through all the items
[10:13] (613.12s)
inside the dropown. Good drop-owns let
[10:15] (615.04s)
you scroll through long lists or even
[10:16] (616.72s)
search within the options, and they also
[10:18] (618.40s)
have to be pretty smart about the
[10:19] (619.60s)
positioning so they don't get cut off by
[10:21] (621.20s)
something else. Now, for mobile devices,
[10:22] (622.80s)
drop downs often take over the whole
[10:24] (624.48s)
screen or slide up from the bottom
[10:26] (626.16s)
because trying to select from a tiny
[10:27] (627.52s)
drop-own list with your fat sausage
[10:29] (629.04s)
fingers is basically impossible. Tool
[10:30] (630.88s)
tips. Now, you see this little pop-up
[10:32] (632.24s)
that appears when you hover over
[10:33] (633.36s)
something. This is called a tool tip.
[10:34] (634.96s)
Tool tips give you extra information
[10:36] (636.64s)
about an element without cluttering up
[10:38] (638.32s)
the screen, like when you hover over an
[10:39] (639.92s)
icon and it tells you what it does. Tool
[10:41] (641.60s)
tips are everywhere once you start
[10:43] (643.04s)
looking. Good tool tips are smart about
[10:44] (644.96s)
positioning. They appear above, below,
[10:47] (647.12s)
or to the side depending on where
[10:48] (648.80s)
there's room. They don't want to get cut
[10:50] (650.24s)
off by the edge of the screen or cover
[10:51] (651.84s)
up important content. Now, for mobile
[10:53] (653.60s)
devices, tool tips don't really work
[10:55] (655.84s)
because there's not really a hover
[10:57] (657.20s)
state. So, they usually get replaced
[10:58] (658.64s)
with a long press or they're just always
[11:00] (660.40s)
visible. Badges. Now, you see these
[11:01] (661.92s)
little colored circles with the numbers
[11:03] (663.36s)
or text. These are called badges. And
[11:05] (665.52s)
yeah, just like a police badge or a
[11:06] (666.96s)
scout badge, they're indicators that
[11:08] (668.64s)
tell you something important at a
[11:09] (669.92s)
glance. There's a lot of different ways
[11:10] (670.96s)
to do badges. You've got notification
[11:13] (673.04s)
badges, status badges that say online or
[11:16] (676.00s)
offline or do not deserve, and label
[11:18] (678.08s)
badges that categorize things like new,
[11:20] (680.16s)
sale, or featured. They're usually small
[11:22] (682.08s)
and positioned strategically. Top right
[11:23] (683.92s)
corner for notifications, inline with
[11:25] (685.68s)
text for labels, overlaid on images for
[11:27] (687.92s)
status indicators. The key is that they
[11:29] (689.52s)
need to be noticeable without
[11:30] (690.72s)
overwhelming the main content. It's a
[11:32] (692.32s)
quick way to add extra information
[11:33] (693.68s)
without taking up space. Radio buttons.
[11:35] (695.76s)
I just wanted to mention this because of
[11:37] (697.36s)
the name. You've seen these before. It's
[11:39] (699.12s)
a button that lets you select one option
[11:41] (701.20s)
from a list of options. It's called a
[11:42] (702.88s)
radio button because they're named after
[11:44] (704.48s)
the physical buttons that were used on
[11:46] (706.08s)
old radios to select preset stations.
[11:48] (708.16s)
When you press one of the buttons, the
[11:49] (709.60s)
other buttons would pop out while
[11:50] (710.88s)
leaving the one you selected pushed in.
[11:52] (712.48s)
I stole that from Wikipedia because I
[11:54] (714.24s)
had no idea why they were called radio
[11:55] (715.84s)
buttons. Yeah, that was some components
[11:57] (717.36s)
you should know. Okay, bye.