Skip to content

App Development

Build an app around a real job

An application should make a task easier to complete—not simply collect a long list of features. JMG Group plans and builds web applications around the people using them, the information they need and the work they must finish. The first release has a clear boundary, with accounts, permissions and integrations defined around that job.

Business Growth Audit →

Planning a new application does not require a live website. If an existing website is relevant to the problem, the Business Growth Audit is also available.

In short

App Development defines and builds the overall product: user workflows, accounts, records, permissions, integrations and the first useful release.

Application & PWA Development addresses how that product reaches users through the browser, including selected installation, offline or device features where supported. These decisions can be part of one project, not two separate purchases.

The Problem

A feature list does not define a useful application

“Add a dashboard, notifications and user accounts” leaves important questions unanswered. Who can see each record? Who owns the next action? What counts as finished? Which existing tool holds the authoritative information?

If those decisions remain unclear, the application can reproduce the same confusion as the process it replaces. They belong in the scope before development begins.

A feature list without a shared workflowFeatures, roles and records have disconnected paths. A missing workflow leaves their relationships unresolved.FeaturelistUserrolesBusinessrecordsWorkflow undefined

Illustrative Example

From request to completed work

This is a planning example, not a reported client result.

Request received → assigned → reviewed → status updated

A customer submits a request and can see its status. An authorised staff member assigns it to the right person. That person records the decision or completed work. The customer sees the appropriate update without receiving internal notes.

A first useful release might include:

  • Customer and staff sign-in.

  • A request form and agreed request records.

  • Assignment and status changes.

  • Role-based access to the relevant information.

  • Agreed notifications and a record of important changes.

Release Boundary

Keep the first release focused

Payments, advanced reporting or additional workflows would wait unless they are essential to completing that first job.

The Solution

Define what users can accomplish at launch

JMG Group maps the workflow and turns it into an agreed release scope. That includes what each user can do, the records the application needs and what happens when something goes wrong.

Application architecture begins with the workflowWorkflow and MVP scope inform records and permissions, which support interfaces and integrations.Workflow + MVP scopeRecords + permissionsInterfaces + integrations

Project Scope

What the project can include

  • First-release scope

    Users, essential tasks, acceptance criteria and a clear list of what waits.

  • Workflow and data design

    Forms, records, status changes and relationships that support the agreed tasks.

  • Accounts and permissions

    Sign-in, account ownership, organisations and rules governing who can read or change information.

  • Interfaces and integrations

    Connections to existing tools, subject to access and compatibility, with defined handling for failed or repeated updates.

  • Testing and release

    Checks for the agreed user journeys, permissions, validation, error states and performance.

  • Handover and iteration

    Guidance for operating the application, with support and later development agreed separately.

The Shortcut

Start with one complete workflow

A smaller first release lets you review a working task rather than wait for every possible feature. The aim is a coherent application that can be used and evaluated—not a large collection of unfinished screens.

Later priorities can then be informed by observed use and customer or staff feedback. A phased approach still requires careful decisions about data, access and future dependencies.

The Outcome

A usable first release with clear responsibilities

Users should be able to complete the agreed job and understand its progress. The business should know who owns the information, how access is controlled and what needs attention when a connection or action fails.

Adoption, time savings and commercial results depend on the workflow, implementation and how the application is used. They are not established by launching software alone.

An application connected to the businessThe application connects with strategy, automation, delivery and measurement rather than operating in isolation.StrategyAutomationDeliveryMeasurementApplication

Delivery

How the work proceeds

  1. 01

    Define the job

    Identify users, current workarounds, required records and the first-release boundary.

  2. 02

    Design the workflow

    Agree screens, permissions, integrations and important failure cases.

  3. 03

    Build and review

    Develop complete parts of the workflow so they can be demonstrated and reviewed.

  4. 04

    Test the release

    Check permissions, normal and exceptional cases, and the intended devices.

  5. 05

    Launch and learn

    Hand over the agreed release and prioritise further work from evidence.

Relevant Work

Local Foodies

Local Foodies provides a real example of an application involving business listings, ownership claims, dashboards and moderation. The case study shows how those capabilities fit a marketplace; it is not the request-management example above.

From John

App Development

I want to be able to describe the job an application does in plain sentences before discussing the feature list.

That makes it easier to decide what belongs in the first release, who should have access and which existing tools need to connect. I would rather begin with one useful workflow than ask people to adopt an application whose purpose is still unclear.

John M Granskou, founder of JMG Group
John M Granskou, SEO, CROGrowth Systems Architect

FAQ

Frequently Asked Questions

What does a first useful release include?
Enough to complete the agreed core workflow, including necessary access controls, validation and error handling. The scope is specific to the project; it is not a standard bundle of screens.
How is this different from PWA Development?
App Development covers the overall product. PWA work addresses browser delivery and selected installation, offline or device features. Both may be included in the same project.
Does this include native iPhone or Android apps?
This offer focuses on web applications. Native applications and app-store distribution are not implied; any requirement for them needs a separate feasibility and delivery discussion before a proposal.
Can the application connect to our existing tools?
Potentially. Compatibility, available connections, permissions, data ownership and failure handling need to be assessed before the integration is included in scope.
Can different users have different access?
Yes, where required by the agreed workflow. Roles and ownership rules are defined and tested as part of the application, rather than relying only on hiding screens or buttons.
What happens after launch?
Monitoring, support and further development are agreed separately. Later releases can be prioritised from actual use, feedback and business needs.

Describe the job your app needs to do

Bring the users, the current process and the systems already in use. The conversation starts with what a useful first release should accomplish.

The Audit requires a live website and is suitable when that website is relevant to the problem. It is not a prerequisite for discussing a new application.