Claude Code mobile

Responsive Layout Breaks Below 375px Screen Width

Your application's layout breaks on very small screens (below 375px width), even though it looks fine on standard mobile sizes. Elements overflow horizontally, text gets cut off, buttons become untappable, and the page requires horizontal scrolling to use.

This affects users with older or smaller phones (iPhone SE, Galaxy A series), users who have increased their system font size, and users viewing your app in split-screen mode on tablets. These are real users who are completely locked out of your app.

Claude Code typically generates responsive CSS targeting common breakpoints (768px, 640px) but doesn't account for screens smaller than 375px, where fixed pixel widths, min-width declarations, and padding cause layout overflow.

Error Messages You Might See

Horizontal scroll appears on mobile Layout shifts when rotating device Elements overflow viewport boundary Touch targets too small (Lighthouse audit)
Horizontal scroll appears on mobileLayout shifts when rotating deviceElements overflow viewport boundaryTouch targets too small (Lighthouse audit)

Common Causes

  • min-width on containers — CSS rules like min-width: 375px or min-width: 320px prevent the layout from shrinking further
  • Fixed pixel widths — Elements have width: 360px or similar fixed values that can't adapt to smaller screens
  • Horizontal padding overflow — Container padding (e.g., px-8 / 32px on each side) consumes too much of the narrow viewport
  • Flexbox not wrapping — Row layouts with flex-nowrap force elements side by side when they should stack
  • Media queries start too high — The smallest breakpoint is 640px, with no styles for screens below that

How to Fix It

  1. Design mobile-first — Write base styles for the smallest screen, then add complexity with min-width media queries
  2. Replace fixed widths with percentages or max-width — Use width: 100% or max-width: 100% instead of pixel values
  3. Reduce padding on small screens — Use responsive padding like p-3 sm:p-6 to reduce spacing on narrow viewports
  4. Test at 320px width — Use Chrome DevTools responsive mode set to 320px to find overflow issues
  5. Add overflow-x: hidden cautiously — Only on the body element as a safety net, not as a fix for individual layout issues
  6. Use clamp() for font sizes — Replace fixed font sizes with clamp(14px, 4vw, 18px) for fluid typography

Real developers can help you.

Milan Surelia Milan Surelia Milan Surelia is a Mobile App Developer with 5+ years of experience crafting scalable, cross-platform apps at 7Span and Meticha. At 7Span, he engineers feature-rich Flutter apps with smooth performance and modern UI. As the Co-Founder of Meticha, he builds open-source tools and developer-focused products that solve real-world problems. Expertise: 💡 Developing cross-platform apps using Flutter, Dart, and Jetpack Compose for Android, iOS, and Web. 🖋️ Sharing insights through technical writing, blogging, and open-source contributions. 🤝 Collaborating closely with designers, PMs, and developers to build seamless mobile experiences. Notable Achievements: 🎯 Revamped the Vepaar app into Vepaar Store & CRM with a 2x performance boost and smoother UX. 🚀 Launched Compose101 — a Jetpack Compose starter kit to speed up Android development. 🌟 Open source contributions on Github & StackOverflow for Flutter & Dart 🎖️ Worked on improving app performance and user experience with smart solutions. Milan is always happy to connect, work on new ideas, and explore the latest in technology. Alvin Voo Alvin Voo I’ve watched the tech landscape evolve over the last decade—from the structured days of Java Server Pages to the current "wild west" of Agentic-driven development. While AI can "vibe" a frontend into existence, I specialize in the architecture that keeps it from collapsing. My expertise lies in the critical backend infrastructure: the parts that must be fast, secure, and scalable. I thrive on high-pressure environments, such as when I had only three weeks to architect and launch an Ethereum redemption system with minimal prior crypto knowledge, turning it into a major revenue stream. What I bring to your project: Forensic Debugging: I don't just "patch" bugs; I use tools like Datadog and Explain Analyzers to map out bottlenecks and resolve root causes—like significantly reducing memory usage by optimizing complex DB joins. Full-Stack Context: Deep experience in Node.js and React, ensuring backends play perfectly with mobile and web teams. Sanity in the Age of AI: I bridge the gap between "best practices" and modern speed, ensuring your project isn't just built fast, but built to last. David Olverson David Olverson Solo dev shipping production apps with AI-assisted development. I specialize in rescuing broken Lovable/Bolt/Cursor builds and taking them to production. 10+ apps shipped including SaaS CRMs, gaming platforms, real estate tools, and Discord bots. Stack: Next.js 16, TypeScript, Tailwind CSS, FastAPI, PostgreSQL, Prisma. I use Claude Code with 50+ custom skills for rapid delivery. Average turnaround: 2-4 weeks from broken prototype to production. Tejas Chokhawala Tejas Chokhawala Full-stack engineer with 5 years experience building production web apps using React, Next.js and TypeScript. Focused on performance, clean architecture and shipping fast. Experienced with Supabase/Postgres backends, Stripe billing, and building AI-assisted developer tools. Basel Issmail Basel Issmail ’m a Senior Full-Stack Developer and Tech Lead with experience designing and building scalable web platforms. I work across the full development lifecycle, from translating business requirements into technical architecture to delivering reliable production systems. My work focuses on modern web technologies, including TypeScript, Angular, Node.js, and cloud-based architectures. I enjoy solving complex technical problems and helping teams turn product ideas and prototypes into working platforms that can grow and scale. In addition to development, I often collaborate closely with product managers, business analysts, designers, and QA teams to ensure that solutions align with both technical and business goals. I enjoy working with startups and product teams where I can contribute both as a hands-on engineer and as a technical partner in designing and delivering impactful software. Daniel Vázquez Daniel Vázquez Software Engineer with over 10 years of experience on Startups, Government, big tech industry & consulting. Pratik Pratik SWE with 15+ years of experience building and maintaining web apps and extensive BE infrastructure legrab legrab I'll fill this later Caio Rodrigues Caio Rodrigues I'm a full-stack developer focused on building practical and scalable web applications. My main experience is with **React, TypeScript, and modern frontend architectures**, where I prioritize clean code, component reusability, and maintainable project structures. I have strong experience working with **dynamic forms, state management (Redux / React Hook Form), and complex data-driven interfaces**. I enjoy solving real-world problems by turning ideas into reliable software that companies can actually use in their daily operations. Beyond coding, I care about **software quality and architecture**, following best practices for componentization, code organization, and performance optimization. I'm also comfortable working across the stack when needed, integrating APIs, handling business logic, and helping transform prototypes into production-ready systems. My goal is always to deliver solutions that are **simple, efficient, and genuinely useful for the people using them.** Antriksh Narang Antriksh Narang 5 years+ Experienced Dev (Specially in Web Development), can help in python, javascript, react, next.js and full stack web dev technologies.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help

Frequently Asked Questions

What is the smallest screen width I should support?

Design for 320px as the minimum. This covers iPhone SE, older Android phones, and split-screen tablet usage. Test at 320px during development to catch overflow issues early.

How do I find what's causing horizontal scroll?

In Chrome DevTools, add a temporary style: * { outline: 1px solid red; } to see every element's boundaries. The element extending beyond the viewport edge is your culprit.

Related Claude Code Issues

Can't fix it yourself?
Real developers can help.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help