Mobile-first philosophy in Tailwind - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the term mobile-first philosophy mean in web development?

It means designing and building websites starting with the smallest screen (mobile devices) first, then scaling up to larger screens like tablets and desktops.

beginner

Why is mobile-first design important?

Because most people use mobile devices to browse the web, so starting with mobile ensures the site works well on small screens and loads fast.

intermediate

How does Tailwind CSS support mobile-first philosophy?

Tailwind applies styles to mobile by default and uses prefixes like sm:, md: for larger screens, making it easy to add styles as screen size grows.

intermediate

What is the difference between mobile-first and desktop-first CSS?

Mobile-first CSS starts with styles for small screens and adds bigger screen styles with media queries. Desktop-first starts with big screens and adds smaller screen styles, which can be harder to maintain.

beginner

Give an example of a Tailwind class that applies only on medium screens and up.

The class md:text-lg changes the text size to large only on medium screens (768px) and larger.

What is the first step in mobile-first web design?

A Ignore screen sizes

B Design for desktop screens first

C Design for small screens first

D Design only for tablets

Mobile-first means starting with small screens like phones before scaling up.

In Tailwind CSS, which prefix applies styles starting at the small screen breakpoint?

A sm:

B md:

C lg:

D xl:

The sm: prefix applies styles at the small screen breakpoint (640px) and above.

Why is mobile-first design better for performance?

A Because it loads styles for small screens first, reducing unnecessary code

B Because it ignores mobile users

C Because it uses only desktop styles

D Because it disables images on mobile

Mobile-first loads only needed styles for small screens first, improving speed.

Which Tailwind class applies a style only on large screens and bigger?

A md:bg-blue-500

B sm:bg-blue-500

C bg-blue-500

D lg:bg-blue-500

The lg: prefix applies styles starting at large screens (1024px) and up.

What is a key benefit of designing mobile-first?

A Ignoring desktop users

B Better user experience on small devices

C Making sites only for phones

D Using fixed widths

Mobile-first ensures the site works well and is easy to use on small devices.

Explain the mobile-first philosophy and how Tailwind CSS helps implement it.

Think about how styles grow from small to large screens.

Describe why mobile-first design improves website performance and user experience.

Consider the common device people use to browse the web.

Practice

1. What does the mobile-first philosophy mean in web design?

easy

A. Designing for small screens first, then adding styles for larger screens

B. Designing only for desktop screens

C. Designing for large screens first, then adjusting for smaller screens

D. Ignoring screen sizes and using fixed layouts

Solution

1. Step 1: Understand mobile-first philosophy

   Mobile-first means starting design with small screens like phones, then adding styles for bigger screens.

2. Step 2: Compare options

   Only Designing for small screens first, then adding styles for larger screens correctly describes this approach; others describe desktop-first or fixed layouts.

3. Final Answer:

   Designing for small screens first, then adding styles for larger screens -> Option A

4. Quick Check:

   Mobile-first = Start small screens first [OK]

Hint: Mobile-first means start small, then grow bigger [OK]

Common Mistakes:

• Thinking mobile-first means designing desktop first
• Confusing mobile-first with ignoring screen sizes
• Believing mobile-first means only designing for phones

2. Which Tailwind CSS class applies styles only on medium and larger screens?

easy

A. md:bg-blue-500

B. bg-blue-500

C. sm:bg-blue-500

D. lg:bg-blue-500

Solution

1. Step 1: Understand Tailwind screen prefixes

   In Tailwind, md: applies styles at medium screen size and above.

2. Step 2: Identify correct prefix for medium screens

   md:bg-blue-500 uses md:, so it applies on medium and larger screens. Others apply on small, large, or all screens.

3. Final Answer:

   md:bg-blue-500 -> Option A

4. Quick Check:

   md: means medium screens and up [OK]

Hint: Remember md: prefix targets medium+ screens [OK]

Common Mistakes:

• Confusing sm: with md:
• Using no prefix and expecting medium-only styles
• Mixing lg: with md:

3. Given this Tailwind code:

<div class="bg-red-500 md:bg-green-500">Box</div>

What background color will the box have on a small screen?

medium

A. Green

B. Red

C. No color

D. Blue

Solution

1. Step 1: Analyze classes on small screen

   The class bg-red-500 applies to all screens by default. The md:bg-green-500 applies only on medium and larger screens.

2. Step 2: Determine active class on small screen

   On small screens, md:bg-green-500 is ignored, so background stays red.

3. Final Answer:

   Red -> Option B

4. Quick Check:

   Default class applies on small screens [OK]

Hint: Default classes apply on all screens unless overridden [OK]

Common Mistakes:

• Thinking md: classes apply on small screens
• Ignoring default classes
• Assuming no color if md: class exists

4. What is wrong with this Tailwind code if the goal is to make text blue on small screens and red on medium and larger screens?

<p class="md:text-red-500 text-blue-500">Hello</p>

medium

A. The order of classes is reversed; it should be text-blue-500 md:text-red-500

B. The md: prefix should be on text-blue-500

C. No error; it works as intended

D. Tailwind does not support multiple text color classes

Solution

1. Step 1: Understand class application order

   Tailwind applies base classes first, then overrides with media prefixes like md:.

2. Step 2: Check if code matches goal

   text-blue-500 applies on all screens, overridden by md:text-red-500 on medium+ screens, matching the goal.

3. Final Answer:

   No error; it works as intended -> Option C

4. Quick Check:

   Base then md: override works [OK]

Hint: Base class first, then md: override for bigger screens [OK]

Common Mistakes:

• Thinking order of classes matters in Tailwind
• Believing md: prefix must be on base class
• Assuming Tailwind can't override colors

5. You want a button that is full width on small screens but only 200px wide on medium and larger screens using Tailwind. Which class combination achieves this?

hard

A. w-full w-[200px] md:w-full

B. md:w-full w-[200px]

C. w-[200px] md:w-full

D. w-full md:w-[200px]

Solution

1. Step 1: Understand mobile-first width classes

   Use w-full for full width on small screens (default). Use md:w-[200px] to set width 200px on medium+ screens.

2. Step 2: Check options for correct order and values

   w-full md:w-[200px] sets full width by default, then overrides to 200px on medium screens. Others reverse or duplicate incorrectly.

3. Final Answer:

   w-full md:w-[200px] -> Option D

4. Quick Check:

   Default full width, md override 200px [OK]

Hint: Default small screen first, then md: for bigger screens [OK]

Common Mistakes:

• Reversing order of width classes
• Using md: on full width instead of fixed width
• Duplicating conflicting width classes