I built an AI therapist that lives in your pocket — and I'm terrified no one will find it
Hi Indie Hackers,I'm Alessandro. Last month I published my first app on the Play Store. It has 2 downloads. One is me. The other is... also probably me on a different device.Here's what I built anyway.LifeContext AI is a personal AI assistant with persistent memory that runs completely offline on your Android phone. No cloud. No account. No data ever leaves your device.Why I built this: I wanted an AI that actually remembers me. Not the "hello, how can I help you today?" amnesia of ChatGPT. I wanted it to know I struggle with anxiety on Sunday nights. That I'm working on a side project I never talk about. That I set a goal three weeks ago and forgot.So I built:The technical bet: I run local LLMs directly on the phone (Qwen, Gemma, SmolLM). The free version uses Qwen 3.5 2B. For €6.99 one-time you unlock bigger models. No subscriptions. I hate subscriptions.My honest situation:What I'm actually asking: Not pity. Reality checks.If this resonates with you, here's the Play Store link. I'd genuinely love feedback — even brutal. Especially brutal.Thanks for reading. This community is why I didn't quit last week.
Before you chase more distribution, check whether ChatGPT names you on the buyer questions. Same five questions in a fresh chat. Log you, competitor, or nobody.
Results are in, and they're exactly what I expected — but worse.5/5 crickets. ChatGPT doesn't know I exist. More interesting: it doesn't know anyone in my space exists.When asked for "offline AI assistant," it recommends Replika (cloud). When asked for "private therapist no servers," it recommends Wysa and Youper (both cloud). When asked for "local LLM," it mumbles about Pygmalion and generic "GPT-based models" with no specifics.So the problem isn't just that I'm invisible. The entire category of "actually offline, actually local, actually private" is invisible. ChatGPT literally cannot distinguish between "claims privacy" and "is architecturally incapable of sending data anywhere."This feels like either:Which side would you bet on? And if it's the first — what's the fastest way to make "actually offline AI" a thing ChatGPT (and humans) can name?
has anyone who isn't you written about LifeContext anywhere — a forum post, a review, anything? If that number's near zero, I'd bet that's the real bottleneck, not the model. It's not hiding you. There's just nothing to surface yet.
You're right — near zero mentions outside my own posts. That's the bottleneck.I'm balancing two things: building in public enough to be discoverable, and not handing the technical roadmap to someone with more resources and more speed. The core architecture isn't complicated to describe, but the specific optimizations that make it viable on mid-range hardware took months of iteration. I'm protective of that.That said, I hear you. The "nothing to surface" problem is real and it's mine to solve. I'm starting with the comparison series ("claims vs actually offline") to create mentions that aren't just me talking about myself. Those pages will exist, they'll be quotable, and they'll name the distinction whether or not they name the app.On the technical side: I'm testing a performance optimization that could make the 4B model viable on more devices. If it works, that's another story worth telling. If it doesn't, I'll write about why it failed and what I learned.The honest timeline: I'm slow because this isn't my full-time job yet. But I'm not stopped.
Bet on the unnamed category. ChatGPT fills the gap with cloud apps because nobody named the other end. Fastest path is the same five questions every week plus pages that say the distinction in plain sentences.
Betting on it. "Actually offline" — I'm building the proof and the name.Weekly five-question log starts now. First comparison page this week.I'll report back when crickets turn into recognition. Thank you for the push.
Good. The name can wait until the log has a row that is not nobody. Come back when the first comparison page is live. That is the proof.
This is a fascinating test — and slightly terrifying. I haven't checked this at all.Running it now. Five fresh-chat buyer questions, logging whether I show up, competitors show up, or it's crickets.My honest guess before I start? Crickets. I have zero web presence beyond the Play Store page, zero PR, zero mentions. If ChatGPT knows I exist, it's probably from scraping IH itself in the last hour.Will report back with results. If it's all competitor names, do you have a playbook for breaking into that training-data visibility? Or is it a long game of content + mentions + time?
Crickets on week one is normal. Training data is slow. Mentions on pages models already cite, and the same five questions every week. If you want the weekly sheet without building it, it is on my profile as a free five prompt snapshot.
Good to know week one is baseline, not verdict. The "same five questions every week" approach is smart — I'll set a recurring reminder and track whether I'm moving from crickets → competitors → me.Checked your profile, grabbed the snapshot. Will run it and see what patterns emerge.One thing I'm realizing from this whole thread: the gap between "claims offline" and "architecturally offline" is so wide that most people (and apparently most AI models) don't even see it. That feels like the real positioning challenge — not convincing people to try my app, but convincing them that "offline" is a spectrum and most apps are at the wrong end of it.If you were building content around that distinction, where would you start? One big manifesto post, or a series of smaller "actually vs. claims" comparisons?
A series of small comparisons. One manifesto is a speech. Three pages that say claims offline versus actually local, then run the same five questions after each. That is how a category gets a name.
This is the blueprint I needed. Not one manifesto — a series of small, falsifiable comparisons.So the structure is:The methodology itself becomes the category. "Actually offline" isn't what I say — it's what the test proves.Starting this now. First comparison goes live this week. Thank you for the framework — I'll credit you when it resonates.
Credit the test, not me. One comparison a stranger can rerun is the page models actually pick up.
This is exactly the kind of brutal I needed. Thank you.You're absolutely right on the title — I led with "therapist" because it's what I personally wanted, but I can see now how it triggers the wrong frame for the people who'd actually value this. "Offline-first with persistent memory" is the real hook, and therapy is just one use case it enables.Your point about 2 downloads being absence of distribution, not product failure — I needed to hear that. I've been reading despair into a number that I never actually tried to change.The thread strategy is brilliant. Instead of "here's my app," show up where people are already annoyed about ChatGPT's amnesia and share what I learned making local memory actually work. I can feel the difference already.Quick question: if you were rewriting the one-sentence description for the Play Store or a landing page, would you go with something like:"100% offline AI assistant with persistent memory. No cloud, no account, no subscription — your conversations stay on your device."Or would you structure it differently?Also: would a technical write-up on quantizing 4B models to run on mid-range Android RAM be interesting to the IH crowd, or better suited for r/selfhosted / r/localLLaMA?Thanks again — this shifted how I'm thinking about the whole thing.
On the one-liner: your version is close but it's four claims in a row, and a reader skims it as a feature list rather than a promise. The negatives are doing the work, so I'd lead with the consequence and let the specs follow.
Something like: "An AI assistant that remembers you and never sends a word off your phone. No cloud, no account."
"Never sends a word off your phone" is concrete enough to be falsifiable, which is what makes it credible. "100% offline" reads as marketing because everyone says it. Also drop "no subscription" from the one-liner — it's a real advantage but it belongs in the pricing area, and putting it next to the privacy claim makes the whole thing sound defensive.
One note for the Play Store specifically: the first 30 or so characters are all most people see. Front-load "Remembers you. Stays on your phone." and put the rest in the long description.
On the write-up: do it, and post it in both places, but not the same piece. r/LocalLLaMA wants the numbers — which quant, tokens/sec on which chipset, RAM ceiling, what broke at 4-bit, what you tried and abandoned. They'll be unforgiving about vagueness and that's exactly the audience that will tell you if you got something wrong. IH wants the decision story: why on-device at all, what it cost you in capability, how you decided the tradeoff was worth it. Same research, different question being answered.
The r/LocalLLaMA one is more valuable to you right now, honestly. It's a group of people who already believe the thing you're selling and are actively looking for apps that do it properly. Just go in with the technical post and no pitch — let the app be a footnote.
Update: checked LifeContext's actual RAM usage on my OnePlus 12 — ~495MB with Qwen 3.5 4B loaded. For context, that's barely above TikTok (~396MB) on the same device.This makes me wonder: should I lead the r/LocalLLaMA post with this efficiency angle ("4B model under 500MB") or would that read as cherry-picked? I can test on a mid-range device if the community values those numbers more.
You asked for brutal, so: the title is working against you. "AI therapist" is the one framing that makes a privacy-conscious person hesitate and makes a cautious person think about liability. The actual differentiator you buried is "runs entirely offline, nothing leaves the device, no account." That's the sentence people search for and repeat to friends. Lead with the offline part and let the therapy use case be one example of it.
Second thing: 2 downloads at one month with no marketing isn't a signal about the product. It's just the absence of any distribution. Don't read despair into a number that hasn't been given a chance to mean anything.
The place to go: people already complaining about the exact thing you fixed. Threads about ChatGPT forgetting context between sessions, and privacy subs/forums where people specifically want local models on-device. Those readers don't need convincing that persistent memory or offline matters - they're already annoyed about it. Show up in those conversations with what you learned making it work, not with a pitch. The RAM optimisation problem you're hitting is genuinely interesting content for that audience.
One more: €6.99 one-time for bigger models is a fine offer, but "no subscriptions" is a real selling point right now and you're only mentioning it in passing. That plus offline is your whole positioning.
The fact that you shipped a local LLM onto a phone as a first app is not a small thing. The build isn't the problem.
Edit: formatting got a bit mangled on mobile, so here's a cleaner read:Why I built this: I wanted an AI that actually remembers me. Not the "hello, how can I help you today?" amnesia of ChatGPT.What it does: 🧠 Persistent memory — recalls past conversations, not just the last prompt 📖 Journal with AI insights — patterns you might miss ⏰ Time Capsule — write to your future self 🆘 Difficult moments toolkit — breathing, grounding, emergency contacts 💪 Proactive coaching — daily check-ins that don't feel roboticThe honest situation: • 2 downloads • €0 revenue • Bootstrapped, solo, no marketing budget • Optimizing RAM for phones I can't afford 😅What I'm asking:Brutal honesty welcome. Especially brutal.