# Quick capture

{% hint style="success" %}
This experiment started on 6 Sep 2021 and concluded on 8 December 2021.
{% endhint %}

<div align="left"><figure><img src="https://1732106784-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxaQYFRJcAPhO63v4FrqX%2Fuploads%2F0c5YpmkE7OjPOkPoD0gP%2Fimage.png?alt=media&#x26;token=27f2e97e-4b5d-42fa-8629-ee66a1a6be66" alt="A screenshot of the Paper Plane iPhone app&#x27;s compose view."><figcaption><p>Paper Plane app's "compose" view</p></figcaption></figure> <figure><img src="https://1732106784-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxaQYFRJcAPhO63v4FrqX%2Fuploads%2Ff4isaUqQzDV9I8IgBHhi%2Fimage.png?alt=media&#x26;token=5b9a797f-2915-485e-b9dd-48ed74c44a20" alt=""><figcaption><p>Spark email app where cards accrued</p></figcaption></figure></div>

This was an experiment to simulate the "quick capture" and "revisit" experience I had been imagining for [the app](https://ping-practice.gitbook.io/pings/app) by stringing existing tools together into a workflow that felt somewhat cogent.

The goals here being to learn:

1. *What did I notice myself doing/needing after having a reasonable "stock" of cards?*
2. *What – if anything – might I need develop a habit of making cards?*
3. *What would I write cards about and what form(s) would cards take?*

### Impact & Conclusions

\#TODO

### Motivation&#x20;

The [DailyNotes experiment](https://ping-practice.gitbook.io/pings/experiments/dailynotes) led me to see [improving my memory and recall](https://ping-practice.gitbook.io/pings/needs) as core to helping me evolve past reflexes that were no longer useful to me.&#x20;

Drawing inspiration from flash cards, [spaced repetition](https://en.wikipedia.org/wiki/Spaced_repetition), and [lateral thinking techniques](https://en.wikipedia.org/wiki/Lateral_thinking) (namely [Oblique Strategies](https://en.wikipedia.org/wiki/Oblique_Strategies)) I sought to come up with a flow that would enable me to quickly create and revisit digital cards.

The intention I had here was to:

1. Keep [the things I was working on and towards](https://ping-practice.gitbook.io/pings/experiments/weeklynotes) present in my mind throughout the day *and*
2. Make it easy for me to "reach" for a stock of strategies (read: quotes I found inspirational, things I thought to be true, etc.) I could use in moments where I felt faced with a choice that would could bring me in or out of alignment with how I was trying to be and what I was trying to do.

### Details

I used two iOS apps for this experiment:

1. [Paper Plane](https://apps.apple.com/us/app/paper-plane-email/id1486124719) for quickly getting down resonant thoughts so that I could explore and refine them at a later time using the Spark Mail app. \[i]&#x20;
2. [Spark Mail](https://sparkmailapp.com/) for receiving the emails I sent to myself using Paper Plane.\[ii]&#x20;

\---

*i. I considered using* [*Drafts*](https://paperplane.williamhockey.com/) *instead of Paper Plane because of the edit history and metadata Drafts exposes about each draft you create. Although, I decided against using it because the actual input didn't feel quite like how I imagine the cards input to feel: fast, simple, and detached from the future.*

*ii. I set up a new, dedicated email account for receiving the thoughts I was jotting down with Paper Plane so as not to muddle this experience with the existing email workflows and habits I'd established.*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ping-practice.gitbook.io/pings/experiments/quick-capture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
