Visual priority
The heading, essential information, and primary action should be distinguishable without every element competing constantly for attention.
FARCOM / CLARITY BY DESIGN
UI/UX design—
a clear experience
with your brand’s character.
For your website, ecommerce experience, or software, we design a clear path to completing the task and an interface shaped around its users—from current-product review and wireframes to mobile UI, clickable prototypes, and developer handoff.
Design thinking,
alongside building experience.
15+years of FARCOM
150+successful projects
Explore FARCOM’s work ↗01 / LESS FRICTION, MORE CLARITY
See design through one simple choice.
From understanding the problem to wireframes and a clickable prototype, explore three layers of a sample scenario. The right outcome is something tested with users, not merely something that looks polished in an image.
DESIGN STUDY / 01
The user arrived to complete one task.
In this sample, the user wants to choose a meeting time. Showing every piece of information at once makes the primary decision harder. The design hypothesis is to move secondary details to the stage where they become useful.
F / APPOINTMENTSAMPLE PROTOTYPE · NOT A REAL BOOKING
Several competing decisions on one screen.
Meet the teamService listMeeting typeContact detailsChoose a timeEngagement termsMeeting historyNewsletter
User goal: choose a meeting time02 / EVERY DETAIL HAS A JOB
Small details;
an effect across the experience.
Every screen needs a clear purpose. We review interface, behavior, and content together so users find the answer they need at the moment of decision.
Real interface states
Interfaces are not designed only for complete data. Errors, empty results, waiting, and success also need a clear message and next step.
Different ways of using the product
Readability, contrast, keyboard navigation, and presentation across screen sizes are part of the design review.
A coherent identity
Color, type, imagery, and motion should serve the brand’s character and maintain a shared language across pages and devices.
03 / FROM INSIGHT TO HANDOFF
Design outputs should be usable by the team.
The engagement may cover one critical flow, a product redesign, or a complete design system. We define the outputs and level of detail for every stage before work begins.
01
Understanding and priorities
Review business goals, users, and constraints. The research approach is selected around access to users, available data, and project scope.
- Problem definition
- Hypotheses
- Priorities
02
Structure and flows
Clarify information architecture, primary journeys, and exceptions before visual design—from starting a task to its result and error recovery.
- Content map
- User flow
- Wireframes
03
Interface and design system
Define color, type, spacing, and components in one visual language, including active, error, empty, and loading states.
- Responsive UI
- Components
- States
04
Testing and handoff
Review an interactive prototype against defined scenarios. Document improvements and component behavior for continued development.
- Prototype
- Findings
- Documentation
04 / DESIGN IN CONTEXT
There is no single visual language;
every brand has its own expression.
In a catalog, imagery and product discovery lead. In an operational dashboard, information clarity and work status matter most. We shape structure, content density, and interface behavior around what the audience needs to do.
Explore all work →
05 / DESIGN AND ENGINEERING, TOGETHER
The gap between design and build
is reduced from the beginning.
Technical constraints, real content, and component behavior are reviewed throughout design. Collaboration can continue with your development team, or FARCOM can provide both design and implementation.
Explore web application development ↗- 01
Begin with a defined problem
Review the product objective, users, priority flow, and constraints together.
- 02
Prototype before full development
Make critical decisions reviewable through wireframes and an interactive prototype.
- 03
Create buildable specifications
Define components, states, responsive behavior, and interaction details for implementation.
- 04
Review the implemented product
When included in scope, compare the real implementation with the design and primary scenarios.
A closer look at interface and user-experience design
Explore UI and UX, redesign, and cost
What is the difference between UI and UX?
User experience concerns goals, structure, and the path to completing a task. User interface makes that logic usable through content, layout, and element behavior. The two should develop together with technical constraints and brand identity in view.
Where should a redesign begin?
Begin with an observable problem: a lost journey, repeated errors, unclear content, or interface inconsistency. When available, behavioral data and user conversations help prioritize the work. A complete visual overhaul is not always the first answer.
How are scope and cost determined?
The number and complexity of flows, user roles, research depth, existing-content readiness, and documentation needs all affect scope. Page count alone is not enough; error states, mobile behavior, and interactions also need definition.
How do we evaluate the design result?
Test scenarios, target users, and measures such as task completion, errors, and need for guidance are defined before evaluation. Without data and testing, we do not promise a conversion increase or shorter task time.
What information is needed to begin?
Describe the current product or initial idea, user groups, their most important task, and any time or technology constraints. Brand guidelines, sample content, and anonymized user feedback also help. When data or interviews are unavailable, we record the hypotheses and research limitations from the beginning.
What does design handoff include?
Editable files, agreed flows, target-screen designs, reusable components, and error and loading states are defined in the delivery scope. Review rounds, font and image licences, and support for the development team should also be clear. Design handoff alone does not mean delivery of an implemented website or application.
BEFORE WE DESIGN
Questions to answer before design begins.
F / CLARITYCLEAR THINKING.
CONFIDENT DECISIONS.
CONFIDENT DECISIONS.
Clarify the path before we begin.
Prepare your project brief ↗Is UI/UX design available without development?
Yes. The scope can cover research and experience architecture through prototyping and a design system, while FARCOM can also provide technical implementation.
How do we know the design can be built?
Designers and engineers work together from the early stages, with technical constraints, real content, and interface states considered throughout design.
How do you redesign an existing product?
We analyze current behavior, friction points, and product constraints, then prioritize changes and implement them incrementally when appropriate.
What affects UI/UX design time and cost?
The number of flows and roles, research depth, target screen sizes, interface states, and required documentation affect the estimate. Page count alone is not enough; each stage’s outputs and review rounds are also defined before work begins.
Will we receive editable design files?
Editable files, components, prototypes, and specifications required for development are listed in the project agreement. Font, image, and other third-party asset licences are reviewed separately.
What if we cannot access real users?
We can begin by reviewing the existing product, available data, and team knowledge, but assumptions do not replace observing users. Research limitations are recorded, with opportunities for later testing included in the ongoing plan.
LET’S MAKE THE NEXT STEP CLEAR
Where do your users
need a clearer path?
Tell us about the current product or the initial idea.
Together, we’ll define the right place to begin.