User research
Interviews, surveys or observation with real participants, and what you concluded from them.
UI/UX FYP Design Support
UI/UX Design Final Year Projects With a Defensible Process
A design Final Year Project is judged on process, not on how many screens you produced. We build the research, the personas, the wireframes, the prototype and the design system — and hand you a Figma file and specifications a developer can build from, including your own project.
UI/UX FYP Design Support
What a UI/UX Final Year Project Should Show
The strongest design projects in a computer science department demonstrate a loop: research, design, test, refine. A moodboard and six polished screens demonstrate none of it. We build the loop so each decision can be defended.
Personas and journeys
Derived from the research rather than invented to fit the screens you already drew.
Information architecture
Sitemaps, card sorting or tree testing before any high-fidelity screen.
Wireframes to prototype
A low-fidelity pass that shows you changed your mind for a reason.
Usability testing
Five or more people on the prototype, with what broke and what you changed.
A real design system
Tokens, components and states — so the interface scales beyond the demo.
UI/UX FYP Design Support
Design Project Ideas With Enough Depth
Each of these has a real research question behind it, which is what separates a design project from a set of rectangles.
Redesign of a university service
Research the current process, prototype an alternative and measure the difference.
Accessibility-first interface
Redesign a common journey for users with low vision, motor or cognitive constraints.
Public transport or wayfinding
Wayfinding and information hierarchy for a station, campus or transit app.
Healthcare patient journey
Appointment, preparation, visit and follow-up designed around patient anxiety.
Financial or budgeting app
Trust, clarity and error prevention in a domain where mistakes are expensive.
Rural or low-connectivity service
Design for intermittent connectivity and low-end devices.
UI/UX FYP Design Support
What You Receive
Everything is handed over in Figma and in writing, so your report and your implementation can both point at the same source of truth.
- Figma file with components, variants and auto-layout
- Design tokens for colour, type, spacing and elevation
- Clickable prototype covering the core flows
- Usability test findings and the changes they caused
- Developer handoff with specs and asset exports
- A written rationale you can adapt for your report
Related
Other Student Project Specialisms
Each of these covers a genuinely different stack and a different set of exam questions.
Questions
Frequently Asked Questions
The questions students ask most about this kind of project. If yours is not here, the free consultation is the fastest way to get it answered.
Ask us directlyNo. You will need to understand the decisions in your submission, but you do not need to arrive with a design background. We explain the reasoning as we build.
Yes — components, variants, auto-layout, tokens and named layers, plus a handoff document with measurements, states and asset exports.
Often that is the most useful arrangement: we audit what exists, design the missing flows, and give you the tokens and components so the code and the design stop disagreeing.
Absolutely, and that is the normal arrangement. You keep the implementation, which is the part you are being assessed on, and we hand over everything needed to build it.
Want an honest answer about your project?
Book a free 30-minute consultation and get professional technical guidance on scope, architecture and what is realistic in your timeline. No obligation, and we will tell you if your project does not need us.
Students remain responsible for understanding, presenting and submitting their academic work according to their institution's policies.