How to Find UX Problems in Everyday Apps
You do not need a client brief to practise UX. Everyday apps are full of opportunities to observe friction, understand user goals and turn small moments of confusion into useful design insights.
Where UX problems hide in everyday apps
Look beyond visual design. A useful UX observation considers the complete task and context.
Onboarding
Look for unnecessary questions, unclear value, confusing permissions or weak first-task guidance.
Navigation
Check whether labels, hierarchy and location help users predict where to go next.
Search
Observe query entry, filters, results, empty states and recovery from poor searches.
Forms
Look for unclear fields, unnecessary input, weak error messages and poor completion feedback.
Checkout
Study trust, price clarity, progress, payment errors and last-minute surprises.
Notifications
Ask whether alerts are timely, useful, understandable and easy to control.
Content
Check labels, instructions, empty states, error copy and information hierarchy.
Accessibility
Consider readability, contrast, touch targets, focus, keyboard access and other relevant needs.
Feedback
Observe whether the interface tells users what happened after an action.
Interactive UX Observer
Pick a common task and practise asking better UX questions.
Booking a service
Goal: complete a booking confidently. Observe search, availability, date/time selection, price clarity, confirmation and changes. Ask: “Where might a first-time user hesitate?”
Buying a product
Goal: choose and purchase the right product. Observe product discovery, comparison, variants, delivery information, trust and checkout. Ask: “What information is missing at the moment of decision?”
Learning something
Goal: understand and practise a concept. Observe discovery, lesson structure, progress, feedback and next steps. Ask: “Does the interface help the user know what to do next?”
Making a payment
Goal: pay successfully and know the transaction status. Observe amount confirmation, authentication, errors, loading and receipts. Ask: “What happens if something goes wrong?”
Ordering food
Goal: find suitable food and complete an order. Observe search, filters, menu information, customisation, fees, delivery time and order tracking.
Interactive UX problem audit
Tick what you observe in an app. Your score helps you decide where to investigate—not whether the app is objectively bad.
0 potential issues selected. Start by observing a real task.
Turn an observation into a UX problem statement
Use this interactive tool to avoid vague statements such as “the app is confusing.”
Use the “Why?” ladder
When you notice friction, do not stop at the first explanation.
What happened?
Describe the observable behaviour or interface moment.
Why might it happen?
Consider language, hierarchy, mental models, context or system behaviour.
What evidence do we need?
Decide how you would verify the suspected problem.
Who is affected?
Identify the user group and situation rather than assuming everyone has the same issue.
How important is it?
Consider frequency, task importance, severity and recoverability.
What could improve?
Only after diagnosis, explore potential solutions and trade-offs.
Quick quiz: can you spot a real UX problem?
Turn everyday observations into portfolio practice
One useful way to practise UX is to document the problem, evidence, analysis and redesign idea without pretending the work was commissioned.
Frequently asked questions
Train your eye to see UX problems everywhere.
Build practical UX thinking, research skills, interface design and portfolio projects with structured learning.