Mobile products. Thought through.

App development, from the first question to handover.

Turn a product idea into an agreed scope, a reviewable user journey and a release with understood responsibilities.

Explore the process
iOSAndroidCross-platformIoTAI
Mobile app and tablet dashboard on a desk.
Define a complete product journey
Prototype the behaviour as well as the interface
Development that can be reviewed
Publishing, account ownership and handover
The starting point

Start with the problem, before selecting a framework

Mobile app and tablet dashboard on a desk.

Mobile app development is useful when recurring use or access to a phone’s capabilities creates a clear advantage for the intended users. A field workflow may need a camera and a way to cope with interrupted connectivity. A connected product may need pairing and device status.

Read more

A customer service may need a simple action that can be repeated without friction. Discovery begins with that task and its context. Define what the user should complete independently and when another person or system needs to take over.

It is also reasonable to examine whether a mobile website could solve the problem. Installation, accounts, publishing and ongoing care create responsibilities for a product owner. Those responsibilities should support a genuine use case. Where an existing system already holds the data or business rules, the mobile application depends on that system. Understanding its interfaces and limitations belongs in the initial scope. A phone interface alone cannot resolve missing backend behaviour or unclear ownership of the underlying process.

App development

Define a complete product journey

A workable specification describes a task from its starting point to a useful result. For example, a field record might begin with selecting an assignment, continue with data entry and a photograph, and finish with confirmation of submission. This is an illustrative planning scenario, not a client reference.

Read more

At every step, decide what information appears, who can change it and how the user recovers after an interruption. These decisions make the expected behaviour reviewable before implementation begins.

Features should be described with their dependencies. A notification needs a triggering event, an intended recipient and somewhere useful to go when it is opened. Search needs an authorised data source, sensible results and an empty state. The initial release should contain the features required for the selected core journey. Keep possible extensions in a separate backlog so that accepting the current scope does not imply a commitment to every future capability. Clear boundaries help both planning and validation.

App development

Choose platforms around the actual users

The choice of iOS, Android or both should follow the users and the devices they need. Native and cross-platform approaches deserve comparison where appropriate. Shared behaviour, deeper system integration and long term maintenance needs can affect the decision.

Read more

We develop native iOS apps in Swift and Android apps in Kotlin, as well as Flutter, React Native and PWA applications. We also build backends and APIs, IoT/BLE apps and AI features. We select technology around users, required features and ongoing maintenance.

The choice should also account for handover. Document how the application is built, what accounts it needs and which external components it uses. A shared codebase does not remove differences in permissions, operating system behaviour or testing requirements. Agree the supported device and system scope, then record the reasoning behind the technology decision. That record gives later changes a useful point of comparison when a new feature brings different integration or maintenance requirements.

App development

Discovery produces decisions and open questions

Mobile app and tablet dashboard on a desk.

Discovery should describe users, roles, tasks and the environment in which the product will run. Separate mandatory business rules from convenience features and assumptions that still need evidence. Existing systems may require API documentation and a suitable test environment.

Read more

A hardware project may need a communication specification and access to a working device. Missing information should become an explicit investigation task. It should not silently become a finished requirement with an assumed solution and an unreliable delivery estimate.

Acceptance conditions make the specification practical. A successful save should be readable afterwards, a failed request should explain what happened, and each role should see the actions it is allowed to perform. Write these conditions in the language of the task. Open questions need an owner and a point at which they will be resolved. The agreed specification can then support a proposal, a prototype and the release review, while providing a reference for any requested changes.

App development

Prototype the behaviour as well as the interface

A prototype makes the core journey easier to discuss before full implementation. It should show the route to the desired result and the important alternatives: empty data, invalid input, denied permissions and interrupted actions. Labels, input order and feedback can expose misunderstandings while they are still inexpensive to resolve.

Read more

A visual design becomes a useful development reference when the behaviour of its elements is understood. Agreeing colours alone does not settle what the product needs to do.

App UI and UX should reflect the environment. A person working outdoors or next to a device may need different interaction priorities from someone browsing at home. Readability, touch targets and content order contribute to accessible use. Where possible, review the design by walking through an actual task with suitable sample data. After a flow is approved, a newly requested journey may change the scope. Discuss its effect on implementation and testing before treating it as part of the release.

App development

Backend, administration and data boundaries

Many mobile projects need server work as well as an app. Sign-in, shared records, permissions and notifications may depend on APIs and business logic. An existing backend needs a documented interface and understood failure responses.

Read more

A new backend needs decisions about administration: who can correct records, grant access or investigate a failed operation? These responsibilities should be visible in the scope. A polished phone interface cannot make an otherwise unmanageable system ready for operation.

Offline operation requires its own agreement. Decide which information is available locally, how long it can remain useful and how conflicting changes are handled after reconnection. A lost phone, a departing employee and a revoked account are also product scenarios. Keep data and permissions within the needs of the task. External integrations introduce dependencies on another provider’s availability and changes. Their operation should be considered when agreeing support responsibilities and preparing a release that relies on those services.

App development

Connected hardware and AI features

Mobile app and tablet dashboard on a desk.

For IoT or BLE communication, pairing and recovery from failure belong in the main user journey. The app and firmware need an agreed meaning for each message. Distinguish a request that was sent from a command that the device actually completed.

Read more

Testing requires suitable hardware and a way to reproduce relevant failures. If the hardware is still changing, its interface changes must be tracked because they may affect the mobile implementation and the conditions needed to validate it.

An AI feature needs an expected result and an understood failure boundary. Suggested search terms and information prepared for a business record may require different review steps. Provider access and usage limits normally need an appropriate server boundary; confidential provider credentials should not be embedded in the mobile client. Discuss human approval, alternative workflows and service outages during discovery. External processing should only receive information that the project’s agreed data handling conditions allow it to use.

App development

Development that can be reviewed

Implementation can be reviewed through agreed pieces of functioning behaviour. A demonstration should explain what can be tried, which connections are using test environments and which questions remain open. Validation includes more than a successful login.

Read more

Interrupted requests, slow connections and permission decisions can change the user experience. Select checks according to the project’s actual risks. When a new requirement appears, discuss it against the approved scope so its effects on the app, backend and testing remain visible.

A test environment should use appropriate data and access. Agree how trial builds are shared, which devices matter and how issues are reported. A useful report describes the starting state, the action taken and the observed result. That makes it easier to distinguish a defect from a new product request. Before release, decide whether each remaining issue needs correction, a later task or explicit acceptance as a limitation. Include those decisions in the handover notes.

App development

Publishing, account ownership and handover

Publication involves the build, developer accounts, store information and an explanation of how reviewers can use the app. Account ownership should be determined early. Access and signing arrangements should not wait until the final step.

Read more

Store review is an external process, so acceptance cannot be guaranteed. The current submission requirements need checking for the actual release. A checklist from a previous project can be a starting point, but it does not replace that release-specific preparation.

Agree handover contents in the contract. They may include source code, build instructions, configuration locations, account access and the publishing process. Access details should be transferred through an appropriate secure channel. Ownership and usage arrangements should also account for external component licences. For an existing app takeover, the first step is to check which of these foundations are available. Missing access or an unreproducible build can become a separate investigation task before further development can be planned reliably.

App development

What affects mobile app development cost?

The effort follows behaviour, dependencies and uncertainty. Roles, integrations, offline data, hardware communication, design and the validation scope can all affect it. Existing code introduces questions about its condition and build process.

Read more

External services and the operating environment may create separate cost dependencies. Discovery turns those factors into a proposal with visible assumptions and exclusions. Screen count alone is not a sufficient basis for a project price, and public package figures would not describe an unassessed project accurately.

Changes need the same reasoning. An additional integration can alter screens, server behaviour and tests together. Rank optional capabilities separately. Maintenance should be agreed as its own scope, including relevant dependency updates, operating system changes and connected services. We do not publish invented prices or return-on-investment promises. A reserved knowledge page will cover the factors involved; the project enquiry is where the actual requirements can be discussed and the information needed for a proposal can be identified.

ScopePlatformsIntegrationsTestingMaintenance
Pricing and cost planning
App development

Boundaries and the next step

We do not make unconditional development promises for unknown code or guarantee external approvals. Unauthorised copying and bypassing access controls are outside the scope. A regulated product may need appropriate specialist input before implementation choices are settled.

Read more

Tell us the target users, core task and intended platforms. Mention existing hardware, a backend, an app or a prototype, and list the uncertain points too. A redacted sample or a short process description can help define the first investigation and the decisions needed before delivery begins.

Before we begin

Frequently asked questions

Do I need a finished specification?

No. Start with the intended users, their core task, target platforms and any existing systems. Discovery can identify the missing information.

Can the project cover iOS and Android?

We discuss platforms around the actual users. We select technology around users, required features and ongoing maintenance. We document the agreed delivery scope.

What determines the price?

Behaviour, integrations, offline needs, design and validation affect effort. A proposal requires an understood scope and visible assumptions.

Can you assess an existing app?

A takeover begins with source access, a reproducible build and an understanding of service and account dependencies.

Can an app connect to hardware or include AI?

These are suitable topics for an enquiry. Communication, data flow, failure handling and the exact implementation need assessment.

What happens after launch?

Handover and maintenance responsibilities are agreed separately. System changes, dependencies and connected services may require continuing work.

Your next step

What should your app solve?

Tell us about the users, the core task and the systems involved.

Request a quote
Mobile app and connected device illustration
Request a quote

Tell us what you need

A few details and a short description are all we need. We’ll get back to you with the details.

What happens next

  1. Describe the task, with a redacted sample if useful.
  2. An optional AI assistant asks clarifying questions.
  3. A person reviews your request, then we get back to you with the details.
  • Built around your workflow
  • With human review
  • Design, app, maintenance
[email protected]
0 / 4000