---
title: "Capture First, Sort Later"
date: "2026-08-04"
canonical: "https://raytally.com/en/ideas/2026-08-04-idea-0ff1f331/"
generator: "RayTally · dev-prompt-v4"
signal:
  query: "How do you capture important thoughts before they disappear?"
  observed_at: "2026-08-04T00:33:33.528Z"
sources:
  - url: "https://www.reddit.com/r/ADHD/comments/1vetrnh/how_do_you_capture_important_thoughts_before_they/"
    boundary: "Published at 2026-08-03T23:38:04.000Z. Observed at 2026-08-04T00:33:33.528Z."
  - url: "https://developer.apple.com/documentation/appintents/app-shortcuts"
    boundary: "No publication timestamp is present in the source record."
  - url: "https://developer.apple.com/documentation/eventkit/creating-events-and-reminders"
    boundary: "No publication timestamp is present in the source record."
  - url: "https://apps.apple.com/us/app/braintoss/id576226036"
    boundary: "No publication timestamp is present in the source record."
notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief."
---

[Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-08-04-idea-0ff1f331/)

Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting.

You are a senior product engineer. Turn the product idea below into a locally runnable MVP.

## Idea

Capture First, Sort Later
Capture a thought by voice the moment it appears, then confirm it that evening as the right reminder, calendar item, or note.

## Product concept

When a thought first appears, the user holds an earbud control or lock-screen button and says, “Remind me Friday to send Xiaolin the sample.” The product immediately confirms that the raw audio was received with haptic feedback, without asking the user to decide whether it belongs in reminders, a calendar, or notes. On the subway, while walking, or when a small task comes to mind, capture is not interrupted by a form. In the background, it extracts times, people, places, and actions from the speech while retaining both the original utterance and its transcript. Complete items wait in a unified inbox, and the user can set an evening review, such as 8:00 PM each day. The review screen pre-fills “book a dentist appointment,” “buy cat food,” and “have dinner with Sister Chen next week” as a reminder, to-do, and calendar draft, respectively. Items missing essential information are grouped for questions during that review, such as “What date should this reminder use?” or “Should dinner with Sister Chen take up calendar time?” After confirmation, items are written according to the user’s chosen rules into Apple Calendar, Google Calendar, Reminders, or a notes app. Each item shows where it was sent, making it easy to edit or undo. The first version handles only spoken Chinese to-dos, appointments, and quick notes. It will not send messages on the user’s behalf or infer vague dates. The product preserves the thought first, then sorts it during a dedicated review window.

## Why now (backed by facts)

On August 3, an r/ADHD user publicly asked for help: speaking was faster than unlocking and typing, yet thoughts still disappeared while choosing between reminders, calendar, or notes, and items ended up scattered across Apple and Google. This puts the break between capture and filing directly in front of users, making the problem immediately recognizable even to people who already use a voice assistant.

## Direction (model inference, not independently verified)

Target user: Best suited first to people who often think of tasks while walking, commuting, or using both hands. They already speak to Siri or a voice recorder, but hesitate when they must first choose between a reminder, calendar, or note. The moment that matters is the few seconds when the thought is still intact but unlocking the phone and filling out a form is inconvenient. A scheduled review works best for people willing to clear an inbox once a day, rather than those expecting the system to decide everything automatically.

Minimal entry point: Start as a native iPhone app. Use App Intents to connect with Siri, Shortcuts, and the Action button on supported devices. Recordings enter a local queue and receive immediate haptic confirmation without waiting for transcription. Use the Speech framework for Chinese transcription, while always retaining both the original audio and text. The review screen extracts only actions, people, places, and explicit times; vague dates must trigger a follow-up question. After confirmation, use EventKit to write to Apple Calendar or Reminders and save the target item identifier to support undo. Add Google Calendar only after the local workflow is stable.

The strongest case against: Capturing a voice note does not make it actionable. In Chinese, phrases such as “next week,” “later,” and “find Xiaolin” often lack a date, identity, or clear action boundary; too many follow-up questions could turn evening review into another backlog. Writing to the wrong calendar can create scheduling conflicts, while writing to the wrong reminder list can erode trust in automatic routing. A failure in lock-screen capture, microphone permissions, calendar permissions, or background upload would break the promise conveyed by the “captured” haptic signal. Original recordings may also contain names, clients, and health information, so the rules for local storage, deletion, and cloud transcription must be explicit. If most entries still need to be rewritten one by one, this is only a layer of organization added on top of a voice recorder and ecosystem expansion should pause.

These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty.

## Punching above weight (model inference)

Recruit the first users from ADHD and GTD communities where people raise the problem of not capturing thoughts in time. Distribute a shortcut that can be bound to the Action button, so users can first experience press-and-hold capture. Product demos should show more than automatic classification: follow a single utterance from haptic confirmation through evening filing. Including the correction flow after a misrouted item in short videos will better reach productivity-tool users who value control.

## Competitors & gaps (model inference)

- Braintoss: Braintoss already supports fast voice, text, and image capture, sending items to email or a webhook. It also offers a share extension, Apple Watch access, transcription, and delivery retries, so the capture step is already mature. For people who use email as a unified inbox, this is a simple, direct workflow that can continue routing items through email rules. The opening is that its public materials still center on sending content to a destination. It does not prefill each voice capture as a reminder, to-do, or calendar draft, nor does it offer batch confirmation for missing dates and ambiguous people. This product can retain the original phrasing, transcript, and destination, then write items into the system only after confirmation. The real differentiators must be reversibility, a low misfiling rate, and review efficiency. If users still have to copy items over manually, Braintoss’s established entry points will be more appealing.
- Apple Shortcuts, Reminders, and Calendar: Apple’s native stack already covers entry points including Siri, Shortcuts, and the Action button. Authorized apps can also use EventKit to create and edit calendar events and reminders. Advanced users can build their own dictation shortcut and send text to a fixed list or calendar. The setup is free, system-level, and has a clear permissions path. For a single, explicit command, users usually do not need another tool. The gap appears before the thought has taken shape: users must still decide where it belongs and fill in its date and type on the spot. Shortcuts can chain actions, but do not inherently provide a unified inbox, original-audio comparison, or an evening batch-clarification flow. This product postpones the decision and records the target item for every write. If someone only needs to say, “Remind me about something,” the native option is already sufficient and should not be treated as a core paid user.

## How it makes money (model inference)

Monthly subscription. The free tier includes on-device capture and manual review; the paid tier unlocks cloud transcription, cross-device sync, and Google Calendar integration. Avoid per-item pricing so users never have to weigh the cost before recording a thought.

## Source context

Theme: Voice capture before a thought disappears
Trigger Web Trend observation: u/switzerswish（r/ADHD） — How do you capture important thoughts before they disappear?

This is one observation bounded by its publication and capture times. It is not evidence of market size or a broad trend and only explains “why now.”

## Sources

- How do you capture important thoughts before they disappear? (https://www.reddit.com/r/ADHD/comments/1vetrnh/how_do_you_capture_important_thoughts_before_they/)
- App Shortcuts (https://developer.apple.com/documentation/appintents/app-shortcuts)
- Creating events and reminders (https://developer.apple.com/documentation/eventkit/creating-events-and-reminders)
- Braintoss App (https://apps.apple.com/us/app/braintoss/id576226036)

## Deliverables

- Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery.
- Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary.
- Do not show unverified market numbers in the UI or API.
- Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge.
- If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code.
- If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype.
- When done, explain what changed, how to run it, and how to verify it.
- Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.