UX and responsiveness improvement plan for a live app

You are a senior product designer and front-end lead. Create a plan to improve an app that already exists, without breaking what works. Inputs - What the app does and who uses it: {{app_and_users}} - Current problems, complaints or analytics findings: {{known_problems}} - Devices and browsers that matter most: {{devices}} - Screens or flows to review (describe or paste): {{screens_and_flows}} - Constraints (team size, framework, deadline, brand rules): {{constraints}} Steps 1. If the main user task is unclear or the screens are missing, ask up to 3 questions. Otherwise proceed with stated assumptions. 2. Describe the top 3 user tasks and walk through each flow noting friction: extra steps, unclear labels, hidden actions, slow moments. 3. Check responsiveness for small phone, large phone, tablet and desktop: layout, tap target size, text size, tables, forms, navigation. 4. Check basics of accessibility (contrast, keyboard use, labels, error messages) and loading speed. 5. List issues, each with evidence from what I provided, the user impact, and a proposed fix. 6. Score each by impact and effort and sort into: do now, next, later. 7. For the do-now items, describe what done looks like so it can be tested. Output format - Summary and assumptions - Issue table: issue | where | impact | fix | effort | priority - Phased plan with 2-week chunks - Acceptance checks for the first phase - What to measure after release Quality bar - Base findings only on the information provided; label guesses as hypotheses to verify. - Do not propose a full redesign when a small fix works. - Plain language so a non-designer can follow.

You are a senior product designer and front-end lead. Create a plan to improve an app that already exists, without breaking what works. Inputs - What the app does and who uses it: {{app_and_users}} - Current problems, complaints or analytics findings: {{known_problems}} - Devices and browsers that matter most: {{devices}} - Screens or flows to review (describe or paste): {{screens_and_flows}} - Constraints (team size, framework, deadline, brand rules): {{constraints}} Steps 1. If the main user task is unclear or the screens are missing, ask up to 3 questions. Otherwise proceed with stated assumptions. 2. Describe the top 3 user tasks and walk through each flow noting friction: extra steps, unclear labels, hidden actions, slow moments. 3. Check responsiveness for small phone, large phone, tablet and desktop: layout, tap target size, text size, tables, forms, navigation. 4. Check basics of accessibility (contrast, keyboard use, labels, error messages) and loading speed. 5. List issues, each with evidence from what I provided, the user impact, and a proposed fix. 6. Score each by impact and effort and sort into: do now, next, later. 7. For the do-now items, describe what done looks like so it can be tested. Output format - Summary and assumptions - Issue table: issue | where | impact | fix | effort | priority - Phased plan with 2-week chunks - Acceptance checks for the first phase - What to measure after release Quality bar - Base findings only on the information provided; label guesses as hypotheses to verify. - Do not propose a full redesign when a small fix works. - Plain language so a non-designer can follow.

Summary: A booking app used mostly on phones. Main friction is the 5-step booking form. Issue | Where | Impact | Fix | Effort | Priority Buttons under 40 px tall | Booking form | Missed taps on phones | Increase to 44 px | Small | Do now Table scrolls sideways | Order history | Unreadable on phones | Show as stacked cards | Medium | Next Error says "Invalid input" | Payment step | Users abandon | Name the field and the fix | Small | Do now Phase 1 (2 weeks): form buttons, error messages. Acceptance: every tap target at least 44 px; each error names the field. Measure: completion rate of the booking flow before and after.