Introduction
Ask a hiring manager what they look for in a junior UI/UX designer, and the answer is rarely "knows every Figma shortcut." It's usually some version of: show me how you think. Tools can be learned in weeks. Judgment, process, and the ability to turn a messy problem into a clear, usable design take practice, and the best way to build them is by doing real projects.
The challenge for most students is knowing which projects are worth their time. Redrawing the same trendy dashboard everyone else posts on Dribbble won't set you apart. This guide covers five practice projects that build the exact skills employers test for, with a clear goal, steps, and finish line for each, so you end up with a portfolio that tells a convincing story.
Why Projects Matter More Than Certificates
A certificate says you attended. A project shows what you can actually do. In UI/UX especially, employers want evidence of:
- Research and problem-framing, not just pretty screens
- A clear process, from user understanding to wireframes to testing
- Decision-making, meaning why you chose a layout, flow, or color
- Polish and consistency across multiple screens
- Collaboration awareness, such as how you'd hand designs to developers
Each project below is chosen to build one or more of these.
The 5 Projects at a Glance
| # | Project | Core Skills Built | Suggested Time |
|---|---|---|---|
| 1 | Redesign an existing app or website | Usability evaluation, problem-framing, before/after thinking | 1 to 2 weeks |
| 2 | Design a mobile app from scratch | Full UX process: research, flows, wireframes, prototype | 3 to 4 weeks |
| 3 | Build a responsive website for a local business | Responsive layout, visual hierarchy, real-client thinking | 2 to 3 weeks |
| 4 | Create a mini design system | Consistency, components, handoff readiness | 1 to 2 weeks |
| 5 | Design a data-heavy dashboard or AI-powered feature | Complex information design, edge cases, modern UX challenges | 2 to 3 weeks |
Project 1: Redesign an Existing App or Website
Why it's first: Redesigns teach you to evaluate before you design. You learn to spot real usability problems instead of changing things for the sake of change.
How to do it:
- Pick a product you actually use, ideally one with obvious friction: a confusing checkout, a cluttered booking flow, a hard-to-find setting
- Audit it honestly. Walk through key tasks, note where you hesitate or get lost, and ask 3 to 5 other people to try the same tasks while you observe
- Define the problem in one sentence, for example: "New users can't find how to reschedule a booking without calling support"
- Sketch and wireframe solutions focused on that problem, not a full visual overhaul
- Design the improved screens and show clear before and after comparisons
- Explain your decisions for every major change
What makes it stand out: A tight story. Reviewers love seeing a specific problem, evidence it was real, and a focused fix. Avoid redesigning everything; depth beats breadth.
Project 2: Design a Mobile App from Scratch (End to End)
Why it matters: This is your flagship case study. It proves you can run the complete UX process, not just decorate screens.
Pick a problem with local relevance. Jaipur offers plenty of authentic ideas:
- A guide app for heritage walks and local tours
- A booking app for handicraft workshops and artisan visits
- A neighborhood food and tiffin ordering app
- A parking or local transport helper for busy market areas
The process to follow:
| Stage | What You Produce |
|---|---|
| Research | 5 to 8 short user interviews or a survey, plus a quick competitor review |
| Define | Problem statement, 2 to 3 user personas, key user goals |
| Ideate | User flows and a feature priority list (what's essential vs. nice to have) |
| Wireframe | Low-fidelity screens for the main flows |
| Prototype | A clickable, high-fidelity Figma prototype |
| Test | Usability tests with 4 to 5 people, with notes on what changed afterward |
| Present | A case study explaining the whole journey |
What makes it stand out: Evidence of iteration. Showing that testing changed your design ("users missed the filter button, so I moved it and made it more prominent") is far more impressive than perfect first-draft screens.
Project 3: Responsive Website for a Local Business
Why it matters: Most junior designers will work on client websites, so this project mirrors real work. It also forces you to think across screen sizes, content constraints, and brand limits.
How to do it:
- Choose a real small business with a weak online presence, such as a boutique hotel, jewelry showroom, textile exporter, café, or coaching center. If possible, talk to the owner to understand goals and audience
- Define what the site must achieve: bookings, inquiries, product browsing, or trust-building
- Create a sitemap and wireframes for mobile first, then desktop
- Design key pages: home, about or story, product or service, and contact
- Pay special attention to hierarchy, spacing, typography, and clear calls to action
- Check accessibility basics: color contrast, readable font sizes, and tap targets
What makes it stand out: Real constraints. Showing how you handled limited photography, long text, or a client's brand colors proves you can design in the real world, not just in ideal conditions. Even if the business never uses it, a "concept redesign" built on genuine research is a strong portfolio piece.
Project 4: Build a Mini Design System
Why it matters: Design systems are now standard in product teams, and students who understand them stand out immediately. This project shows you think in components and consistency, not one-off screens.
What to include:
| Component Area | Examples |
|---|---|
| Foundations | Color palette, type scale, spacing system, grid |
| Core components | Buttons (with states), inputs, cards, navigation, modals |
| Patterns | Forms, empty states, error messages, loading states |
| Documentation | Short usage notes: when to use each component and when not to |
How to do it:
- Reuse the screens from Project 2 or 3 and extract the repeating elements
- Build them as Figma components with variants and auto layout
- Define styles and variables so changing one value updates everywhere
- Document the rules briefly and clearly
What makes it stand out: Careful handling of states (hover, disabled, error, focus) and clear documentation. These are the details developers and design leads care about most.
Project 5: Design a Data-Heavy Dashboard or an AI-Powered Feature
Why it matters: Simple screens are easy. Complex information is where design skill shows. This project pushes you toward harder problems that mirror what many companies now build.
Choose one direction:
- A dashboard for something like sales tracking, student progress, or inventory, where the challenge is making dense data scannable and actionable
- An AI-powered feature, such as a chatbot, a recommendation panel, or a smart search, where the challenge is building trust, handling mistakes, and being transparent about what the AI is doing
What to focus on:
- Information hierarchy. What does the user need to see first, second, and only on demand?
- Edge cases. Empty data, errors, loading, very long values, and wrong results
- Clarity over decoration. Charts and tables should answer questions, not just look busy
- For AI features: show confidence or sources where useful, make it easy to correct or undo, and design graceful responses when the AI can't help
What makes it stand out: Thoughtful handling of the unhappy paths. Most student portfolios only show the perfect scenario; showing what happens when things go wrong signals maturity.
How to Turn Each Project into a Case Study
A beautiful set of screens isn't enough. Structure each project as a short story:
- The problem: who is struggling and why
- Your role and tools: what you personally did, and what you used
- Research: what you learned from real people
- Process: key sketches, flows, and wireframes
- Solution: final screens and prototype link
- Testing and iteration: what changed after feedback
- Outcome and reflection: what worked, what you'd improve
Aim for something a busy recruiter can skim in two minutes but that rewards a deeper read.
Common Mistakes Students Make
- Skipping research. Designing from assumptions produces generic work
- Showing only final screens. Without process, a reviewer can't see how you think
- Copying trending shots. Redrawn Dribbble designs say nothing about your problem-solving
- Ignoring real content. Placeholder text everywhere hides layout problems
- No testing. Even five quick tests make a project far more credible
- Too many mediocre projects. Three to five strong case studies beat ten shallow ones
Tools You'll Use Across These Projects
| Purpose | Common Tools |
|---|---|
| Design and prototyping | Figma, Adobe XD |
| Research and notes | Google Forms, Notion, FigJam |
| Flows and wireframes | Figma, Whimsical, Miro |
| Usability testing | Maze, simple moderated sessions over video call |
| Portfolio hosting | Behance, Notion, or a personal website |
| AI assistance | Used carefully for copy drafts, idea generation, and quick variations, while you keep the design decisions |
Where to Build These Projects in Jaipur
Practice projects work best with feedback from someone who has hired and managed designers. TGC Jaipur's AI-Integrated UI/UX Design Course is built around hands-on, project-based learning with Figma, Adobe XD, and modern AI-powered design workflows. Students work through the full process of research, wireframing, prototyping, and usability testing, so the portfolio you leave with reflects real design practice, not tutorial exercises.
If you want a stronger foundation in layout and front-end basics before or alongside UI/UX, the Web Designing Course covers HTML, CSS, and responsive design, which helps enormously with Project 3. Designers who want to sharpen their visual fundamentals can also explore the Graphic Design Course, and students can browse the full range of programs in the TGC Jaipur course catalog.
Final Thoughts
You don't need dozens of projects to land your first UI/UX role. You need a handful of well-told, well-researched ones: a redesign that shows your eye for problems, a full app that shows your process, a real-world website that shows client thinking, a design system that shows craft, and a complex interface that shows you can handle difficulty.
Start with Project 1 this week. Pick a product that frustrates you, document why, and fix it. Each project you finish makes the next one easier, and by the fifth, you'll have both a portfolio and the confidence to talk about your work like a designer.
Ready to build a job-ready UI/UX portfolio with expert feedback? Explore TGC Jaipur's UI/UX Design course and start working on real projects from day one.


Please select course category