Flows category icon
Debugging
Beginner

Improve Mobile Responsiveness

Make your app genuinely usable on phones: audit at real widths, fix layouts, and verify touch targets.

5 steps15 verify checks45-75 minutesWorks with: emergent · chatgpt · claude · cursor
Start Guided Walkthrough

The Route

0/5 verified

Context Pack

Paste this first. It briefs the AI on requirements, constraints, and the Definition of Done before your first build prompt.

Context Pack
PROJECT CONTEXT:
My app was built desktop-first and breaks or feels unusable on mobile screens.

GOAL:
Every page works and feels native at 375px width with proper touch targets and no horizontal scroll.

REQUIREMENTS:
- Page-by-page audit at 375px and 768px
- No horizontal overflow anywhere
- Readable text and tappable targets (44px minimum)
- Usable navigation on small screens
- Forms and tables adapted for mobile

CONSTRAINTS:
- Do not hide core functionality on mobile as a 'fix'
- Test at real viewport widths, not by resizing casually

DEFINITION OF DONE:
- No page horizontally scrolls at 375px
- All interactive elements are comfortably tappable
- Navigation is fully usable on mobile
- Forms, modals, and tables work on small screens

COMMON FAILURES TO AVOID:
- Fixed-width containers forcing horizontal scroll
- Desktop nav unusable with no mobile menu
- Tables overflowing with no scroll or stacking strategy
- Modals taller than the viewport with unreachable buttons

Paste this into your AI builder first. It teaches the AI what you want before you give it the build prompt.

Related routes

More Debugging flows that share ground with this one.

Flows category icon
Debugging

Add Database Persistence

Your app forgets everything on refresh: move state into a real database with working CRUD.

01Inventory unpersisted state
02Design models and endpoints
03Wire writes to the backend

+2 more steps to Done

Best foryour first pass at this - no prior setup assumed

5 steps45-75 minutesBeginner
Flows category icon
Debugging

Add Loading/Error States

Eliminate silent failures and frozen screens: add loading, empty, and error states across the whole app.

01Inventory async surfaces
02Add loading states
03Add error states with retry

+2 more steps to Done

Best foryour first pass at this - no prior setup assumed

5 steps30-60 minutesBeginner
Flows category icon
Debugging

Fix App That Looks Good But Does Not Work

The systematic recovery flow for beautiful-but-broken AI builds: audit honestly, then fix by functional priority.

01Run a brutal functional audit
02Prioritize the fix order
03Fix the core value action

+3 more steps to Done

Best forbuilders who have shipped a basic app before

6 steps60-120 minutesIntermediate

Made with Emergent