sector
patient apps, clinic systems and field-force tools where the data is somebody's health
Subscription patient care across a clinic network, consent portals, and a pharma field-force app with odometer-based travel allowance.
- 18
- health engagements
- 2
- apps, patient and clinic
- 8 yrs
- on one clinical estate
- SIGSEGV
- diagnosed from native frames
Clutch
the problem
what this sector actually deals with.
Health software fails in ways other software gets away with. A shared device that shows the previous user's notifications is not a UX bug, it is a privacy incident. A crash you cannot reproduce is not an annoyance when the app holds someone's appointment. And the person reviewing your data model needs to know the domain, not just the schema.
sound familiar?
- Devices get shared between staff and between shifts
- Consent and treatment records cross system boundaries
- Accessibility is a requirement, not a nice-to-have
- Crash reports point into the framework, not your code
- Clinic-scoped access has to be real, not implied by the UI
what we have built here
systems delivered in this sector.
Subscription patient care
A patient app and a separate clinic app on a shared API for a dental network — plans, family members, appointment booking and visit history for patients; appointment handling and history scoped to the clinic for staff.
Consent and patient portals
A patient portal handling treatment consent forms alongside a commerce site, plus a treatment guidance app — part of an eight-year, four-system estate for one clinical business.
Pharma field force
A medical representative app with punch-in and punch-out capturing an odometer photograph plus a manual reading, in and out kilometres recorded, and travel allowance calculated automatically for the day.
Release discipline
Crash reporting wired to a dedicated project, an over-the-air update channel so patches ship without a store round trip, and app version tracked via a header written to the customer record by middleware.
the hard part
notifications that followed the device instead of the user.
On a field-force app, notifications were read from device storage rather than from the server. A second user signing in on the same handset could see the previous user's notifications.
- 01
On a field application where one device passes between staff, that is a data-privacy failure rather than a UX bug, and it was fixed by moving the read path to the server where identity is actually known.
- 02
The other hard one was a fatal native crash — a SIGSEGV deep inside React Native's Fabric rendering pipeline during a shadow-tree commit, reproduced on a specific Android version and handset. Every frame in the report was native; none were application code.
- 03
Diagnosing that meant reading the crash chain through the framework's own binding and commit layers and correctly concluding it was a framework or OS-level race, not an app bug — which changes the response from a rewrite to a mitigation and an upgrade path.
- 04
Domain review matters as much as either. On a sports platform in the same portfolio, the system happily accepted a coach aged six; real coaching qualifications start at fourteen. That rule only surfaces when somebody who knows the field looks at the data.
what it runs on
the stack we reach for here.
Chosen for the sector requirements and for maintainability over the life of the system.
- Mobile
- React Native, with over-the-air updates and dedicated crash reporting
- API
- Node.js, clinic-scoped access enforced server-side
- Portals
- Patient-facing consent and records, separated from commerce surfaces
- Operations
- Version tracking via request header, written to the record by middleware
how an engagement runs
what the first weeks look like.
Scope against real user stories
Negotiated line by line with your clinical team, not inferred from a wireframe.
Decide what is not in the MVP
On one build we deliberately excluded the public website to control cost, while designing the API to support it later. Saying no early is what keeps the budget honest.
Test on real devices
Shared handsets, older Android versions, and the accessibility settings your users actually have switched on.
Ship patches without the store
An over-the-air channel, configured before you need it rather than during an incident.
selected work
written up in full
The engagements with the detail attached — and the numbers.
01
B2B commerceThe engineering partnership behind a cross-border wholesale marketplace.
Next.js storefront, Python ingestion pipelines, DynamoDB data layer and AWS infrastructure.
02A commission-free ticketing platform built for ownership and scale.
Multi-organiser commerce, Stripe instalments and two native apps in one connected platform.
03
Global logisticsEmbedded product engineering for a global shipping platform.
Rate, tax and duty calculators, server-rendered courier pages and a custom MongoDB CMS.
04A custom furniture marketplace engineered from storefront to infrastructure.
Server-rendered Next.js commerce over a Laravel API, bespoke operations tooling and re-architected AWS infrastructure.
05An AI-native operating system that runs a consultancy lead to invoice.
Discovery briefs, e-signed contracts, Stripe deposits, delivery milestones and time tracking in one operational system.
06A conversion platform for a growing UK boiler-cover provider.
Custom plan configuration, postcode-qualified lead journeys, CRM synchronisation and campaign landing pages.
07A custom Shopify store for a French beauty brand.
Custom theme, customer accounts, loyalty rewards, referrals and gift-with-purchase offers.
08Made-to-measure shutters with live pricing.
A seven-step product builder with live previews, sample orders and supplier tools.
09
AdvertisingA self-service advertising platform for venues.
Campaign creation, audience targeting, in-app ads and reporting linked to venue check-ins.
10Social eventsAn events app with the tools to run it.
Mobile app, backend, advertising tools, a digital marketplace and website.
11Two mobile apps for real-time companionship.
Customer and buddy apps with per-minute billing, wallets, moderation and admin tools.
12Player profiles and discovery for youth football.
Verified profiles, video highlights, coach discovery and safeguarding on web and mobile.
13Websites and a talent platform for DeepSpatial.
Corporate and investor pages, the Xploor talent platform and ongoing releases on AWS Amplify.
14
TravelTour bookings with a custom mobile-first checkout.
A multilingual website connected to the booking API, with deposits, coupons and affiliate tracking.
15One platform for tenders, contracts and accounts.
Supplier tenders, contract management, brokerage accounting and client records.
Teams that trusted us with the thing that matters
UK · Europe · Worldwide
the practices behind it
what this work is made of.
native mobile
React Native apps that ship past App Store review and stay shipped — offline-first paths, push, real-time sync and over-the-air updates.
product engineering
Multi-tenant SaaS, marketplaces, ticketing and booking engines — the systems your business actually runs on, built to survive their own success.
rescue & security
AI-generated prototypes and stalled builds taken to production, and compromised live systems recovered — audited first, stabilised second, then finished and hardened properly.
reviews · verified on clutch
the people who signed off the work
Clutch★★★★★5.0 / 5.0Across 18 independently published client reviews
“They have a deeper technical knowledge than any web designer I've met to date.”
faq
questions from this sector
Do you handle both patient and staff apps?
Yes, usually on a shared API — which is what keeps clinic-scoped access consistent between them.
What about accessibility?
It gets tested. Client testing on one build found text not responding to system text-size settings and dead-end empty states; both are the kind of thing that only shows up if somebody actually checks.
Can you work with our existing clinical systems?
Yes. Integration into existing records and scheduling is normal; we will be honest about which integrations are hard before you budget for them.
Is our data safe with an offshore team?
You own the repository, the cloud accounts and the keys from day one, and we scope access per engagement. Ask us for the security page — that is a practice here, not a checkbox.
keep reading
the other sectors we work in.
building something with patients on the other end?
A thirty-minute call with the engineer who would lead the work.