Mobile app development

An experience designed for a phone

We define priority tasks, frequency of use and network conditions. A repeated action in the field needs a different interface from an occasional information lookup.

A prototype helps validate navigation, comprehension and information density before feature development. Permissions and interruptions belong in that discussion too.

Choose technology after defining the need

The choice between native development, a cross-platform approach and a mobile web application depends on required capabilities and the team maintaining the product. We examine integrations rather than deciding solely from the number of platforms.

• iOS and Android journeys and interface components.
• Accounts, synchronisation and backend connections.
• Assessment of offline use, notifications and device capabilities.
• Testing on devices and versions agreed during discovery.
• Preparation of release materials and account access.

Plan distribution from the start

Distribution accounts, content, privacy information and third-party access need early attention. We establish who provides and approves each item.

Technical preparation does not guarantee acceptance by an app store. Applicable requirements are checked at release time, and the schedule needs room for potential adjustments.

Plan for life after launch

Launch begins a period of monitoring, fixes, user feedback and compatibility work as platforms evolve. Maintenance scope should be separate from the initial build.

To get started, describe the tasks people need to perform on a phone, your audience, target devices and existing services. That information makes it possible to compare approaches.

Before we start