Engineering
Web & Mobile Products
Customer-facing web and mobile applications built for the conditions they ship into — patchy networks, older devices, and users who will not read instructions.
Built for real conditions, not the demo laptop
A product is judged on a three-year-old mid-range phone on a weak connection, because that is what most people are holding. We set that as the target device from the start rather than optimising for it after launch.
Accessibility is measured, not asserted
Contrast ratios, focus order, touch target sizes and screen reader labels are checked programmatically on every page before release. A claim of accessibility that nobody measured is a claim.
The interface stays coherent as the team grows
A design system with real components — not a page of swatches — is what keeps the tenth screen looking like the first, long after the original designer has moved on.
What this includes
- Progressive web apps and native iOS and Android builds
- Design systems that keep a product coherent as it grows
- Offline-tolerant sync for unreliable connectivity
- Accessibility to WCAG 2.2 AA, verified by measurement
- Analytics and release tooling wired in from the first build
Related services
Hospital Information Systems
HIS and EMR platforms that unify registration, orders, pharmacy, billing and clinical documentation into a single patient record clinicians actually want to use.
PACS & Radiology Informatics
DICOM-native PACS, RIS and reporting workflows — built by a team that understands hanging protocols, worklists and what actually slows a radiologist down.
Interoperability Engineering
Integration engines and FHIR APIs that connect EMR, LIS, RIS, PACS and third-party systems — including the ones whose vendors stopped answering email.
Tell us what you are building.
Describe the problem rather than the solution. We reply with a considered view of what to tackle first — and say plainly if we are not the right fit.