Skip to content
Discuss a project

Software · 02

Web & mobile applications

Responsive, usable applications for people at a desk and people in the field, backed by a reliable architecture and a clear release plan.

Discuss your requirements View related projects

1440 PXOffice desk768 PXTablet on site390 PXPhone in the field

One inspection feature on a laptop and a phoneA laptop shows a web application listing this week's site inspections, with inspection INS-2207 for pump room B selected and its photos and readings in a side panel. In front, a phone shows the same inspection adapted for field use: a checklist with ticked items, a pressure reading being entered, photo capture and an indicator that the phone is offline with three changes queued to sync.1440InspectionsSitesScheduleReportsAll syncedThis week18 inspections · 4 sitesAssignIDSITECHECKSSTATEINS-2207INS-2206INS-2205INS-2204INS-2203INS-2202Pump room BSubstation 3Chiller plantGenerator yardRoof AHU-2Boiler roomOn siteDoneQueuedDoneDraftDoneView all 18 →INS-2207Pump room BStarted 09:40 · mobile2 pendingDischarge pressure4.2 bar12 of 14 checks9:41‹ This weekPump room BINS-2207 · 12/14Valve taggedGuard fittedNo leak at sealDischarge pressure4.2barSeal housing photoOffline3 changes queuedWEB APPAT THE DESKSAMEFEATURE,IN THEFIELDOFFLINE QUEUESYNCS ON RECONNECT390
Illustrative interface · one inspection, desk and field views

One product, three surfaces

Different screens. One back end underneath.

Office staff, field teams and customers rarely need the same screen. They do need the same records, rules and permissions. We design each surface for its user and build them on shared services, so a change made in the field is what the office sees.

Three user surfaces sharing one back endA web application for office staff, a mobile application for field teams and an installable progressive web app for customers each connect over HTTPS to the same back end, which provides authentication and roles, a REST API, an offline sync queue, file and photo storage, notifications and the database.01 · WEB APP02 · MOBILE03 · PROGRESSIVE WEB APPapp.example.comInspectionsSitesScheduleReportsUsersInspections per weekW37W42OPEN6OVERDUE1INS-2207INS-2205Pump room BChiller plant12/149/14Pump room BValve taggedGuard fittedGauge readingOffline · 3 queuedportal.example.comRequest a site visitSitePreferred datePump room B21 Oct, morningSendInstall the portalAdd to home screenInstallOFFICE · TABLES · REPORTS · ADMINFIELD · OFFLINE · CAMERACUSTOMERS · INSTALLABLE · NO STOREHTTPS · JSONHTTPS · SYNCHTTPS · JSON04 · SUPPORTING BACK ENDAuth & rolesREST APISync queueFiles & photosNotificationsDatabasesign-in · permissions/v1 · versionedoffline changesobject storageemail · pushrecords · audit
  1. 01 Web appFor the officeFull tables, reports, scheduling and administration, built responsive so it still works on a laptop in a site cabin.
  2. 02 MobileFor the fieldShort tasks, large tap targets, the camera, and work that continues without a signal and syncs later.
  3. 03 PWAFor customers and suppliersAn installable web app from a link: no app store listing, one codebase, updates on release.
  4. 04 Back endShared by all threeOne set of records, permissions and rules, exposed through a documented API. Cloud & APIs →

Typical deliverables

What a project can include.

The exact package is agreed from your context, risk, timeline and responsibilities. A small product may start with discovery and one surface.

  1. 01

    Product discovery and interaction flows

    Who uses it, where, and on which device. User journeys and clickable flows are agreed before any code is written.

    OUTPUTJourney maps · wireframes · clickable prototype

  2. 02

    Responsive web applications

    Browser-based applications that hold up from a wide office monitor down to a phone, with accessibility checked as we build.

    OUTPUTWeb application · shared UI components

  3. 03

    Mobile and progressive web experiences

    Mobile experiences or installable web apps for people away from a desk, including offline work where the job needs it.

    OUTPUTMobile app or PWA · offline sync where in scope

  4. 04

    Back-end services and release support

    The APIs, data and hosting behind the screens, with a release plan for each version and documentation for handover.

    OUTPUTAPI · deployment · release plan · handover docs

A good fit for

When a new interface is the right investment.

If the problem is the process rather than the screen, start with custom business systems.

  1. 01New digital services and customer experiencesA service your customers or partners will use directly, where usability decides whether it gets used at all.
  2. 02Teams validating a product directionA focused first version to put in front of real users before committing to the full build.
  3. 03Organisations replacing fragmented interfacesSeveral tools, forms and logins doing parts of one job, brought into one consistent product.

Engagement flow

Brief→Scope→Design→Delivery→Support

Milestones, review points and acceptance criteria stay visible from start to handover.

Start a conversation

Talk through your web or mobile product. Start with who uses it.

Tell us who the users are, where they work and what they need to get done. We will come back with the surfaces we would build and the questions to answer first.

Discuss your requirements All software services

Inquiries are routed to the software practice lead.