App development consulting

Make the product and platform decisions with something working in front of you.

Touch Grass beta, with a sand canvas and instrument controls.

Decide with a prototype.

Gesture-driven sound. Shown in its beta build.

Our own products put those decisions into practice.

From the first conversation to the handover.

  1. Define the decision

    Start with the user, the task and the constraint that matters.

  2. Make it tangible

    Use a small working example to test the uncertain part.

  3. Set the scope

    Agree the deliverables, assumptions and next review point.

Make the uncertain part concrete

You might have a brief, a prototype or an app that has become hard to change. We begin with the decision you need to make: what to build first, which devices to support or whether the current code can carry the next release.

The work can include a review of the user journey, a codebase assessment, an integration map or a small technical prototype. The output is a set of decisions and an implementation scope with assumptions attached. It is useful whether we build the next stage or your team does.

Native, cross-platform or web

Compare the audience, device features, offline needs, interaction quality and maintenance burden. Our hands-on product evidence is strongest in native Apple apps. If Android or a cross-platform framework is part of the requirement, we assess that path explicitly and identify any additional delivery expertise it needs.

A wearable needs its own reason to exist

A watch companion should make a short task easier: glance, acknowledge, start or stop. We can scope the interaction, the phone dependency and a prototype. This is a planning offer, not a claim of an existing production wearable portfolio.

What you leave with

A prioritised scope, the open technical questions, recommended next steps and a practical acceptance check for each deliverable. Timing and fees depend on the material to review and the depth of the work.

A few things you might be wondering.

What should I bring?

The idea, the users, any existing code and the decisions you are stuck on. A long specification is not required.

Will we choose a technology straight away?

We first establish what the product needs to do. Native, cross-platform and wearable choices follow the requirements and the constraints.

Tell us what you're building.

Bring the task, the people using it and the systems it needs to work with. We'll define the scope and the next useful step.

Discuss your project