UI/UX design that looks right and works right
Gjethe designs interfaces for websites, web applications and mobile apps: user research, user flows, wireframes, high-fidelity Figma designs, clickable prototypes, usability testing, design systems and developer-ready handoff. Pricing is based on your project and agreed in your quote.
- Free first consultation
- Written quote for your project
- Flexible payment milestones
At a glance
- Covers
- Research, flows, wireframes, UI, prototypes
- Tool
- Figma
- Handoff
- Specs, components, tokens
- Pricing
- Quoted per project
Definition
What is UI/UX design?
UI/UX design is the practice of designing digital products so they are easy and pleasant to use. UX (user experience) design covers structure, flows and usability; UI (user interface) design covers the visual layer, layout, typography, colour and components.
A beautiful interface that confuses people loses money, and a functional one that looks untrustworthy loses it too. Good product design does both jobs: it makes the next step obvious and makes the product feel credible. We start from what users are trying to do, design the structure before the visuals, and test with real people before anything is built, because changing a prototype is far cheaper than changing code. Designs are handed over with components, states and notes that developers can build from without guessing.
Who is it for?
Startups before development
Validate flows and look with a prototype before spending on code.
SaaS products
Dashboards, onboarding and settings that users understand without support.
Mobile apps
iOS and Android interfaces that follow platform conventions.
Products that need a redesign
Existing interfaces with usability problems or an outdated look.
What's included, and what you keep
What's included
- Stakeholder and user research
- Competitor and pattern review
- User personas and jobs to be done
- Information architecture
- User flows
- Low-fidelity wireframes
- High-fidelity UI design
- Clickable prototypes
- Usability testing
- Accessibility review
- Design system and components
- Developer handoff
What you receive
Handed over at the end. Yours to keep.
- Research summary
- User flows and wireframes
- Final Figma designs for every screen and state
- Interactive prototype
- Component library and handoff specs
UX versus UI
| UX design | UI design | |
|---|---|---|
| Question it answers | Can people achieve their goal easily? | Does it look clear, consistent and trustworthy? |
| Work involved | Research, flows, structure, wireframes, testing | Layout, typography, colour, components, states |
| Output | Flows, wireframes, prototypes | High-fidelity screens and design system |
| Failure looks like | Users get lost or give up | The product feels cheap, inconsistent or hard to read |
Why we wireframe before visual design
Wireframes are simple grey layouts that show what goes on each screen and how screens connect. They let everyone focus on structure (what information appears, in what order, and what the user does next) without debating colours or fonts.
Fixing a confusing flow at wireframe stage takes minutes. Fixing it after visual design takes hours, and after development it can take days. That's why we get wireframes approved before any high-fidelity work starts.
Testing with real users
Designers and stakeholders know the product too well to see its problems. A handful of usability sessions, people outside your team trying to complete real tasks on the prototype, reveals most of the major issues quickly.
We write task scenarios, run moderated or unmoderated tests, and turn what we observe into specific design changes. The findings are shared with you as short clips and a prioritised list, so decisions rest on evidence rather than opinion.
Accessibility built in
Accessible design is better design for everyone.
- Colour contrast that meets WCAG AA
- Readable type sizes and line lengths
- Touch targets large enough for fingers
- Clear focus states for keyboard users
- Labels and error messages that explain what to do
- No information conveyed by colour alone
A handoff developers can build from
Designs are only useful if they're built as intended. We organise Figma files with named components, auto-layout, defined spacing and colour tokens, and design every state: empty, loading, error, hover, disabled, success.
Developers get annotated flows, responsive behaviour for each breakpoint and exportable assets. We stay available during development to answer questions and review the build against the designs.
Designing onboarding that keeps users
Many products lose most new users before they see any value. Onboarding design focuses on the shortest path to that first useful moment: fewer fields at sign-up, sensible defaults, sample data instead of empty screens, and guidance that appears when it's needed rather than as a long tour.
We map the onboarding journey with you, identify where users drop off in your analytics, and design and test changes that get people to value faster.
How UI/UX design works, step by step
Every step has a clear output you can review. Timing is agreed in your quote.
- 1
Discover
Goals, users, constraints and competitors researched.
- 2
Structure
Information architecture and user flows mapped.
- 3
Wireframe
Low-fidelity layouts for every key screen, approved before visuals.
- 4
Design
High-fidelity UI in your brand, with all states.
- 5
Prototype and test
Clickable prototype tested with real users; issues fixed.
- 6
Hand off
Developer-ready files, components and support during build.
Tools, and what shapes your quote
Pricing is based on your project and agreed in your quote. These are the things that move it.
| Factor | Why it matters |
|---|---|
| Number of screens | More screens and states take more design time. |
| Research depth | User interviews and testing rounds add time and insight. |
| Platforms | Designing for web, iOS and Android separately adds work. |
| Design system | A full component library takes longer than page designs alone. |
| Brand readiness | Without existing brand guidelines, visual direction needs defining first. |
| Interaction complexity | Advanced animations and custom interactions add prototyping work. |
| Area | Tools |
|---|---|
| Design | Figma, FigJam |
| Prototyping | Figma prototypes, ProtoPie for advanced interactions |
| Research and testing | Maze, Hotjar, moderated video sessions |
| Assets | Adobe Illustrator, Adobe Photoshop |
Common mistakes to avoid
What we see go wrong most often, and how a good project avoids it.
Designing visuals first
Without agreed structure, visual designs get redone repeatedly.
Skipping user testing
Your team isn't your user. Test with people who don't know the product.
Forgetting edge states
Empty, error and loading screens are where products feel broken.
Ignoring platform conventions
Users expect iOS and Android apps to behave like their platform.
Handing off unorganised files
Messy Figma files lead to inconsistent builds.
Frequently asked questions
Do you design in Figma?
Yes. Figma is our primary tool, and you get full access to the files.
Can you design an app that someone else will build?
Yes. We produce developer-ready designs and specs, and can work alongside your developers during the build.
Can you also build what you design?
Yes. Our development team can build websites, web apps and mobile apps from the designs, which keeps design and build closely aligned.
How do revisions work?
Two rounds of revisions are included at each major stage, wireframes and visual design, so feedback is handled when it's cheapest to change.
Do you do user research?
Yes, scaled to the project: from a review of analytics and competitors to user interviews and moderated usability tests.
Can you redesign our existing product?
Yes. We start with a UX audit of the current product, identify the biggest problems and redesign step by step if needed.
Do you create design systems?
Yes. A design system of reusable components and tokens keeps products consistent and makes future design and development faster.
Do I own the designs?
Yes. Once the project is paid, all designs and Figma files are yours.
Is accessibility included?
Yes. We design to WCAG AA contrast and usability guidelines by default and flag anything that needs development attention.
What do you need from us to start?
Your goals, target users, any existing brand assets, analytics or research, and access to the current product if there is one.
Can you design dashboards with lots of data?
Yes. Data-heavy dashboards need careful hierarchy, filtering and chart choices; it's a common part of our SaaS work.
Can you design for both iOS and Android?
Yes. We design a shared product structure and adapt navigation, controls and patterns to each platform's conventions where it matters.
Related services
Figma Design & Design Systems
Components, variables and libraries your team can scale.
Web Applications & SaaS
Portals, dashboards and subscription products.
Mobile App Development
iOS and Android apps, from design to store launch.
Website Redesign
Rebuild an outdated site without losing traffic.
Brand Identity Design
Logo, colour, type and guidelines as one system.
Conversion Rate Optimization
Research and A/B tests that lift conversions.
UI/UX Design by industry
Design your product properly.
Tell us what you need. You get an honest assessment, a clear plan and a written quote. The first consultation is always free.
- What happens next
- 1You tell us what you need
- 2We aim to reply within 24 hours with questions
- 3You get a written quote for your project