Point-of-care diagnostics · Product localisation · Android
ThyroSpot India Localisation
The localisation problem was not translating a screen. It was controlling every condition between a biological sample and a repeatable reading.
Every product visual is labelled by provenance, so original work is never confused with a portfolio-created explanation.
A genuine working document, wireframe, screenshot or output that can be shown publicly.
A recreated product view grounded in the original work, using synthetic or anonymised information.
A simplified model created for this portfolio to explain system behaviour, workflow or product logic.
The product problem beneath localisation
A diagnostic platform could not be moved into a new market as though it were only an app.
Medtech · Point-of-care diagnostics · Android · Product localisation · Market entry
Clinical workflow, sample handling, operator training, environmental conditions, phone behaviour, storage, offline use, regulation, service, pricing and distribution all influenced whether the system could operate consistently. The product task was to preserve the diagnostic workflow while redesigning the surrounding operating environment for India.
The sample and cassette create their own operating constraints.
Handling sequence, timing, storage and operator technique all affect what reaches the imaging stage. The interface could not compensate for an uncontrolled pre-analytic workflow.
A camera reading is only meaningful when alignment and illumination are controlled.
The reader had to position the cassette at the correct focal relationship while the light enclosure reduced variation in image acquisition.
A general-purpose phone introduces uncontrolled behaviour.
Notifications, settings, unrelated apps, operating-system differences and connectivity assumptions could all interrupt or alter a high-stakes workflow.
Regulation, distribution, service and training shape the product itself.
India entry required the physical system, software workflow and operating model to be considered together rather than as separate launch workstreams.
The end-to-end diagnostic product
The result was produced by a chain of chemistry, hardware, optics, software and operator actions.
The smartphone app sat near the end of the workflow. Before software could analyse anything, the sample had to move through a disposable assay, the cassette had to be aligned with the camera and image acquisition had to happen under defined illumination.
Serum / plasma enters a controlled assay workflow
Test, control and calibration signals become visible
Cassette and camera are held in a defined relationship
The light-box stabilises image acquisition conditions
Android software identifies and quantifies the optical signal
The result is stored and interpreted within the clinical workflow
Turn measurement variability into explicit product controls
The localisation work started by asking what could vary—and what the product had to control.
Each source of variation created a corresponding product responsibility. Some controls lived in hardware, some in Android, some in instructions and some in the operating model around storage, training and service.
Preparation · timing · condition
Guided handling sequencePosition · test/control visibility
Indexed physical fitFocus · angle · camera alignment
Reader attachmentAmbient illumination
Defined light enclosureApps · settings · OS behaviour
Standardised Android environmentSequence · interpretation · training
Constrained workflow and instructionsThree decisions that made localisation operable
The highest-leverage choices were about control, not cosmetic adaptation.
The product decisions connected consumer hardware, a biological assay and field operations into one repeatable workflow. Each decision reduced a different form of uncertainty before the result reached the user.
Treat the smartphone as part of the medical instrument.
The phone was not merely a display. Its camera, operating system, installed software and settings directly participated in image acquisition and result generation. The India configuration therefore treated the handset, reader and app as one controlled product system.
Control the conditions around image capture.
Image analysis depended on a repeatable view of the cassette. The reader attachment aligned the cassette with the smartphone camera, while the light enclosure reduced illumination variability. Calibration and control signals remained part of the workflow rather than hidden technical details.
Localise the entire operating workflow, not only the interface.
The India work covered cassette handling, software sequence, operator instructions, device interaction, offline use, training, storage, service and market-entry dependencies. A translated interface would have left the most consequential workflow risks untouched.
Make a general-purpose device behave like a dedicated instrument
The Android environment was intentionally reduced around the diagnostic workflow.
The India-specific configuration removed unnecessary device behaviour and prioritised a kiosk/POS-style operating mode. The core workflow did not depend on continuous connectivity, and test images and analysis results could remain stored on the handset.
From clinical discovery to India-readiness work
I connected clinical discovery, product localisation and Android-side delivery into one India-readiness programme.
My scope covered market and user research, hospital and laboratory workflow discovery, beta-test planning, Android customisation, kiosk-mode operation, diagnostic application work, workflow localisation, clinical stakeholder coordination, distributor and regulatory workstreams, and go-to-market planning. The work required translating field constraints into product and engineering decisions across software, hardware and operations.
India market, user and clinical-workflow research
Beta-test planning and small-scale field testing
Android customisation and kiosk-mode operating model
Diagnostic application and workflow localisation
Cross-functional coordination across clinical, hardware and software work
Regulatory, import, validation, service and distribution preparation
Preserve the diagnostic logic while adapting the device, workflow and operating environment around it.
Evidence-bounded outcomes
Delivered work
What changed as the platform was adapted for the Indian operating context.
Completed India-market product assessment and clinical-workflow discovery.
Led Android customisation, kiosk-mode operation and diagnostic-application work.
Localised the end-to-end operating workflow rather than only the user interface.
Conducted small-scale field testing of the India-specific configuration.
Supported regulatory, import, validation, local-manufacturing, laboratory and distributor workstreams.
The work reached India-market adaptation, product localisation and small-scale field testing. This case does not claim Indian regulatory approval, commercial launch, large-scale clinical validation or clinical impact.
The public product views are portfolio reconstructions based on documented system behaviour. Private partner, regulatory, clinical and field-testing materials are not published.
What the work changed in how I think
A high-stakes product is the complete chain that produces the result.
The app was only one component of the product.
Chemistry, physical alignment, illumination, software and operator behaviour formed one measurement chain.
Workflow variability can become product risk.
In high-stakes environments, uncontrolled steps before and after the interface can matter more than the interface itself.
Controlled simplicity can be safer than flexibility.
Restricting device behaviour reduced operational uncertainty and kept the diagnostic workflow primary.
Market entry belongs inside product strategy.
Regulation, service, distribution and device standardisation materially influenced the India product configuration.