Thermovision
Turn an early thermal-health concept into a connected mobile product.
The product would only be useful if a specialist imaging workflow could feel calm, repeatable, and understandable in someone’s hands.
A promising instrument without a product around it.
Thermovision began with a compelling proposition: use temperature variation to add context to personal skin monitoring. The specialist camera could produce meaningful thermal information, but the surrounding experience was still a collection of technical possibilities rather than a repeatable consumer product.
The early conversations were less about screens than confidence. A scan taken badly would create noise; a result shown without context would create anxiety. The product had to make every step—from connecting the device to returning weeks later—feel deliberate and legible.
Make the scan the organizing principle.
Instead of treating the camera, analysis, reminders, and history as separate features, we organized the system around one repeatable scan. Every decision had to help a person capture a useful image now or understand its place in a longer monitoring history later.
That choice clarified the interface and the architecture at the same time. Hardware state, body-area guidance, capture quality, thermal processing, and saved context became consecutive states in one product loop rather than separate technical concerns.
Connect physical hardware to a patient mobile experience.
The mobile applications were built alongside the proprietary camera integration and Java middleware needed to translate raw capture into a usable flow. Image processing services handled thermal data while the interface guided positioning, body-area selection, and review.
Accounts, history, reminders, subscriptions, and operational services completed the product around that core. The hard part was not adding each capability; it was preserving a clear sense of progress while several systems were working underneath the same moment.
An experiment became a product people could return to.
The result was a public iOS and Android product with a guided path from opening the box to completing and revisiting a scan. The technical foundation could support a connected device without exposing the complexity of that connection to the person using it.
More importantly, Thermovision gained a coherent product model. Future features could be judged against the same question: do they make the monitoring loop clearer, more dependable, or more valuable over time?
The camera was never the whole product. The repeatable decision around the camera was.
Spicy Coconut / Product principle
A product model that can keep learning.
The durable foundation is the scan loop: hardware, guidance, processing, and history moving as one system. That gives the product room to evolve without asking users to relearn its core behavior.
