Launched this week
For decades, technology has understood what you type. Today, it starts understanding you. Life is the first cognitive wellness app, built on top of Synheart's Human State Interface infrastructure. It learns from how you type and reads your biosignals, then shows you how you're actually doing across your focus, stress, and recovery. Ask syni, your AI companion why your focus is dropping, or when you're usually at your best, and it answers from your real patterns.






Hey Product Hunt 👋 I'm Israel, founder of Synheart.
We built Life to answer a small, maddening question: you end a week feeling wrecked and have no idea why. Most wellness apps just ask you to guess — in a nicer interface.
Life doesn't ask. It reads two signals passively. How you type — rhythm, pace, focus stability, never the content of what you write — and your biosignals from a wearable. Together they give you an honest daily read on focus, stress, and recovery, without logging a thing.
Yes, we know how that sounds. So to be clear: it's not a keylogger. We never see your words — only the timing patterns. We're early, and we're still validating how well those patterns map to your state — I'd rather tell you that than hand you a number I can't stand behind yet. It all runs on your device. We don't read what you write, and we don't sell your data. That's how it's built, not just what our policy says.
Syni, the companion inside Life, already sees your state before you speak to it. So when you ask "why has my focus been dropping," it answers from your actual patterns — not a script.
I'll be here all day. Product questions, hard questions, skeptical ones especially — those are the ones I want.
Would love your feedback 🙏
@isrugeek How does it tell the difference between me being stressed and just typing fast because I'm in a hurry?
@yoseph_gebeyehu73 Fair question — it's the one I'd ask too.
The short answer: speed alone tells us almost nothing. The shape does. Being in a hurry and being stressed both make you type faster, but they don't look the same underneath. Hurried-but-fine typing stays smooth and evenly paced. Stress shows up as variance — inconsistent gaps between keys, micro-hesitations, more backspacing and mid-word corrections. And we read it against your baseline, not a universal threshold, so it's your normal we're comparing to, not everyone's.
Then the wearable is the tiebreaker. Fast typing + steady heart rate and normal HRV = you're just moving quick. Fast typing + elevated HR and suppressed HRV = actual stress. One signal guesses; two either agree or they don't.
Honest caveat: we're early and still validating how tightly these map for everyone. So that's how it's designed to tell the difference — not a solved accuracy number I'd hand you yet. If you try it and it misreads a hurried moment as stress, that's exactly the feedback I want.
@isrugeek Thanx for your response.
@isrugeek Does the desktop version read the same signals as mobile, or is it just a viewer?
@enochcodes Both, and honestly desktop is where it shines. Life runs on phone and desktop, and the desktop version reads the same signals — your typing patterns — just like mobile.
If anything it's the more powerful side: you type way more on a computer than a phone, so there's a richer, more continuous signal to read from. More keystrokes, more context, a sharper picture of your focus and stress through the day.
So it's not a viewer bolted onto the phone app — it's a full sensing surface in its own right. Use either, or both and they sync
@isrugeek Hey there! I have installed it and I have started to use it. Question: How long before the readings actually feel accurate?
@hanna_girma Great question — and the honest answer is it gets better as it learns you. Life reads your patterns against your own baseline, so on day one it's making its first guesses. Figure two weeks to a month of normal use for it to really lock onto your rhythm and feel genuinely accurate — and it keeps sharpening from there. The good news is you don't have to do anything: just use your phone and desktop like you normally would, and it's calibrating in the background.
If a reading feels off during that window, that's useful too — noticing the misses is part of how you'll know when it's dialed in. Would love to hear how it feels for you a couple weeks in.
Do I need a wearable for this to work, or does it do its thing on its own?
@yabetsz Nope, you don't need one. Life works on typing patterns alone — that's the core, and it runs fully on-device without any extra hardware.
The wearable is a boost, not a requirement. When it's there, your biosignals and your typing cross-check each other and the read gets sharper. When it's not, we lean on your typing patterns against your own baseline. Both work independently; together they're stronger.
So: install and go. Add a wearable later if you want the higher-resolution version.
Can other developers build on the Human State Interface, or is it just powering your own apps for now?
@abdi_hamid Yeah, HSI is open — it's not just powering our own stuff. Life is our first proof of what it enables, but the Human State Interface is there for anyone who wants to build human-aware products on top of it.
If you want to build with it, everything you need is at synheart.ai — docs, access, the works. Come make something that actually understands the person using it.
Happy to answer anything technical here too — infra questions especially.
@isrugeek On a scale of 1–10, how important is on-device/local processing of your biometric data vs. cloud sync for you?
@dagmawi_gebremariam For us it's a 10 — it's not a feature we chose, it's the foundation we built on.
Biometric data is different from app data. It's inference about your body and mind — hard to change, revealing if it leaks. The second "we read your state from how you type" meets "and we send it to our servers," the whole trust equation flips. So Life processes on-device by design. We structurally can't misuse what we never receive — that's a stronger guarantee than any privacy policy I could write.
The one honest tradeoff with pure on-device is continuity — history across devices, backup. Our take: local by default, and anything that ever syncs is encrypted and your choice, never the default. Trust first, convenience without giving up the trust.
Where do you land on it? Curious whether 10 is your number too :)))
@isrugeek Honestly same, once you realize what this data actually says about a person, you can't unsee it. It's not app data. It's not even health data in the normal sense. It's you, in real time. That changes everything about how you build
The typing-vs-hurried distinction and the on-device answer are honestly the two questions I'd have led with, glad those are already covered in detail. The one I'd add, since this is framed as wellness rather than just analytics: what happens when Syni's read disagrees with how you actually feel in the moment? Say it flags elevated stress during a stretch where you genuinely feel fine. Is there a way to tell it "no, I'm okay" and have that feed back into your baseline, or does it just log the mismatch silently? For a wellness app specifically, I'd worry about training people to defer to the sensor over their own read of themselves, especially early on before the calibration is dialed in.
the typing pattern thing feels kinda eerie at first but honestly the focus insights actually matched what i was feeling, syni explained why my focus dipped during a meeting and it made sense
@necatigayr32510 We hear "eerie at first" a lot, then it clicks once the read actually matches what you felt. Really glad Syni's explanation held up for you. Thanks for giving it a real shot.
The typing pattern detection is surprisingly accurate, and syni actually gave me a real reason my focus dipped yesterday instead of generic advice. Kinda wild that just from how I type it can tell when I'm fried.
@ecea0ty This is the part we're proudest of, Syni answering from your actual patterns instead of a generic script. Glad it gave you something real to work with. Thanks for the kind words