Product Development

Start with a first releaseworth building.

A product idea needs a clear scope before development begins. We help you define who it is for, what it needs to do first and the technology behind it, then build and support the agreed web or mobile product.

Areas of support

From idea to product

  1. Idea and goals

    Who it is for and what it must do

  2. Journeys and screens

    Agreed before the build begins

  3. First release

    The smallest version worth launching

  4. Releases that follow

    Shaped by how people use it

Engineering, infrastructure and support from one team

An idea and its goals shape the journeys and screens, the design becomes a first release, and later releases follow how people use the product, with engineering, infrastructure and support from one team throughout.
  1. Discovery and scope

    Pin down the users, the problem and the first version worth building.

  2. Journeys and screens

    Shape the product around the tasks people come to do.

  3. First release

    Build the web or mobile product and the backend behind it, ready to launch.

  4. Improvement after launch

    Plan each next release around what users need and what the data shows.

  5. Platform and support

    Run the infrastructure and look after the product once people rely on it.

Starting a product

Decide what matters before you build it.

A useful first release starts with priorities. We work with you to define the people the product is for, the problem it needs to solve and the tasks it has to support at launch.

That gives the build a clear target and a basis for reviewing scope, costs and changes.

Built to grow

A first release built to keep growing.

We consider likely next steps when choosing the architecture, so future changes can be assessed against a clear foundation.

Cost stays part of every decision: what to build now, what can wait and what the product will cost to run.

Relevant experience

Platform experience, applied to your product.

For NMHS-2, Datalk built an offline-first mobile app, the infrastructure behind it and central data management. We bring that delivery experience to new products, with the technical approach shaped around their requirements and budget.

  • Mobile App & Survey PlatformFlagship programme

    NMHS-2

Technology

The stack behind a product that keeps growing.

We weigh the needs of the first release against maintenance and likely next steps. The aim is a focused set of tools, with additional technology introduced when the requirements justify it.

  1. Web and mobile

    React and Next.js for web interfaces, Flutter or React Native for mobile applications, and TypeScript for typed web and React Native code.

    • React
    • Next.js
    • TypeScript
    • Tailwind CSS
    • Flutter
    • React Native
    • Expo
  2. Backend and data

    Services in Node.js or Python with PostgreSQL behind them, or Firebase for a quick start while the product is small.

    • Node.js
    • NestJS
    • Python
    • FastAPI
    • PostgreSQL
    • Firebase
  3. Releases

    Build and deployment workflows planned around the release process, with checks and rollback arrangements defined for the product.

    • GitHub Actions
    • Docker
    • Vercel
    • AWS

Bring us the idea. We will help you shape the product.

Tell us who it is for, what it has to do and where things stand today.