Customer service and bookings
Let customers request a service, manage appointments or check progress, with accounts and notifications where they are part of the agreed scope.
S05 / MOBILE APPLICATIONS
Plan a mobile experience around the task, the people using it and the devices they rely on. We agree the platforms, development approach and back-end needs before work begins.
Put the right tools in your customers’ and team’s hands.
Discuss your project
Bespoke scope, pricing and delivery. Speak to customer support for an assessment.
POSSIBLE USE CASES
A clear reason to open the app.
These are examples to discuss, rather than a fixed package. The features and deliverables depend on your project.
Membership and repeat visits
Create a mobile home for member content, account details or loyalty features, connected to the systems your business already uses.
Field teams and site visits
Help staff view jobs, complete checklists or capture photos on location. Discuss offline use and synchronisation if connectivity is a concern.
A mobile companion to your product
Extend an existing web application with a focused mobile experience, using agreed APIs and consistent account permissions.
DEFINE THE WORK
Agree the details before development.
Platforms and experience
Agree whether the project targets iOS, Android or both, the device features required and whether a native or cross-platform approach suits the work.
Accounts, data and device features
Scope sign-in, APIs, data storage and any camera, location, notification or offline requirements. Confirm permissions and third-party costs during discovery.
Testing and release responsibilities
Agree supported devices, test builds, acceptance checks, store account ownership and submission responsibilities. Store reviews are handled by the platforms and their timing is outside the project’s control.
PROJECT DELIVERY
A clear process, shaped to the project.
- 01
Discuss and assess
Tell customer support about the users, current systems, required features and preferred timing. We assess feasibility and agree any discovery work and its cost first.
- 02
Agree the project
Confirm the scope, price, payment stages, milestones, dependencies, revisions, acceptance checks and handover arrangements in writing before development starts.
- 03
Build and review
Develop the agreed work, review it at the planned stages and assess changes to scope, cost or timing before additional work proceeds.
- 04
Accept and hand over
Complete the agreed acceptance checks and release or migration steps. Provide the agreed code and documentation, and arrange ongoing support if required.
COMMON QUESTIONS
Before we begin.
Can the project cover both iOS and Android?+
It can be scoped for one platform or both. We review the audience, device features, budget and maintenance needs before recommending an approach and agreeing which platforms and versions will be supported.
Are app store publication and ongoing updates included?+
They are included only where agreed in the project scope. We confirm responsibility for developer accounts, store submissions, review responses, platform fees and future updates. Approval and review timing remain with the app stores.
What does a mobile app cost and how long does it take?+
Pricing and delivery are bespoke. Contact customer support with the main user journeys, target platforms, integrations and preferred timing. We agree the scope, quote and delivery arrangements in writing; the standard website subscription delivery provisions do not apply.
LET’S DISCUSS IT
Start with the problem you want to solve.
Share the main users, features, existing systems and any preferred timing or budget. Customer support will help clarify the assessment and next steps before a project scope and quote are agreed.