Mobile application development

When does this service fit?

For use cases involving cameras, notifications, location, field work or repeat use that benefits from a mobile application.

Development scope

• Define journeys, target devices and the need for native or cross-platform development.
• Build interfaces, accounts, data connections and device features with contextual permission requests.
• Test weak connectivity, sessions, updates, synchronization and offline use when included.

From requirements to implementation

1. Device requirements: Choose journeys, permissions and connectivity requirements for each feature.
2. Build & trial: Build connected features and trial them on physical devices within scope.
3. Distribute & update: Prepare test builds, release materials and error follow-up procedures.

What is delivered?

• Journey and interface designs with a target device and OS list.
• Applications, source, agreed backend connections and distributable test builds.
• Device test results, release and update instructions, and store submission preparation.

What needs to be defined?

Stores require owner accounts, policies and submission materials, and acceptance is subject to their review. Maps, messaging and payments may carry separate fees and conditions.

A service-specific acceptance example

Save an action offline and reconnect; show sync state and resolve conflicts without loss or duplication.

Scope, cost & schedule

The discussion starts with users, workflows, data volume, integrations and the existing system. Priorities are agreed, followed by a written first-release scope, cost, schedule and acceptance criteria. Later phases can follow business needs.

Testing, handover & support

The agreement defines handover files, usage rights, hosting, backups, updates and support. Agreed scenarios are tested, and operating setup, permissions and rollback procedures are documented before launch.