> For the complete documentation index, see [llms.txt](https://outdraw-academy.gitbook.io/become-a-ux-designer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://outdraw-academy.gitbook.io/become-a-ux-designer/roadmap/month-2-learn-ux-patterns.md).

# 🍜 Month 2: Learn UX Patterns

&#x20;As a UX Designer, you need to be familiar with these patterns and be able to use them in your designs. It's important to learn them upfront, so that when it's time to solve a desing problem, you have something to fall back on and choose from.

## Analyzing design systems

This is how I've started learning UX design, and it was the fastest and easiest way to wrap my head around different UX and UI patterns.

I recommend starting with [Material Design's ](https://m3.material.io/components)components and guidelines. It's the easiest to consume and a very comprehensive design system. You can read specificacion and guidelines on how to build and use components. They also provide a Figma library so that you can start using the design system in your projects, especially when designing Android apps.

I also recommend analyzing [Polaris by Shopify](https://polaris.shopify.com/). There will be a lot of overlapping components and topics, but you'll see how the design systems vary when it comes to naming conventions, usage, and restrictions.

And the last one is [Human Interface Guidelines by Apple](https://developer.apple.com/design/human-interface-guidelines/) 🍎. It's best if you explore it as the last one since it's the least beginner-friendly on this list. At the same time, it's very important since Apple products are extremely popular, and you need to know how to design for different devices and operation systems.

## UX Patterns series

Another method to learn about UX patterns is to explore my 'UX Patterns' series. I'm continuously building a library of videos and articles. I'll put the link to the playlist here and link the knowledge base in the description.

* 👀 [UX Patterns series](https://www.youtube.com/playlist?list=PLbGmbQvnHhkXxCWmKrHvboG-JAIorNzCB) on Youtube
* ✍️ [UX Patterns knowledge base](https://outdraw-academy.gitbook.io/ux-patterns/)

In this series, I not only explain the patterns and components but also dive deeper into how to design them, what mistakes to avoid, and what to pay attention to. We analyze how the UX patterns are used in various products and across different design systems.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://outdraw-academy.gitbook.io/become-a-ux-designer/roadmap/month-2-learn-ux-patterns.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
