The problem it solves
Confusing navigation, unclear buttons or a long form stop the user — and that often shows only after launch, in lost enquiries. A prototype lets us notice and fix those problems before development, while changes are cheap.
Who it is for
New digital product teams, startups, businesses improving an existing website or app, and development teams that need finished, structured design.
UX: structure and user journey
UX work begins before any interface is drawn. We establish who the user is, what task they arrive with and which steps lead to the goal. We create a page map, an information hierarchy and wireframes — black-and-white layouts where logic is agreed first, not colours. Most questions surface at this stage: where the price goes, how many fields a form needs, what a visitor sees on the first screen.
UI: visual system and components
In the UI stage the wireframes take on the brand style: colours, typography (including the specifics of Georgian type), buttons, form fields, cards and their states — default, hover, active, disabled, error. Components are built as a system in Figma so adding a page never starts from zero and developers have exact, repeatable rules.
Interactive prototype
A Figma prototype shows screens and transitions on a real device — tapping a button moves to the next screen as if the product already existed. That lets you decide on something tangible, show the team or an investor, and test with users before development starts.
Handoff to developers
Design is finished when it can be implemented exactly. We prepare structured files: a component library, sizes and spacing, colour and type variables, mobile and desktop versions of every screen, exported icons and images. When we build the project ourselves (website or app), this stage continues seamlessly.
What the service includes
- User journeys, page map and information structure
- Wireframes and their approval
- Visual style: colours, typography, components and states
- Mobile and desktop versions of every screen
- Interactive Figma prototype for review and testing
- Basic accessibility rules: contrast, sizes, readability
- Design system and structured developer handoff
- An agreed number of revision rounds
How we work
1. Discover
Define the goal, audience and essential functions.
2. Design
Agree on structure, visual direction and user journeys.
3. Build
Develop and test the agreed functionality.
4. Launch
Prepare publication, access and ongoing maintenance.
Choosing the technology
The final technology is selected after reviewing your requirements. These are possible directions.
What affects the timeline
The number of screens, edge states (empty lists, errors, loading), research scope and testing needs define the timeline. Feedback speed in each round directly affects it.
What affects the price
The cost depends on the number of screens and scenarios, the scale of the design system, research and the agreed revision scope. In a website or app project, design is usually part of the overall price; a standalone design project is estimated after a short discussion. See the pricing page.
Pricing ↗Support after launch
As the product evolves, so does the design system — new screens and components are added under the same rules, optionally as an ongoing collaboration.
Why webandapp
We document the task, agree on stages and define the deliverables before development. You can see what is included and what needs a separate decision.
FAQ
What is the difference between UI and UX?
UX covers how a task is completed — structure, steps, logic. UI is the visible interface and its components — colours, type, buttons. Both must work together.
Is a prototype a working app?
No. It shows screens and transitions on a real device; server functions, login and data need separate development.
Will you use our existing brand style?
Yes. Provide your logo, colours, fonts and existing rules. If you have no brand style, we create a basic visual system within the project.
Is mobile design included?
Yes — screen sizes and their states are written into the scope. For a website the mobile version is essential and often where we start.
Will I receive the files?
Yes. Deliverables and usage rights are defined in advance. The Figma file is handed over in a structured form to you or your developer.