Rethinking PKM Part 3: Quick Capture (with Google Keep)

TL;DR

Replace slow mobile typing into Obsidian with a dedicated quick-capture inbox to eliminate the “start of workflow” gap.

Briefing Cornell Notes

Briefing

A weak “quick capture” step is the bottleneck in many personal knowledge management systems—and this workflow replaces a clunky phone-first Obsidian habit with Google Keep as the universal intake layer. The core problem: typing notes directly into Obsidian on a phone is slow and awkward, and it breaks down entirely when the user is driving or wants to talk instead of type. After asking the Twitter community for quick-capture tools, the responses were scattered, but one app repeatedly surfaced: Drafts. Still, the user needed something that works across an Android phone and an iPad, and Drafts wasn’t the best fit for that cross-platform requirement.

Email inboxes emerged as another strong contender because they’re universal—send-to-inbox capture works from almost any app and the user even created a dedicated mailbox for this purpose. But Google Keep ultimately won, largely because it combines multiple capture modes in one place: typed notes, voice memos (with transcription), checklists, drawings/handwriting, and photo capture with text extraction. On Android, the user installs Keep widgets and relies on the smaller widget for speed, using its quick buttons to create notes, dictate, sketch, or snap pictures. A key addition is Google Assistant integration: by adjusting Google Assistant settings so Keep becomes the “notes app,” the user can dictate “note to self” hands-free—useful for situations like being in the shower or using Google Home devices—then find the dictated note in the Keep inbox.

The workflow is then completed with a weekly “processing” step. Keep functions as a temporary holding pen: nothing is meant to stay there. When it’s time to process, the user opens Keep, selects each captured item, and moves it into Obsidian. For images, the user copies/pastes the photo into Obsidian. For scanned content, Keep’s “grab image text” feature extracts text from photos or handwritten pages, which the user then copies into Obsidian as well. After processing, the corresponding Keep note is deleted to prevent clutter and keep the inbox clean.

On iPad, the user couldn’t successfully route Siri to Google Keep as the default notes app, due to Apple’s tighter ecosystem controls. Instead, the iPad setup uses Keep directly: the user can capture book pages with photo-based text recognition, dictate voice memos with transcription, and write with an Apple Pencil for quick sketches or handwritten notes. The user reports that Keep’s handwriting recognition is surprisingly good, with finger-written text sometimes recognized better than Apple Pencil writing.

The result is a two-stage system: fast, multimodal capture into Google Keep from phone, tablet, and voice assistants; then periodic cleanup and placement into Obsidian. The payoff is fewer lost ideas, less friction during capture, and a single inbox that works across devices—without paying for the service, since Google Keep is free.

Cornell Notes

The workflow fixes a common PKM weakness: quick capture is too slow or inconvenient when notes must be typed into Obsidian on a phone. Google Keep becomes the intake inbox because it supports text, voice dictation (with transcription), checklists, handwriting/drawing, and photo capture with “grab image text” for OCR. On Android, Keep widgets enable one-tap capture, and Google Assistant can be configured so “note to self” dictates directly into the Keep inbox. On iPad, Siri integration wasn’t possible, but Keep still supports photo OCR, voice memos, and Apple Pencil handwriting. Once a week, items are copied into Obsidian and then deleted from Keep so the inbox stays uncluttered.

Why does the workflow move away from typing directly into Obsidian on mobile?

Typing into Obsidian on a phone is described as slow and clunky, with app launch taking time. It also fails for hands-busy moments like driving or when the user wants to talk instead of type. Those constraints create a gap right at the start of the quick-capture process.

What alternatives were considered for quick capture, and why didn’t they win?

Community responses highlighted Drafts as a frequent favorite, but the user needed a solution that works on both Android and iPad. Todoist was shortlisted by others and has an Obsidian plugin, but the user wasn’t comfortable treating ideas as to-do items. Email inbox capture was also considered—universal and easy to send to from any app—but Google Keep ultimately offered richer capture modes in one place.

What capture methods does Google Keep add to the quick-capture workflow?

Keep supports creating quick text notes, making to-do lists via checkboxes, recording voice memos with transcription, drawing/sketching, and capturing images. A standout feature is “grab image text,” which extracts text from photos (including handwritten notes or book pages) so the user can copy the recognized text into Obsidian.

How does Google Assistant integration change hands-free capture?

The user configures Google Assistant settings so Keep is the notes app. After that setup, dictating “note to self” (including from Google Home devices) writes the dictated note into the Keep inbox. The user demonstrates both the saved transcribed text and, when using dictation, the stored voice recording.

How are captured items processed and prevented from cluttering the system?

Keep acts as a temporary inbox. The user processes items weekly by copying images or extracted text from each Keep note into Obsidian, then deleting the Keep note afterward. This ensures nothing remains in Keep to clutter the inbox.

What’s different about capture on iPad compared with Android?

The user couldn’t set Siri to route notes to Google Keep, so Siri-based capture wasn’t available. Instead, the iPad workflow uses the Keep app directly: photo capture for OCR from book pages, microphone voice memos with transcription, and Apple Pencil handwriting/sketching. Handwriting recognition is reported as fairly strong even when handwriting quality is poor.

Review Questions

What specific features of Google Keep make it better suited for quick capture than typing into Obsidian on a phone?
Describe the end-to-end workflow from capturing an idea to having it appear in Obsidian, including what happens to the original Keep note.
How does the iPad workflow differ from Android, and what limitation affected Siri integration?

Key Points

1
Replace slow mobile typing into Obsidian with a dedicated quick-capture inbox to eliminate the “start of workflow” gap.
2
Google Keep supports multiple capture modes—text, voice dictation with transcription, checklists, handwriting/drawing, and photo capture with OCR via “grab image text.”
3
Configure Google Assistant so “note to self” saves directly into Google Keep, enabling hands-free capture in situations like driving or shower time.
4
Process Keep on a weekly cadence by copying images and extracted text into Obsidian, then deleting Keep notes to prevent inbox clutter.
5
Cross-platform practicality matters: the workflow is designed to work on both Android and iPad, even when Siri-to-Keep routing isn’t possible.
6
Handwriting recognition quality can vary by input method, with finger writing sometimes recognized better than Apple Pencil in this setup.

Highlights

Google Keep becomes the temporary “inbox” for everything—then Obsidian is treated as the permanent home after weekly processing.

“Grab image text” turns photos of handwritten notes or book pages into copyable text for Obsidian.

Google Assistant can be set up so dictated “note to self” entries land in the Keep inbox automatically.