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.
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.
prajwalfullstack
Hi Im a full stack developer, a vibe coded MVP to Market ready product, I'm here to help
Luca Liberati
I work on monoliths and microservices, backends and frontends, manage K8s clusters and love to design apps architecture
legrab
I'll fill this later
Matthew Jordan
I've been working at a large software company named Kainos for 2 years, and mainly specialise in Platform Engineering. I regularly enjoy working on software products outside of work, and I'm a huge fan of game development using Unity. I personally enjoy Python & C# in my spare time, but I also specialise in multiple different platform-related technologies from my day job.
Victor Denisov
Developer
Jacek Rozanski
Senior PHP/Symfony developer and DevOps engineer with 20+ years of professional experience, running opcode.pl (web development agency, est. 2004).
Day job: I'm the sole backend developer at merketing company where I own and maintain 11 PHP/Symfony microservices on AWS (ECS Fargate, RDS, S3, CloudFront), handle the full CI/CD pipeline (Bitbucket Pipelines, Docker), and manage monitoring with Sentry and CloudWatch. These services handle high request volumes in production every month.
What I bring to AI-built apps:
- I audit and fix security issues (OWASP methodology), performance bottlenecks, and architectural problems in codebases generated by Cursor, Claude Code, Lovable, Bolt, and v0
- I refactor AI-generated prototypes into production-grade applications with proper error handling, testing, and clean architecture (SOLID, DDD, hexagonal architecture)
- I set up the infrastructure AI tools don't touch: AWS hosting, CI/CD pipelines, automated deployments, database optimization, monitoring, and alerting
- I integrate external services: payment providers, email systems, partner APIs, SSO/auth
Tech stack: PHP 8.x, Symfony, React, Next.js, PostgreSQL, MySQL, Docker, AWS (ECS, RDS, S3, SQS/SNS, CloudFront), Terraform, Supabase. I also use AI tools daily (Claude Code, Cursor) in my own workflow, so I understand both the strengths and the gaps in AI-generated code.
Based in Poland (CET timezone). Available for async work and calls during EU/US business hours.
Matt Butler
Software Engineer @ AWS
PawelPloszaj
I'm fronted developer with 10+ years of experience with big projects. I have small backend background too
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.
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.