Apps and websites that feel obvious to use, designed in Figma and tested with real people before a line of code.
01 In short
ELVN designs the UI and UX of websites, mobile apps and web products: user flows, wireframes, interface design, prototypes and a design system in Figma, tested with real users before development. We don’t build apps ourselves; your developers get a clean hand-over with every screen, state and component they need.
- Best for
- Apps, web products, platforms and websites
- Timeline
- Set by the scope, with the quote
- You get
- Flows, screens, prototype and design system
- Hand-over
- Figma, ready for developers
02 Why UI/UX
- 01
Flows before screens
We map how people move through the product first: what they want, every step, every decision and every dead end. Fixing a flow on paper costs minutes; fixing it in code costs weeks.
- 02
From wireframe to interface
Wireframes settle the layout and the content, then the interface brings in your brand, type, colour and motion. Each step is reviewed, so the final design has no surprises.
- 03
Tested with real people
A clickable prototype is put in front of real users with real tasks. Where they hesitate, misread or get stuck, we change the design, before your developers start.
- 04
A hand-over developers love
Every screen comes with its states, spacing and components, built on a design system in Figma. Developers build from it without guessing, and new screens later reuse the same parts, as on the Day & Night Dubai city platform.
03 What’s included
- 01
Research
Interviews, competitors, analytics and the jobs people come to the product to do.
- 02
User flows and wireframes
Every path through the product, then the layout and content of each screen.
- 03
Interface design
Every screen and state, for phone and desktop, in your brand.
- 04
Prototype and testing
A clickable prototype tested with real users, and the design fixed where they struggled.
- 05
Design system
Colours, type, spacing and components in Figma, documented for your team.
- 06
Developer hand-over
Specs, assets and a walkthrough, and answers to developers’ questions during the build.
04 What we use and why
Figma
Flows, wireframes, interface, prototype, design system and developer hand-over, all in one file.
Framer
When the website is the product, we design and build it in Framer, with real motion.
Photoshop
For product imagery, mockups and the visuals inside the interface.
05 UX or UI?
Two halves of one job. We do both, in this order.
| UX | UI | |
|---|---|---|
| Answers | Does it work, and is it easy? | Does it look and feel right? |
| Made of | Research, flows, wireframes, testing | Screens, type, colour, components, motion |
| Mistakes cost | Lost users and rebuilds | Lost trust and a dated look |
The look of the product starts from the brand: see brand identity.
06 How it works
01Step 1
Research and flows
Who uses the product, what they need, and every path through it.
02Step 2
Wireframes
The layout and content of each screen, reviewed with you.
03Step 3
Interface and prototype
The final design, clickable, and tested with real users.
04Hand-over
Ready to build
Design system, specs and a walkthrough for your developers.
07 Questions
No. We design it, and your developers build it from a clean Figma hand-over with a design system. For websites, we design and build.
It depends on the number of flows and screens. A few screens take days, a whole app takes weeks. You get a timeline with the quote.
Yes. We start with what users struggle with today, from analytics, support questions and tests, and fix that first.
Yes. Contrast, text size, tap targets and clear states are checked as we design, so the product works for more people.
Yes. Once the project is paid, all rights in the final work are yours, with the Figma files.
Let’s design something people get.
Book 30 minutes. We look at your numbers and tell you what we would do first. No pitch deck.
Book a call