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)
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
- Design mobile-first — Write base styles for the smallest screen, then add complexity with min-width media queries
- Replace fixed widths with percentages or max-width — Use width: 100% or max-width: 100% instead of pixel values
- Reduce padding on small screens — Use responsive padding like p-3 sm:p-6 to reduce spacing on narrow viewports
- Test at 320px width — Use Chrome DevTools responsive mode set to 320px to find overflow issues
- Add overflow-x: hidden cautiously — Only on the body element as a safety net, not as a fix for individual layout issues
- Use clamp() for font sizes — Replace fixed font sizes with clamp(14px, 4vw, 18px) for fluid typography
Real developers can help you.
Jaime Orts-Caroff
I'm a Senior Android developer, open to work in various fields
Krishna Sai Kuncha
Experienced Professional Full stack Developer with 8+ years of experience across react, python, js, ts, golang and react-native. Developed inhouse websearch tooling for AI before websearch was solved : )
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.**
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.
Nam Tran
10 years as fullstack developer
Stanislav Prigodich
15+ years building iOS and web apps at startups and enterprise companies. I want to use that experience to help builders ship real products - when something breaks, I'm here to fix it.
Anthony Akpan
Developer with 8 years of experience building softwares fro startups
Franck Plazanet
I am a Strategic Engineering Leader with over 8 years of experience building high-availability enterprise systems and scaling high-performing technical teams. My focus is on bridging the gap between complex technology and business growth.
Core Expertise:
🚀 Leadership: Managing and coaching teams of 15+ engineers, fostering a culture of accountability and continuous improvement.
🏗️ Architecture: Enterprise Core Systems, Multi-system Integration (ERP/API/ETL), and Core Database Structure.
☁️ Cloud & Scale: AWS Expert; architected systems handling 10B+ monthly requests and managing 100k+ SKUs.
📈 Business Impact: Aligning tech strategy with P&L goals to drive $70k+ in monthly recurring revenue.
I thrive on "out-of-the-box" thinking to solve complex technical bottlenecks and am always looking for ways to use automation to improve business productivity.
Daniel Vázquez
Software Engineer with over 10 years of experience on Startups, Government, big tech industry & consulting.
Omar Faruk
As a Product Engineer at Klasio, I contributed to end-to-end product development, focusing on scalability, performance, and user experience.
My work spanned building and refining core features, developing dynamic website templates, integrating secure and reliable payment gateways, and optimizing the overall system architecture.
I played a key role in creating a scalable and maintainable platform to support educators and learners globally.
I'm enthusiastic about embracing new challenges and making meaningful contributions.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently 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.