← Return to myShelf

Building Responsive Designs

It was Monday (I think), 9 AM. I opened my laptop, ran the deploy processes on the project, and boom — "Site is live!" I looked at the layout and said "Beny, you're the GOAT" — everything perfect, pixels on point, fonts just right. Then I checked on my phone. It broke. Everything out of place. Elements overlapping each other, text bleeding off the screen. My breakfast got cold while I tried to figure out what happened.


That's when I learned the truth: responsive isn't a trend — it's survival.


Now, light-years past that traumatic day, I swear on Broly's father that I never start a project on desktop anymore. Mobile-first became a religion. Why? Because it's easier to expand than to shrink. You start small, with the essentials, and add layers as the screen grows. It's like cleaning your room: basics first, decorations later.


In practice, here's how it goes: I write the base styles for mobile without any media queries. Then I add breakpoints with min-width to improve the experience on larger screens. Clean code, less CSS, zero stress. And the layout doesn't break — because you never started broken.


What many don't know is that media queries don't work magic alone. You need flexible units: percentages, vw, vh, and that angel called clamp() for fonts that breathe. Besides that, flexbox and grid are your best friends — they solve 90% of the problems you'd otherwise solve by hand.


I'm pretty sure you've probably already seen a site that worked perfectly on a laptop and turned into a complete mess on an entry-level tablet. Users don't forgive. If they open your site on the bus ride home and can't click the right button — boom, you lost them. They go straight to the competition without even blinking.


So think about it like this: your site needs to be like Vegeta — it adapts to any fight that comes its way. Small screen? It shrinks the elements and keeps its posture. Giant screen? It expands with pride, like a Saiyan prince. Doesn't matter the opponent (or device), the thing just has to work. Unlike early Vegeta, who only knew how to punch everything with no strategy, responsive code thinks before acting. And in the end, that's what separates a common warrior from a true web fighter. (lol sorry, I love making these metaphors, just ignore me...)


Bottom line: start with mobile, use media queries to level up, and test on real devices whenever you can. Your future self — and your users — will thank you. And enjoy your hot coffee, because now you actually know how to do it right.

Tags deste artigo

Leituras Sugeridas