Mobile & Interface

We build apps and interfaces around what people need to do.

From a mobile app to a dashboard or the interface for a connected device, we design and build the parts of a product people interact with. We start with their situation: what they need to understand, what they need to do, and what would make that easier.

Discuss your project See how we approach it

Bring an idea, a prototype, or an existing experience you want to improve.

What should someone be able to do?

Someone might be recording work in the field, checking equipment, finding information or completing a purchase. Each situation calls for different information, controls and feedback. The experience should follow that use, rather than start with a list of screens.

Consider both the person using the product for the first time and the person returning to it every day. What needs explaining? What should be quick? Where could someone lose their place or make a mistake?

The people: Who is using it, and what are they trying to accomplish?
The task: What information and actions help them move forward?
The context: Where, when and on which device will they use it?

The screen is part of a wider experience.

An interface connects a person to the rest of the product. A button may change a device setting, save work for a team or request information from a service. What happens behind the screen needs to match what the screen tells someone has happened.

We consider the journey, interface and application together. Not every project needs a mobile app, a web dashboard and a device interface. The right combination depends on who needs access and what they need to do.

Journeys and interaction: Connect the steps someone takes, from their first visit to the work they return to.
Interface design: Give information, navigation and controls a clear place, with consistent behavior across screens.
Application software: Build the screens and behavior that turn the design into a working product.
Connections and data: Connect the interface to accounts, services or devices and make the state of that connection clear.
Feedback and refinement: Use observation, feedback and relevant measurements to decide what needs to change.

How we make product decisions

Human input gives the work a purpose. Data helps test whether an experience supports that purpose. AI can assist exploration and execution, with people reviewing the work and making the decisions.

Make the next action understandable.

Clear language, hierarchy and feedback help someone know where they are, what they can do and what happened. Loading, empty and error states need as much thought as the screen with everything filled in.

Test the flow before adding more features.

A prototype can help reveal unclear steps and missing information before they become application code. Feedback from the people doing the task gives the design something concrete to respond to.

Measure what helps you improve the experience.

Start with a question: where do people get stuck, repeat a step or abandon a task? Choose measurements that help answer it, alongside direct feedback. More taps or more time in an app do not automatically mean it is more useful.

Give AI a specific role.

AI can help explore alternatives, draft work or examine feedback. Adding AI to the product is a separate choice: it needs a useful job, clear limits and a way for people to understand and correct its output. An interface does not need an AI feature to be valuable.

Design for the conditions of everyday use.

A flow that works in a demonstration still has to work with interruptions, different abilities, incomplete information and the devices people actually have. These questions belong in the brief:

Where will people use it?: Consider the device, screen size, available attention and the setting in which the work happens.
What happens with a slow or missing connection?: Decide what can remain available, how pending work is shown and what happens when a connection returns.
Who can see and change what?: Define accounts, roles, permissions and the information each person needs.
What makes the interface accessible?: Consider readable text, contrast, touch targets, keyboard use, assistive technology and reduced motion.
How will the product reach people and evolve?: Agree on distribution, platform requirements, testing, updates and maintenance responsibilities.

Platform coverage, offline behavior, accessibility requirements and ongoing support are defined for the project. They are decisions to resolve, rather than assumptions to leave until release.

Choose the technology around the experience.

Flutter is one of the tools we work with. A mobile app, a browser interface and a device companion can have different requirements. We choose the implementation for each surface, with shared design patterns and service connections where they help.

Mobile applications: Flutter and Dart for iOS and Android applications, with platform-specific integrations where needed.
Web interfaces: React and Next.js for browser-based product interfaces, dashboards and tools.
Device and platform integration: Connections to device data and services; Swift, Kotlin or native libraries where the application needs platform capabilities.
Interface systems: Reusable components, navigation patterns and purposeful motion that support a consistent experience.
Testing and delivery: Checks for application behavior and release workflows suited to the agreed platforms and distribution channels.

Tell us what people need to do.

Describe who will use the product, the task it should support and what you already have. Include any existing designs, systems or devices it needs to work with, and where the current experience falls short.

Discuss your project