Get AI summaries of any video or article — Sign up free
2 simple questions to help you find the best note-taking app thumbnail

2 simple questions to help you find the best note-taking app

Greg Wheeler·
5 min read

Based on Greg Wheeler's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Choose a notes app by matching it to your “why” (up to three reasons for taking notes) rather than chasing the latest feature set.

Briefing

Choosing a notes app isn’t a matter of picking the newest tool—it’s about matching the app to two personal answers: why notes matter to you, and how you naturally capture and use them. The practical takeaway is simple: love and ease of use decide whether the app gets used at all, and those preferences should be derived from your goals rather than from feature lists.

The first step is to write up to three reasons for taking notes. Notes are a means to an end, so the “why” should reflect what’s at stake if notes don’t happen—remembering meaningful moments, improving thinking, creating or expressing ideas, or other personal priorities. Once those reasons are on paper, the next move is to translate each “why” into a “what would make this easy” checklist of features. For example, if the goal is to remember meaningful moments, the app should support quick capture with minimal friction, a simple interface, and fast note creation—potentially including photo attachments. If the goal is to improve thinking, features like bi-directional linking, powerful search, and ways to connect ideas become central. If the goal is to create or express, the app should make writing comfortable and support sharing or integration with other tools.

The second step asks how notes get taken in practice. Here the framework borrows from Thiago Forte’s CODE method (from Building a Second Brain), which looks at preferences across capturing, organizing, distilling, and expressing. For capturing, the key questions are what content gets saved and how easily it can be stored: book notes and quotes may call for fast text capture, while article-heavy workflows may require a web clipper; email newsletters might need forwarding or import options. Templates can also matter if different note types are captured repeatedly. Practical constraints count too—offline access, syncing across devices (phone, iPad, computer), and especially a usable mobile experience, since inspiration often strikes on the go.

Organizing preferences come next. Some people want folders and tags; others prefer a self-organizing workspace. The guidance is blunt: if a system (like avoiding folders) clashes with how someone thinks, it will slow capture and reduce follow-through. Distilling preferences cover how people refine notes—whether they rely on heavy formatting, highlighting, visual grouping, or instead prefer plain Markdown. Expressing focuses on how notes leave the app: exporting options, sharing workflows, and collaboration needs.

After turning “why” and “how” into a concrete feature list, the final recommendation is to test drive before committing. Even if research narrows the choice to a few candidates, free versions make it possible to evaluate real usability—especially for people with years of existing notes who may need to migrate. The end goal is a short list of apps that match specific requirements, not a long list of impressive features that won’t fit personal workflow.

Cornell Notes

A notes app should be chosen by matching two answers: why notes matter to you and how you actually take notes. Start by writing up to three reasons for note-taking, then convert each reason into a “what would make this easy” feature checklist (e.g., fast capture and photos for remembering moments; bi-directional linking and search for improving thinking; easy writing and sharing for creating). Next, map your note-taking style using the CODE method: capturing (web clipper/email/templates, offline access, syncing, strong mobile), organizing (folders/tags vs self-organizing), distilling (formatting vs Markdown), and expressing (exporting, sharing, collaboration). Finally, test drive a few top candidates—free versions help—before committing, especially if migrating a backlog of notes.

How does a “why” statement turn into a usable feature checklist for a notes app?

Write up to three reasons for taking notes, then translate each into “what would make this easy.” For instance, if the goal is to remember meaningful moments, the checklist might include quick capture, a simple UI, speed, and photo support. If the goal is to improve thinking, it might include bi-directional linking, powerful search, and ways to visualize patterns. If the goal is to create or express, it might include easy writing, sharing options, and compatibility with other apps. The key is that the reasons act as a filter so features are chosen for fit, not novelty.

What does the CODE method add to the selection process beyond “features”?

CODE frames note-taking preferences as capturing, organizing, distilling, and expressing. That shifts evaluation from generic capabilities to workflow fit. Capturing asks what content gets saved (quotes, articles, emails) and how (web clipper, forwarding, templates), plus practical needs like offline access and syncing across devices. Organizing asks whether folders/tags or a self-organizing workspace matches the user. Distilling asks whether the user wants heavy formatting/highlighting or plain Markdown. Expressing asks how notes are shared or exported, including collaboration needs.

Why is mobile usability treated as a make-or-break requirement?

Inspiration often appears on a phone, so the app must be frictionless on iPhone (and other devices like iPad and desktop). If the mobile experience is slow or hard to use, the user won’t capture ideas when they matter. The checklist therefore includes checking the mobile version, ensuring smooth syncing between devices, and confirming offline access if internet is unreliable.

When might “no folders” be a bad fit even if it sounds modern?

A self-organizing workspace can be appealing, but it may conflict with how someone naturally thinks about organizing. The guidance is that if avoiding folders throws the user off and makes it harder to jot down ideas, it’s not worth the tradeoff. The goal is capture and later reuse; if the system creates friction, it undermines the whole knowledge management workflow.

What should someone test during a trial period before committing to an app?

After narrowing to a few candidates, test drive the apps to confirm real usability. Focus on the features that match the user’s “why” and “how” checklist: speed of capture, whether the interface feels intuitive, how well the app handles the user’s content types (articles, emails, photos, quotes), and how organizing/distilling/expressing works in practice. Free versions are recommended for this step, and people with existing note backlogs should also consider migration needs.

Review Questions

  1. What are three reasons you take notes, and what specific features would make each reason easier to achieve?
  2. Which parts of CODE (capturing, organizing, distilling, expressing) most strongly match your current workflow, and where do you expect friction?
  3. If two apps both have many features, what criteria would you use to decide which one you’ll actually keep using?

Key Points

  1. 1

    Choose a notes app by matching it to your “why” (up to three reasons for taking notes) rather than chasing the latest feature set.

  2. 2

    Translate each “why” into a “what would make this easy” checklist of concrete capabilities (e.g., fast capture, photos, linking, search, sharing, writing comfort).

  3. 3

    Evaluate note-taking style using CODE: capturing, organizing, distilling, and expressing—so the app fits how you work day to day.

  4. 4

    For capturing, verify practical essentials like quick input, templates/web clipping or email saving, offline access, and reliable syncing across phone, iPad, and computer.

  5. 5

    Treat mobile usability as critical; if the iPhone experience is slow or awkward, idea capture will suffer.

  6. 6

    Pick an organizing system that matches your brain (folders/tags vs self-organizing); if it disrupts capture, it’s a poor fit.

  7. 7

    Test drive a short list of apps—free versions help—before committing, especially if you need to migrate existing notes.

Highlights

The best notes app is the one someone will actually use—love and intuitive usability come before feature comparisons.
Your reasons for taking notes should act as a filter; otherwise most features won’t get used or will get in the way.
Mobile performance and syncing aren’t optional details—they determine whether capture happens when inspiration strikes.
CODE turns app shopping into workflow matching: capturing, organizing, distilling, and expressing.
Free trials make it possible to validate real fit before migrating a backlog of notes.

Topics

Mentioned