This is a submission for the Presage SmartSpectra SDK Challenge
What I built
Dolowcool is a desktop message composer with one odd rule: if your pulse or breathing jumps well above your own normal, the "Open in email" and "Copy message" buttons stop working until you've settled.
You can keep typing the whole time. Write the angry version, get it out of your head, save it as a draft. What you can't do is move it into your email client while your body is still running hot. When the readings come back down and stay down for eight seconds straight, the buttons return and the decision is yours.
It does not guess what you feel. It never says "you're angry". It compares two numbers against a baseline it learned from you in the first 20 seconds of that session, and tells you exactly which number tripped the pause. There's a "Why is this paused?" panel with your baseline, your current values, the rule that fired and the rule that will release it.
Nothing is ever sent automatically. The only exit is a mailto: link that you click, and even that opens a draft in your own mail app for you to review.

Simulator build, so this screenshot contains no face or camera data.
Demo
Code
https://github.com/Agozie180/dolowcool
Run it from source. The two ways to launch it (with a camera, or with the camera-free simulator) are in the How to run it section at the bottom of this post.
How It Responds to Human Signals
I request exactly two SmartSpectra metrics, PULSE_RATE and BREATHING_RATE, and nothing else. I left HRV and expressions out on purpose: the idea only needs two signals, and every extra one is one more thing to interpret and one more thing to explain to the user.
Capture. The SDK owns the camera in Electron's main process at 1280×720 / 30 fps (sources/presage.js). The renderer only receives validated metric events and a throttled preview that stays in memory. The API key never reaches the UI process.
The score. Once a stable baseline exists, I compute two relative rises: pulse rise divided by 15%, and breathing-rate rise divided by 30%. The larger one wins, and an exponential moving average smooths it. At 1.0 the actions pause. To release, the score has to drop to 0.5 or below and stay there for eight continuous seconds. Two different thresholds, so one lucky low sample can't flip the button back and forth. The lock engine itself is a pure module with no Electron in it (renderer/lock.js), which is why I could test it properly.
The rule I cared about most: missing data is never calm. If a metric is absent, stale, or below SmartSpectra's confidence floor (40 for pulse, 45 for breathing), the engine pauses, wipes the recovery timer, and makes you earn a fresh continuous stretch. A gap of more than 2.5 seconds between samples counts as a break. SmartSpectra's validation states (no face, too dark, too much motion, low frame rate and so on) are turned into plain instructions like "Step back until your face, shoulders, and upper chest are visible."
Two things broke on real hardware, and both changed the design:
Frames over IPC. My first version captured in the renderer and copied raw 720p frames to the main process. On my Windows machine with an HP webcam that couldn't hold the frame rate, and the SDK ended the session with error code 14. Dropping to 640×480 proved the copy was the bottleneck but ruined the framing. Moving capture into the SDK's native main-process path fixed it.
Pulse and breathing arrive in separate packets. I had treated every packet as a complete pair, so the UI flickered between "pulse missing" and "breathing missing". Now each metric is cached independently and expires after eight seconds, so a pair is evaluated together without ever letting stale data pass as current.
I also want to be straight about live reliability. The strict acceptance run (npm run test:live, which only passes if both metrics clear their confidence thresholds). Two later reruns failed closed, which is what the test is supposed to do: one hit a low camera frame rate, the other got breathing above threshold but pulse confidence peaked under 40. The app stayed paused both times. Framing and light matter a lot. The full run log is in LIVE_TEST_REPORT.md.
Prize Categories
Most Creative or Delightful Use. Most camera-vitals demos end on a chart. I wanted the reading to change what your hands can do. The send step is the one place where people regret speed, so that's where the signal lives. The recap at the end shows how long you waited, drawn as a small timeline in memory, and it's gone when you close it.
Best Thoughtful Real-World Use: Regretted messages are an everyday, non-medical problem: anyone who has ever hit send at the wrong moment is the user. A few choices came straight from thinking about those users: the baseline is personal rather than a population average, the override exists but needs a continuous 3-second press-and-hold, Save draft is always available, and the whole thing admits it's a speed bump rather than a lock.
Consent and Data Handling
Consent. The camera stays off until you tick an unchecked box that spells out the data flow and then press Start live camera session. A visible Stop camera & end session button releases the camera. Starting again asks for consent again. The preview is always on screen while sensing, so there is no covert monitoring.
On-device vs network. Presage's documentation says all metric computation runs on-device and that its backend is contacted only to authenticate the API key and validate the subscription (SmartSpectra docs). Dolowcool therefore needs internet and an API key, and it does not claim to be offline or anonymous.
Telemetry. SmartSpectra telemetry is on by default in the SDK, so Dolowcool passes enableTelemetry: false unless the app owner sets DOLOWCOOL_TELEMETRY=1. Presage describes what telemetry contains in SDK Telemetry & Privacy.
Storage. Frames, pulse, breathing, baseline, score and recap are never written to disk. The one exception is the optional message draft in Electron's localStorage, and Discard local draft deletes it.
Sharing. No AI service touches your text, and there's no Gmail or Outlook API. The email handoff is a mailto: link opened by your click.
No medical claims
No diagnosis, no treatment advice, no emotion labels, no medical decisions. The 15% and 30% reference rises and the 1.0 / 0.5 / 8-second values are interaction-design starting points. They are not clinically validated.
How to run it
Dolowcool is a desktop prototype that you run from source. You need Node.js 22.12 or newer. Supported: Windows x64, macOS Apple Silicon, Linux x64/ARM64 (glibc 2.35+).
git clone https://github.com/Agozie180/dolowcool.git
cd dolowcool
npm install
Step 2. Pick a way to launch
A. Simulator, no camera and no API key. Fastest way to see the whole flow:
npm run start:sim
The top-right badge reads Developer simulator · Simulated. Everything here runs through the same lock engine as the live version, but the numbers are fake.
B. Live camera with SmartSpectra. You need a SmartSpectra API key. Copy .env.example to .env and fill it in:
SMARTSPECTRA_API_KEY=your_key_here
DOLOWCOOL_TELEMETRY=0
DOLOWCOOL_CAMERA_ID=
(Leave DOLOWCOOL_CAMERA_ID empty to use the default camera.) Or set the key for one session in PowerShell:
$env:SMARTSPECTRA_API_KEY='your_key'
Then
npm start
The badge should read Live SmartSpectra · ready. If it says API key needed, the key wasn't picked up.
For a good live reading, sit with your face, shoulders and upper chest in frame, with soft light in front of you, and stay comfortably still. Don't force fast breathing. Pulse and breathing take a while to become reliable.
Step 3. Consent
Read the data-flow notes, tick the checkbox, then press Start live camera session. The button stays disabled until you tick.

Step 4.Let it learn your baseline**
For about 20 seconds it collects a stable baseline. You can already type in To, Subject and the message box. The email button reads Open in email when settled and stays inactive. If a metric drops out, the baseline restarts and the screen tells you why.

Step 5. The pause
When pulse or breathing rises far enough over your baseline, the score passes 1.0 (the "× threshold" number). The button changes to Paused until settled, Copy is disabled, and the panel names the driving signal. Open Why is this paused? to see baseline vs. now, the pause rule and the unlock rule.
Step 6. Settled
Sit still and breathe normally. The score has to fall to 0.5× or lower and stay there for 8 continuous seconds. Then you get Settled. Your choice is open. and Open in email and Copy message come back. Open in email hands the draft to your default mail app. Nothing sends by itself.

Step 7. End session
Press Stop camera & end session. The camera is released and you get a memory-only recap of how long you waited.
Stimulator shortcut
In simulator mode, press Run demo scenario · about 60 seconds in the Demo Control card. It plays baseline, a rise, a pause, settling and the unlock automatically. The slider lets you dial the simulated arousal yourself.

Top comments (0)