Where this service fits
Mobile design has to work with limited attention as well as limited space. We look at why someone opens the app, what they need to complete and what may interrupt them. That helps us organise onboarding, navigation and the key actions around a useful sequence, rather than asking users to learn the entire product at once.
We design the journey through flows and prototypes before refining the interface. Touch targets, readable content, keyboard behaviour and the states around each action matter to the final experience. We consider permissions, slow connections and the path back into an unfinished task. The result should be understandable both to the person using it and the developer implementing it.
What the work can include
We agree the deliverables around your product and existing setup. A focused engagement can include the following work.
- Mobile journey mapping and navigation structure
- Onboarding and key-screen prototypes
- Interface states and responsive device behaviour
- Development specifications and implementation review
Planning your project
Existing support questions, usage patterns and user feedback can help identify the journey to improve. For a new app, we agree assumptions and focus on a small set of important tasks. Research with participants, additional device classes and extensive design systems are scoped according to the product’s needs.
The estimate should identify the work, assumptions and responsibilities on both sides. We can shape a first phase around the highest-priority outcome, with additional work planned separately once the relevant decisions have been made.
Share your starting pointPrepare for real devices and a real release
Testing needs to reflect how mobile products are used. We agree a device and operating-system matrix, check the important flows and consider permissions, backgrounding, poor connectivity and expired sessions. Purchase-related work also needs attention to subscription status, restored access and the difference between the development and production environments.
Release preparation can include build configuration, signing, store-listing assets and submission support. Review decisions remain with the platform, so the schedule should allow room for feedback and any required changes. We also agree who maintains the app after launch and how future operating-system updates, dependency changes and product improvements will be handled.
How delivery works
Understand the work
We start with your users, business model and current constraints. Bring an idea, a running product or a workflow that causes friction. Together we identify what needs to change and what a useful first outcome looks like.
Shape a practical scope
We connect the user journey to the design, engineering and operational work it needs. Assumptions, dependencies and responsibilities are discussed early, so you can make informed decisions about the first release and the work that follows.
Build with visible progress
Designs, prototypes and working features give us something concrete to discuss. We review progress with you, resolve questions as they arise and test the important journeys. Changes to priorities are considered against the agreed scope.
Launch and keep improving
Release preparation includes the agreed testing, deployment and handover. We make support responsibilities clear and can continue as your product team, improving the experience as you learn from real use and plan the next release.
Coach Phil brings fitness goals, meals and workouts into a subscription app, with a separate admin workspace for managing the coaching experience. See both sides of the product.
Explore related workFrequently asked questions
Can you improve our app’s onboarding without redesigning everything?
Yes. A focused engagement can cover the entry journey, account setup and first useful action. We review the surrounding navigation and dependencies so the improvement works within the existing app.
Can this be a focused engagement within our existing product?
Yes. We can scope this work around an existing product after reviewing the relevant design, code or operating setup. We identify the dependencies and agree what is included, who provides access and how the change will be reviewed. If another part of the product also needs work, we explain that before expanding the scope.