Design decides whether software gets used. We work out the screens and the flow between them with you, and agree them before anyone writes the code that builds them.
What we do
Work out what each screen has to do, and for whom
Design the flow: what a user sees first, next and last
Design the screens themselves, and review them with you before development starts
Change them while changing them is still cheap
Hand the design to the developers who build it, and stay available while they do
Who it's for
Companies building something new, and companies whose existing software works but is hard enough to use that people avoid it or make mistakes in it.
Frequently asked questions
What is the difference between UI and UX design?
UX is the flow: what a user sees first, next and last, and what each screen is for. UI is the screens themselves. We design both.
Why design before writing code?
Because changing a design is cheap and changing built software is not. We agree the screens with you before development starts.
Do we review the designs?
Yes. We review the screens with you and change them while that is still easy.
Our software works but people avoid it. Can design help?
Yes. Software that is hard enough to use that people avoid it or make mistakes in it is one of the cases we work on.
What happens to the design after you finish?
We hand it to the developers who build it and stay available to them while they do.
FlowricaUsually replies instantly
Flowrica can make mistakes. Check important replies.
We’d like to use Google Analytics to see how this site is used. Nothing is set unless you accept.