Common Issues
mobile
Buttons and Links Too Small to Tap on Mobile
Your app's buttons, links, and clickable elements are so small on a phone that users keep tapping the wrong thing or can't tap them at all. They have to zoom in just to hit the right button, and even then they might accidentally tap something else because everything is crammed together.
This is incredibly frustrating for users and is one of the main reasons people leave a website on their phone. If the "Buy Now" button, the navigation menu, or the login form requires surgical precision to use, people will give up and go somewhere else.
Google also penalizes websites with this problem. If your tap targets are too small, your site will rank lower in mobile search results, meaning fewer people will even find your app in the first place.
Error Messages You Might See
No error — just difficult/impossible to use
Tap targets too small (Google Search Console)
Mobile usability issues found (Google alert)
Links too close together (PageSpeed Insights)
Common Causes
- Desktop-sized buttons — Buttons were designed for a mouse cursor (which is precise) and not for a finger (which covers a large area)
- Too many links close together — Navigation items, footer links, or form fields are packed too tightly for finger tapping
- Text links with no padding — Clickable text has no extra space around it, making the tap target only as big as the text itself
- Font size too small on mobile — Text shrinks to an unreadable size on small screens, and the buttons scale down with it
- No mobile-specific sizing — The same CSS sizes are used for both desktop and mobile without adjustment
How to Fix It
- Make all buttons at least 44x44 pixels — Apple and Google both recommend a minimum tap target size of 44x44 pixels (about the size of a fingertip)
- Add spacing between clickable elements — Leave at least 8 pixels of space between buttons and links so users don't accidentally tap the wrong one
- Use larger font sizes on mobile — Body text should be at least 16 pixels on mobile to be comfortably readable
- Test with your thumb — Open the app on your phone and try to use it with just your thumb. If it's hard, the targets are too small
- Run Google's mobile-friendly test — Go to search.google.com/test/mobile-friendly and enter your URL to see what Google thinks about your tap targets
Real developers can help you.
Matt Butler
Software Engineer @ AWS
hanson1014
Full-stack developer experienced in fixing and deploying AI-generated apps from Lovable, Bolt.new, Cursor, and Replit. I specialize in debugging Supabase integration issues (auth flows, RLS policies, database connections), fixing broken deployments, resolving routing/blank screen problems, and cleaning up messy React/Vite codebases. I also build production apps with the Claude API and have shipped a Mac desktop dev tool (Nexterm from scratch. Based in Hong Kong, fast turnaround.
Rudra Bhikadiya
I build and fix web apps across Next.js, Node.js, and DBs.
Comfortable jumping into messy code, broken APIs, and mysterious bugs.
If your project works in theory but not in reality, I help close that gap.
PawelPloszaj
I'm fronted developer with 10+ years of experience with big projects. I have small backend background too
zipking
I am a technologist and product builder dedicated to creating high-impact solutions at the intersection of AI and specialized markets. Currently, I am focused on PropScan (EstateGuard), an AI-driven SaaS platform tailored for the Japanese real estate industry, and exploring the potential of Archify.
As an INFJ-T, I approach development with a "systems-thinking" mindset—balancing technical precision with a deep understanding of user needs. I particularly enjoy the challenge of architecting Vertical AI SaaS and optimizing Small Language Models (SLMs) to solve specific, real-world business problems. Whether I'm in a CTO-level leadership role or hands-on with the code, I thrive on building tools that turn complex data into actionable value.
Mehdi Ben Haddou
- Founder of Chessigma (1M+ users) & many small projects
- ex Founding Engineer @Uplane (YC F25)
- ex Software Engineer @Amazon and @Booking.com
Matthew Butler
Systems Development Engineer @ Amazon Web Services
legrab
I'll fill this later
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.
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.
Describe what's wrong in plain English. No technical knowledge needed.
Get HelpFrequently Asked Questions
What's the minimum size a button should be on mobile?
Both Apple and Google recommend at least 44x44 pixels (about 11mm) for any tappable element. This matches the average size of a fingertip. Anything smaller becomes frustrating to use accurately.
Will making buttons bigger mess up the desktop version?
Not if a developer uses responsive design. They can make buttons bigger only on mobile screens while keeping the desktop design unchanged using CSS media queries.