Skip to article
Back to bobTech

bobTech / STUDIO GUIDE

Mobile applications

Purpose-built interfaces for people working or buying on a phone or tablet.

When this is useful

Products whose device features or repeat usage justify an application.

What we can include

We shape the exact deliverables around your brief and confirm them in the proposal.

  • Platform and user-flow planning
  • Responsive screen and interaction design
  • Build, testing and release preparation

What to bring

Identify target devices, account flows and required phone capabilities.

An example brief

A field team needs to record visits from a phone. The first release could focus on a small set of actions, with the required offline and synchronisation behaviour agreed in advance.

Decisions to make together

These questions help turn a broad request into an actionable scope.

  • Which platforms and device versions are in scope?
  • What should remain available without a network?
  • Who owns store accounts, release approvals and ongoing updates?

What we review before handover

The final review criteria are agreed for your project. A typical checklist could include:

  • Test core journeys on the agreed physical devices.
  • Review interrupted connections and any queued updates.
  • Verify permission prompts, session handling and the release checklist.

How the work progresses

We agree the brief, review a direction, develop the selected approach and check the agreed deliverables before handover. Review rounds and approval responsibilities are set at the start.

Scope and dependencies

App-store accounts, store review, supported OS versions and ongoing updates are agreed separately.

Planning cost and timing

Complexity, available assets, number of outputs and external dependencies affect the estimate. Share your priorities and deadline so we can propose a realistic first phase.

Let’s apply this to your project.

Tell us what you want to create, what already exists and what a useful next step would look like.

Plan your project