Apps and services people understand first time.
We design how apps, software products and internal tools work: the steps people follow and the screens they use every day. Rron Imami, Co-founder and Creative Director, leads it. He maps the tasks people do most, simplifies them, tests clickable prototypes with your users, and then draws every screen your developers need, including the empty, error and loading states, so nothing is left for them to guess.
Who it is for
For founders, product owners and operations leads with software people use every day. Usually one of these is true:
- You are building the first version of a product and want the flows settled before the developers start.
- People struggle with your software, and your support inbox shows it.
- Your staff keep their own spreadsheets because the internal tool is harder to use.
- You are adding a large feature and want it to feel like part of the product from the first day.
It also suits growing businesses whose customers log in to something: a booking area, a client portal, an order tracker.
What you get
The tasks people do most, mapped step by step and simplified
Clickable prototypes to try with your users before anything is built, so the big questions are settled while they are cheap to change.
Screen designs ready for your developers, with the empty, error and loading states drawn, including what people see before there is any data.
A review of a product you already have, with the fixes in order of importance, if you are not ready for a redesign.
A design system, where it helps: one shared kit of type, colour and components that matches your brand identity.
Every file we make, including the design source files. Nothing is locked to us.
How it runs
A call with Rron about what the product does, who uses it, and where they get stuck.
A written scope before any work starts, naming what we will design, who will design it and the dates.
Mapping. We go through the main tasks with you, and with your support inbox or your users if you can share them.
Prototypes and testing. Clickable versions of the key flows, tried with your users before any code is written.
Screen design. Every screen in the agreed flows, with its states, drawn for the devices people use.
Handover to your developers, with a weekly look at real progress throughout.
A review of an existing product fits a sprint: a fixed piece of work over a few weeks with one named outcome. A new product, or a large feature, runs as a project in milestones. More on how a project runs.
What to bring
- The product, or a demo or test account, if it exists. Please do not send passwords by email; we will arrange access on the call.
- Who uses it, and the two or three things they do most.
- Complaints and questions from your support inbox, even a rough sample.
- What your developers build with, and any design kit they already use.
- Any fixed date, such as a launch or a funding milestone.
An example
As founding designer at a B2B software start-up, Rron designed the product's UX from the first sketch, from its flows to its campaign dashboard. That included the first-run screen, a short set-up card that ticks off each step as the user finishes it, and the page where users teach the app about what they sell. He also made the founding brand and the marketing site's information architecture, SEO and front end. The lead developer owns the back end, and the start-up owns the brand and the product. It is not presented as a Giant Entity project, and the screens on our work page use invented sample data.
When the screens sit on top of your records
Internal tools are only as good as the data behind them. If the tool you need is really a better way to keep your records, Dorotea, who leads our workflow and automation work, can set up the databases and operations side while Rron designs the screens your team will use. If you need a marketing site for the product too, see website design and build.
Questions
What is the difference between UX and UI design?
UX design is how the product works: the steps someone takes to get a task done, and what happens at each one. UI design is how each screen looks and reads. We do both, so the flows and the screens are designed together.
Can you review an app we already have?
Yes. We review the product as your users meet it and give you the fixes in order of importance. You can hand those to your developers, or ask us to design the changes.
Do you build the app as well?
Not the code of a software product: we design it and your developers build it, working from screen designs that cover every state. For internal tools where you have no developers, the workflow and automation side of the studio can build one in the tools you already use.
Do you test designs with real users?
Yes. We test clickable prototypes with people who use, or will use, the product, before anything is built.
Can you work with our existing brand?
Yes. We design the screens in your brand and, where it helps, turn it into a design system your developers can build from. If the brand itself needs work, that can sit in the same scope.
Book a call
The call is with Rron Imami. Bring the product, or just the list of things your users keep asking about.
Not sure which? Plan your project