for ObsidianSimple Memo Obsidian integrationMedia kitMarkdown tool
EN

For writers and reviewers

Product facts, visuals, and the original sources.

A compact kit for covering email-to-self capture, Siri, Obsidian workflows, or the operations of a small app. Descriptions are ready to copy; setup conditions and source data are linked alongside them.

Updated 1 October 2026 · Maintained by the Simple Memo development team

A short product description

Simple Memo - for Obsidian is an independent iPhone app for capturing a thought and sending it to your own email address, with optional appending to an Obsidian vault. It supports typed notes, Siri capture, and Apple Watch. With a compatible folder selected, the app writes to the vault on the iPhone without an Obsidian community plugin. Email delivery and vault appending are separate paths: offline email waits in the Outbox, while folder-based appending can work locally. A vault must be accessible in the Files picker for the direct-folder method. The app also publishes a dated operations ledger describing work performed by AI, human interventions, and failures. Those records are available for inspection and reuse as research material. Simple Memo is developed by YURIKA, K.K. It is not an official Obsidian product and does not claim to be an official successor to Captio. Setup instructions and limitations are available on its website.
Download description (TXT)Obsidian setupSiri setup

Check the facts before reviewing

ItemWhat the product does
ProductSimple Memo - for Obsidian
DeveloperYURIKA, K.K.
CaptureTyped notes, Siri and Apple Watch
ObsidianOptional; no community plugin required
Direct-folder requirementA writable vault folder accessible through Files
Offline behaviorEmail queues in Outbox; folder append can run locally

The vault picker and the URL-scheme fallback behave differently. With no compatible folder selected, the fallback may open Obsidian. Apple Watch hands off the append to the iPhone. Cloud synchronization can add delay. Normal email sending is not end-to-end encrypted email; local encryption and transport security are separate properties. Read the privacy architecture before making privacy claims.

Use the current setup guide and product page for availability and pricing. This kit deliberately avoids a competing-app speed table: warm and cold starts, different definitions of “ready,” and human actions are not interchangeable.

Setup screens and explanatory videos

These are published Siri setup screens. They show the setup guide; their labels are not a promise that every OS version presents the same interface. Phrases in the images such as “Phone stays pocketed”, “Works the same on every AirPods” and “‘Hey Siri’ always works” are earlier wording, not a guarantee for every device state. See the Siri guide for the current conditions.

Siri setup screen 1
Open original PNG
Siri setup screen 2
Open original PNG
Siri setup screen 3
Open original PNG
Japanese explanatory animation of the normal mode, which keeps a memo both in your email and in the selected vault. The vault append does not travel through the email. This is an illustration, not a timed recording from an iPhone.
Obsidian illustration (MP4)Siri illustration (MP4)App icon (PNG)

The Siri illustration is a slideshow of the Japanese in-app guide screens. It is not a recording of email receipt or vault storage, and its on-screen phrases meaning “arrives in email and Obsidian at the same time” and “not lost offline” are earlier wording. Email and the vault are separate paths; see the Siri guide.

Three angles with material to inspect

Using the material

When covering Simple Memo, these product descriptions and original illustrations can be used with their context intact. Identify explanatory animations as animations. Screenshots may contain third-party trademarks; this kit does not grant rights in those trademarks or imply endorsement. Please retain the dates and denominators when citing research, and link readers to the relevant source page.

For additional screenshots, an interview, or a reproducibility question, contact the developer. Editorial conclusions and link choices belong to the publisher.