This is a submission for the Presage Challenge.

What I Built

Pausa is a short desktop breathing pause that follows you, not a timer.

Most breathing apps give you a fixed rhythm ("inhale 4, exhale 6") and hope you keep up. Pausa does it the other way round. It uses the Presage SmartSpectra SDK to read your breathing from an ordinary laptop camera, and then:

  • a green circle moves with your chest, driven live by SmartSpectra's chest breathing trace, so you can literally see your breath on screen;
  • a blue guide ring starts at your own measured pace and slows down by one breath per minute every 20 seconds, but only while you're keeping up. If you fall behind, it waits.

A session lasts 1, 2, or 3 minutes: consent → about 30 seconds of calibration → guided pause → a short summary → one click to clear everything.

In my own two-minute test, the guide stepped down from 11.5 to 8.5 breaths per minute and my measured rhythm followed it from about 11 down to 8.

Pausa is general wellness software, not a medical device. It doesn't diagnose, treat, or give health advice.

Pausa consent screen: what is measured, for how long, what is saved, and how to stop

Demo

This post is published without a demo video. The screenshots show the consent screen and data-handling panel; they do not demonstrate a live breathing measurement. The challenge requires a demo video, so this entry does not yet satisfy that requirement.

To try the experience on a supported computer, follow the setup instructions, add your own SmartSpectra API key, and run npm start. Choose a session length, read and accept the camera consent, and keep your face and upper chest in view. After calibration, the green circle follows the chest trace and the blue guide responds to the measured breathing rate. Stop with the button or Esc, then use Clear and finish to clear the summary.

For a preview without a camera or API credits, run npm run dev:mock. Its SIMULATION MODE banner identifies synthetic signals; this mode is not evidence of live SDK measurement.

Pausa data-handling panel explaining processing, network access, storage, deletion, and wellness scope

Code

GitHub logo yosef7 / pausa-presage

Pausa: a breathing pause that follows you. Built with the Presage SmartSpectra SDK and Electron for the DEV Presage Challenge.

Pausa

A breathing pause that follows you. Pausa is a desktop experience built with the Presage SmartSpectra SDK and Electron. It reads your breathing from an ordinary camera and turns it into two shapes on screen:

  • a green circle that moves with your chest, driven live by SmartSpectra's chest breathing trace, and
  • a blue guide ring that starts at your measured pace and slows down by one breath per minute every 20 seconds, but only while you are keeping up. If you fall behind the guide waits.

Pausa was built for the Presage Challenge on DEV.

Important

Pausa is general wellness software, not a medical device. It does not diagnose treat, or make health decisions, and its numbers are approximate.

Pausa consent screen

How it responds to human signals

SmartSpectra signal What Pausa does with it
breathing.upperTrace (chest movement) Moves the green "you" circle and draws the live waveform,
…

Setup is npm install, put your SmartSpectra key in .env, then npm start. There's also npm run dev:mock, a clearly labeled simulation mode for exploring the UI without a camera or credits.

How It Responds to Human Signals

SmartSpectra signal What Pausa does with it
breathing.upperTrace (chest movement) Moves the green "you" circle and draws a live waveform
breathing.rate + confidence Sets the guide's starting pace and decides when it may slow down (only at confidence ≥ 45, SmartSpectra's stability threshold)
videoOutput frames A small mirrored preview so you can frame your face and chest
validationStatus codes Plain guidance: "Keep your upper chest visible", "Too dark", "Too much movement"…
error codes Clear messages (invalid key, no internet, camera busy, credits used up); every error stops the session and releases the camera

How the SDK is integrated (Node.js / Electron, @smartspectra/node-sdk 3.4.0):

  1. The SDK is only created after the user ticks the consent box and presses Start: new SmartSpectraSDK({ apiKey, requestedMetrics: [...breathingMetrics], enableTelemetry: false }).
  2. The camera is opened natively in Electron's main process with useCamera(CameraSelection.byId(id)). Pausa lists cameras with availableCameras() and picks the built-in one, skipping virtual cameras like OBS, so the SDK always measures a real person. The renderer never gets camera permission.
  3. Each metrics packet is decoded with decodeMetrics(). Pausa keeps only the newest rate and its confidence plus the new chest-trace samples, and sends that small object to the UI.
  4. The UI plays the chest trace back with a 400 ms delay so batched samples look continuous, smooths the rate over the last five readings, and runs the "guide that waits" logic.

Things I learned along the way:

  • Framing matters more than lighting. With only my face and shoulders in view, SmartSpectra kept saying "Keep your upper chest visible" and never produced a stable rate. Sitting back so the camera saw me down to mid-chest got a stable signal (confidence 68–84) in about 30 seconds. That's why I added the camera preview.
  • Calling stopAsync() can fire a late kInvalidState error from the session that is shutting down. Pausa now ignores events from any SDK instance that is no longer the active one, so users don't see a scary error after a normal stop.
  • My Mac has four cameras (built-in, iPhone Continuity, two OBS virtual cams). Choosing explicitly by ID instead of CameraSelection.default avoids measuring a virtual feed by accident.

Prize Categories

  • Best Thoughtful Real-World Use: a short pause you can take at your desk, with consent, transparency, and data minimization built in rather than bolted on: no session files are saved by default, telemetry is off, the session has a hard time limit, and one button clears it all.
  • Most Creative or Delightful Use: your own chest movement becomes the main visual, and the guide adapts to you instead of asking you to adapt to it.

Consent and Data Handling

  • Consent first. The welcome screen explains, in plain language, what the camera measures, for how long, that nothing is saved, how to stop (button or Esc), and that Pausa is not a medical device. The Start button stays disabled until the person ticks "I understand and consent". The camera never turns on before that.
  • Visible while active. A red "● Camera on" indicator and a "What happens to your data?" panel are on screen for the whole session.
  • What is processed and where. Breathing rate and chest movement are computed on the device by the SmartSpectra SDK. Video frames are not uploaded. The on-screen preview is a 192-pixel-wide thumbnail drawn to a canvas and discarded frame by frame.
  • What leaves the computer. The SDK contacts Presage to validate the API key and count trial credits. Pausa sets enableTelemetry: false, which turns off the SDK's aggregate session telemetry (see Presage's Telemetry and Privacy docs). Pausa itself sends nothing to any server.
  • Storage and retention. By default, Pausa writes no video, images, measurement files, or localStorage; results live only in memory until the person clicks "Clear and finish" or closes the app. Developers can explicitly enable PAUSA_DEBUG=1 to print breathing rate and confidence to the terminal. Leave it off for normal use; terminal capture or redirection could retain those debug values.
  • Deletion. Stopping a session calls stopAsync() and destroy(), which releases the camera. The session also stops automatically at the chosen length, after 15 seconds without window focus, on sleep, on screen lock, and on any SDK error.
  • Sharing and AI services. No data is shared with third parties, and Pausa uses no AI or LLM services.
  • Not medical. Pausa is general wellness software. It makes no diagnostic or treatment claims, and the numbers are approximate.

Agent Session

I built Pausa with help from an AI coding assistant (Claude Code). It helped review the SDK's type definitions, debug the real-camera sessions, and write the simulation mode. I also used Codex to prepare this publication and its documentation.