Responsive Design for Mobile Devices

Responsive Design for Mobile Devices

The desktop version looks great on a monitor, but on a mobile screen, it's chaos: menus don't fit, buttons overlap, text overflows, and LCP goes through the roof. Responsive design is not just adding max-width: 100% to images. It is the systematic design of an interface that works correctly at widths from 320px to 2560px+, with different pixel densities, input methods (touch vs. mouse), and network conditions. We take on end-to-end implementation. Get a free consultation — we will evaluate your project and suggest the optimal stack. Our clients save between 20% and 40% on development budget by using a Mobile-first approach.

Why Choose Mobile-first?

Mobile-first means writing base styles for mobile and expanding via min-width media queries. The alternative — Desktop-first with max-width — is harder to maintain due to cascading overrides. In practice, Mobile-first reduces debugging time by a factor of 3 compared to Desktop-first.

/* Mobile-first: base styles for mobile */
.card-grid {
  display: grid;
  grid-template-columns: 1fr;
  gap: 16px;
}

@media (min-width: 640px) {
  .card-grid {
    grid-template-columns: repeat(2, 1fr);
    gap: 20px;
  }
}

@media (min-width: 1024px) {
  .card-grid {
    grid-template-columns: repeat(3, 1fr);
    gap: 24px;
  }
}

Choosing the Right Breakpoints

Breakpoints should be determined by content, not devices. There is no point in targeting specific iPhone models — each new generation has different sizes. A typical system: xs (320px), sm (640px), md (768px), lg (1024px), xl (1280px), 2xl (1536px).

Viewport and Units of Measurement

Required meta tag: <meta name="viewport" content="width=device-width, initial-scale=1.0">. Without it, the browser renders the page as 980px wide and scales it — media queries will not work. You can read more about viewport on MDN. As noted by Google in its guide: "We recommend using a mobile-first approach" (Google Search Central).

Use dvh instead of vh for mobile: vh does not account for the browser's address bar, so a 100vh element may be cut off. dvh (dynamic viewport height) changes on scroll. svh and lvh are fixed extreme values.

Responsive Typography

:root {
  --text-base: clamp(1rem, 0.85rem + 0.75vw, 1.125rem);
  --text-lg:   clamp(1.125rem, 1rem + 0.625vw, 1.375rem);
  --text-xl:   clamp(1.375rem, 1rem + 1.875vw, 2rem);
  --text-2xl:  clamp(1.75rem, 1.25rem + 2.5vw, 2.75rem);
  --text-3xl:  clamp(2rem, 1.25rem + 3.75vw, 3.5rem);
}

clamp(min, preferred, max) allows fonts to smoothly scale between min and max depending on viewport width.

Touch Targets and Navigation

On mobile, tappable areas should be at least 44×44px (Apple HIG) or 48×48px (Google Material). Visual size may be smaller; the touch area can be increased using ::before with inset: -12px. For mobile navigation, use a hamburger menu with proper aria attributes and transitions.

Responsive Images

<picture>
  <source media="(min-width: 1024px)" srcset="hero-desktop.webp 1440w, hero-desktop-2x.webp 2880w" sizes="100vw">
  <source media="(min-width: 640px)" srcset="hero-tablet.webp 768w, hero-tablet-2x.webp 1536w">
  <img src="hero-mobile.webp" srcset="hero-mobile.webp 390w, hero-mobile-2x.webp 780w" alt="Responsive version of Hero image" width="390" height="520" loading="eager" fetchpriority="high">
</picture>

sizes tells the browser how much of the screen the image will occupy, allowing it to select the right file before CSS loads.

How to Create Responsive Layout? (Step-by-Step Guide)

1. Analyze mockups: Determine key interface states for different widths.
2. Set up viewport: Add the viewport meta tag with width=device-width, initial-scale=1.0.
3. Mobile-first styles: Write base styles for the minimum width (320px).
4. Media queries: Add min-width queries to expand for larger screens.
5. Testing: Check on real devices and emulators.

Over many years of work, we have accumulated experience in more than 80 projects — allowing us to refine the process to 3 days for landing pages and up to 6 days for corporate sites. Contact us for a free evaluation of your project.

Performance and Comparison of Approaches

Mobile networks are slower. Critical techniques: lazy loading for everything below the fold, font subsetting for Cyrillic, CSS containment on sections. Preload only critical first-screen resources. Mobile-first approach can reduce maintenance costs by up to 30%.

.container {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(280px, 1fr));
  gap: 1rem;
}

What Our Work Includes

We audit your current desktop version and adapt it for mobile. We implement Mobile-first layout with media queries and fluid grids. We set up responsive navigation (hamburger menu, touch zones). We optimize images using responsive images and lazy loading. We configure typography using clamp(). We test on real devices (iOS, Android, tablets). We hand over documentation on breakpoints and techniques used. We provide support — fixes based on test results. Reduced long-term development costs are another benefit of this approach.

Timeframes

Cost is calculated individually after scope evaluation — contact us to discuss details. We will evaluate your project for free.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

• React Query / TanStack Query — for server state (API data, caching, invalidation)
• Zustand — for global client state (lightweight, no Redux boilerplate)
• React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

• Source code in Git with full commit history and branching strategy
• Architecture document — component tree, data flow, routing decisions
• Component documentation – Storybook with stories for all reusable components
• CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
• Access to staging environment during development and after launch
• Team training – 2‑3 live walkthrough sessions with your developers
• 3‑month warranty on any bugs found in production
• Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.