#1 India's Top IT Training Institute
×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
Mentors

Mentors

Meet the industry experts who train and guide you through your course.

Read More →
Free Resources

Free Resources

Free tutorials, interview questions, tools and calculators to help you learn.

Explore →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →

UI/UX Design · Beginner Mistakes

Common Mistakes Beginners Make Learning UI/UX Design

The habits that hold back new UI/UX designers, grouped by stage: while learning, while designing, and while building a portfolio, with a practical fix for each.

Tracks
Design Mistakes · Live Interactive
Focus
—
Key insight
Strategy
—
Approach
Result
—
Outcome
No Research → Visual Overkill → No Feedback → Design Success
Click a tab to explore common UI/UX design mistakes and how to avoid them.

Home / Tutorials / UI/UX Design / Common Mistakes Beginners Make Learning UI/UX Design

UI/UX Design · Beginner Mistakes

Common Mistakes Beginners Make Learning UI/UX Design

A design can look polished in Figma and still fail the moment a real person tries to use it. That gap, between what looks good and what works, is where most beginner mistakes sit. Below they are grouped by the stage where they usually appear, so you can check the ones that apply to where you are now.

While you are learning

Learning tools instead of design

Many beginners spend weeks on Figma shortcuts, auto layout and plugins and very little on why a layout works. Tools change; principles such as visual hierarchy, alignment, spacing, contrast and consistency do not. Try this instead: for every tool tutorial, study one principle and redesign a screen you use daily (a bank app, a railway booking page) applying only that principle.

Treating UI and UX as the same thing

UI is how the interface looks and responds: type, colour, components, states. UX is whether the whole experience helps someone finish a task: research, flows, information architecture, testing. Beginners who only practise UI end up with beautiful screens that solve the wrong problem. Try this instead: before opening a design tool, write down who the user is, what they are trying to do, and what currently gets in their way.

Copying Dribbble shots without understanding them

Inspiration sites are full of concept shots made to look good in a thumbnail, often with low-contrast text and no real content. Copying them teaches style, not problem-solving. Try this instead: study real, shipped products and ask why each element is there.

While you are designing

Skipping user research

Designing from your own assumptions feels faster, but you are rarely the user. A student designing a food delivery app for elderly parents in Lucknow will make different choices after talking to three of them for twenty minutes each. Try this instead: run short interviews (five or six open questions, no leading ones), note pain points in the user's own words, and only then sketch.

Never testing with real people

Jakob Nielsen's widely cited 2000 article argued that small rounds of usability testing, around five users each, uncover most of the problems in a design, and that several small rounds beat one large one. You do not need a lab. Try this instead: give a friend or classmate a task ("book a ticket for Saturday"), ask them to think aloud, and stay silent while they use your prototype. Note where they hesitate, then fix and repeat.

Ignoring accessibility

The World Health Organization estimates that about 1.3 billion people, roughly one in six worldwide, live with a significant disability, and many more have temporary or situational limits such as bright sunlight or one free hand. Common beginner failures and the standards to check against:

ProblemGuideline
Light grey text on whiteWCAG AA asks for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text
Tiny tap targetsWCAG 2.2 sets a 24×24 CSS pixel minimum; Apple suggests 44×44 points and Material Design 48×48 dp
Meaning shown only by colourAdd text, icons or patterns, for example "Error: enter a 10-digit mobile number" rather than a red border alone
Placeholder used as the only labelKeep a visible label; placeholders disappear when the user types

Figma has contrast-checking plugins, and browser developer tools can check contrast on built pages.

Too many fonts, colours and styles

Three typefaces, eight colours and buttons in four styles make a screen feel noisy and hard to scan. Try this instead: one typeface family with a clear size scale, one primary colour plus neutrals and semantic colours (success, warning, error), and a single button style per level of importance.

Designing only the happy path

Beginners design the screen where everything works. Real products also need empty states (no orders yet), loading, errors (payment failed, no internet), long names that overflow, and the first-time experience. Try this instead: for every main screen, list its states and design at least the empty and error versions.

Designing for one screen size

Most people in India reach the internet on a phone, often a mid-range Android device with a smaller screen than a designer's monitor. Try this instead: start with a mobile frame, check the design on an actual phone with the Figma mobile app, and then adapt to larger screens.

Not talking to developers

Handing over a file with inconsistent spacing, unnamed layers and no component states creates rework. Try this instead: use components and variants, a spacing system (multiples of 4 or 8), and annotate interactions. A short call with the developer before handover saves days later.

While you are building a portfolio

Showing only final screens

Recruiters and design leads want to see how you think. A gallery of polished mock-ups does not show that. Try this instead: write each project as a case study: problem, users, research findings, early sketches, what testing changed, the final design, and what you would do next.

Three generic projects

Food delivery, travel booking and a fitness tracker are the most common student projects, so they blend together. Try this instead: pick problems you have access to, such as your college's admission portal, a local clinic's appointment booking or a parent's small shop, and redesign with real users.

Learning alone

Without feedback, mistakes repeat. Try this instead: share work in design communities, ask for critique on specific questions ("is the hierarchy on this checkout clear?"), and give feedback to others, which trains your own eye.

A quick check before you share any design

  • Can I say who this is for and what task it supports, in one sentence?
  • Have at least two people outside my team tried it?
  • Does text pass contrast checks, and are tap targets large enough?
  • Have I designed empty, loading and error states?
  • Does it work on a small phone screen?
  • Are components and spacing consistent?

To go further, see the UI/UX skills beginners should learn, designing web layouts in Figma, and the UI/UX design resume guide when you are ready to apply. Uncodemy's UI/UX course covers research, design and portfolio reviews if you want structured feedback.