VANKPA
Start a project

Selective mobile products

Build for a task that belongs on mobile.

Before building an app, establish who needs it, what they need to do, and whether a mobile website or existing tool could do the job.

Illustrated scene: Two people compare a phone and tablet at a device-testing bench.
Illustrative planning scene

Who it is for

A focused way forward.

For teams with a proven mobile need, someone responsible for launch, and a realistic support plan. Every app project begins with discovery.

Engagement
Selective mobile products
Timing
Selective custom mobile products start at $28,000. Builds typically take 10–24+ weeks depending on platform, backend, and release scope; discovery confirms fit and timing.
What you receive
A build-versus-buy recommendation and first-release plan

Problems it solves

Signs this may be the right starting point.

If these challenges sound familiar, this service may help you move forward.

01

A mobile task with no good tool

02

An unvalidated first release

03

Unclear device or offline needs

04

No release or support owner

Illustrated scene: Three people review mobile screen layouts around a low workshop table.

Plan before you build

Agree on the goal. Then plan the work.

We compare existing options and test the main user journey before development. Together, we define the first release, permissions, support needs, and who will run it.

Phase 01

Validate the mobile task

Identify what people need to do on the move and what currently stops them. Check whether a mobile website or an existing tool is enough.

What you receiveA recommendation on whether to build
Phase 02

Test the first journey

Prototype the core task with representative users, including interruption and recovery.

What you receiveA focused prototype and validation findings
Phase 03

Agree on a release

Agree on supported devices, permissions, data, integrations, and completion checks before development begins.

What you receiveFirst-release scope and technical plan
Phase 04

Build and test on devices

When a build is agreed, implement the scoped release and test real devices, failed actions, and connection changes.

What you receiveA tested first release
Phase 05

Prepare ongoing ownership

Confirm who handles release and support. Track completed tasks, failed actions, and the problems users report.

What you receiveRelease checklist and owner handover
01SET

Scope defined

Included work, exclusions, responsibilities, and review points are agreed before delivery.

02NAMED

Outputs named

You know what you will receive and how each part supports your project.

03VAN

Senior lead

Van stays close to the strategy, experience, engineering, and launch.

Scope clarity

Know what the work includes.

The proposal names the sources, outputs, owners, and checks for your project.

What is included?
  • Discovery and comparison with a mobile website or existing tools
  • Agreed first-release plan and user journeys
  • Prototype and task-validation plan
  • Technical, data, and permission decisions
  • Separately agreed cross-platform or platform-specific implementation
  • Device testing, release preparation, and owner handover
What is outside the scope?
  • Every possible feature in the first release
  • Untested platform assumptions
  • App-store approval, adoption, or retention guarantees
  • Ongoing platform fees or unbounded post-launch support
What do we need to begin?
  • A meaningful mobile use case and representative users
  • A decision-maker and release owner
  • A realistic operating budget and support plan
  • Agreement on device permissions, sensitive data, and release scope
How will progress be measured?
  • Agree on task completion, failed or interrupted actions, support issues, and release acceptance checks before building. Downloads alone are not a measure of usefulness.

A practical starting point

Let’s plan your next move.

A short description is enough to begin. Tell Van about your business, the challenge, and your timing and budget if known.

Capture in context: Choose device features only when they help the real user task.; Keep state clear: Explain saved, pending and failed actions, including interrupted connections.; Prepare the handover: Agree the release checks, ownership and support boundaries.
The work, made visible

Design around the mobile task

  1. 01
    Capture in context

    Choose device features only when they help the real user task.

  2. 02
    Keep state clear

    Explain saved, pending and failed actions, including interrupted connections.

  3. 03
    Prepare the handover

    Agree the release checks, ownership and support boundaries.

Practical planning view. Final scope is agreed before work starts.
Help me choose