In beta · iOS & Web
A private voice app for saying the messy version and making sense of your recordings later.
For People who think out loud and want to find what they said later, with the original recording as the evidence.
iOS / Web · Notes reviewed 20 September 2026
A private voice archive that remembers the context, not just the recording.
A long voice memo is easy to save and hard to revisit. Automatic summaries can be worse when they invent a personal trait, overstate a pattern or lose the evidence behind a sentence. Capturing the moment must also succeed independently of a network request or an expensive model call.
Smart Rant makes recording a thought immediate and makes the archive useful later. It is designed around a person’s own moments, people and recurring subjects rather than forcing every recording into a journal template or a coaching conversation.
01Screen · Phone
Normal, Private or Burn, chosen before anything is processed.
App Store capture with fictional sample recordings.
02Screen · Phone
Past: every moment, searchable by what you said.
App Store capture with fictional sample recordings.
03Screen · Phone
A moment: the original voice, the words, and what it connects to.
App Store capture with fictional sample recordings.
04Screen · Phone
Ask: an answer that points back to the recordings it came from.
App Store capture with fictional sample recordings.
05Screen · Phone
You: patterns only where the recordings support them.
App Store capture with fictional sample recordings.
How it is used
Interactive demo Searched in your browser
Ask something about these recordings. The answer is only what they say, quoted, with where each quote came from.
Recordings
Lisbon for the anniversary
Trip budget
Sintra day trip
Flights booked
Pricing question
Pitched Leo
Knee twinge
Knee is fine
Ran the full 10K route
Decided to stay
A good call with my brotherPrivate
This moment is Private, so Ask doesn't use it.
Try
01 · System
Capture never waits for the network. Everything after it is a durable job.
Select a part to see what it is responsible for and what it connects to.
SwiftUI capture that commits the recording locally before any follow-on work.
Trade-off: Mode is persisted asynchronously, so an interrupted capture is a failure case to recover from.
→ TypeScript API: consented upload
Next.js with Clerk sign-in, over the same archive.
→ TypeScript API: archive requests
Accepts uploads into private object storage and records work.
→ Durable job queue: recorded job
Token-bound leases, heartbeats and classified retries in Postgres.
→ Worker: leased job
Transcription, normalization, embedding, extraction and thread refresh as separate stages.
Trade-off: It checks consent, revision and analysis epoch first, so a stale worker cannot publish into a newer privacy state.
→ Postgres + pgvector: evidence and vectors
Transcripts, structured evidence and vectors for semantic and lexical recall.
→ TypeScript API: quoted sources
The native client uses SwiftUI and a durable local archive. The web application uses Next.js and Clerk. The current backend is a Node/TypeScript API and worker over Neon Postgres with pgvector and private object storage; older Supabase material is historical, not the current deployment design. Work is recorded in a durable database queue with token-bound leases and revision/analysis-epoch checks. The pipeline separates transcription, normalization, embedding, extraction, temporal processing, thread refresh and evaluation.
02
The capture controller creates a durable take before recording audio and commits the local recording before invoking follow-on work. Recoverable files remain available when finalization fails.
Normal, Private and Burn have different processing rules. Private recordings can use cloud transcription only through the separate explicit consent path; that is not permission to include them in normal archive analysis.
Archive questions use semantic and lexical retrieval, structured evidence and source-grounded quotations. Unsupported or insufficient evidence should produce a limited answer rather than a confident story.
Workers claim token-bound jobs, heartbeat while running, classify retryable failures and record outcomes. A stopped process is recoverable through the queue rather than through wishful post-response work.
03
Native capture on the phone, with a web app beside it.
SwiftUI · Next.js · Clerk
An API and worker over Postgres with vector search.
TypeScript · Neon PostgreSQL · pgvector
Private audio storage, a durable queue and web hosting.
Private object storage · Durable job queue · Netlify web hosting
04
Approach
The capture state machine prepares durable storage before the first audio frame and treats save completion separately from processing completion.
Trade-off
The extra states and recovery paths are failure cases of their own. A successful UI animation must not be the only evidence that the recording is safely stored.
Approach
Extraction, retrieval and generated wording are checked against source material. Recurrence and trait-like statements require more than one anecdote, and the wording guard rejects several forms of unsupported interpretation.
Trade-off
Regex and schema checks are conservative heuristics, not a semantic proof. They can reject useful phrasing and miss a paraphrased overreach, so they can be wrong in both directions.
05
Links checked 21 September 2026
Answers quote the source notes and cite them.
