Getting started
How to use nodes
This is the whole thing in one page. The first four sections get you from nothing to a working daily habit — that is genuinely all you need, and you can stop reading there. Everything after it is optional and will still be here in a month.
What this is
nodes is a flashcard app. You write a question on one side and the answer on the other, and the app decides when to show each card again — just before you would have forgotten it. That scheduling is the entire point. Reviewing everything every day does not scale past a few hundred cards; reviewing the right twenty does.
A day with it looks like this: you open the app, one deck says it has cards due, you press Start, you answer cards until it says you're done, and you close it. Ten minutes, most days. The app owns the question of what and when; you only ever answer do I know this.
It is a closed beta made by one person. Things will be rough in places. If something is broken or confusing, use Report a bug in the app — that goes straight to me and it is the fastest way to get it fixed.
Install it
Desktop is the real app: you can write cards, import, change settings, and study. The web version is for reviewing when you're away from your own machine.
macOS Invite code
You need an invite code — ask me for one. Then go to the download page, enter the code, and download the zip.
Unzip it, move Nodes.app to your Applications folder, and then run this once in Terminal:
xattr -dr com.apple.quarantine /Applications/Nodes.appThat line is not optional and it is not a workaround for anything shady. The build is signed ad-hoc rather than with a $99/year Apple Developer certificate, so macOS quarantines it and refuses to open it with "Nodes is damaged and can't be opened" — which looks like a corrupt download but isn't. The command clears the quarantine flag. You do this once; later updates download from inside the app and are never quarantined.
Windows Store invite
Windows ships through the Microsoft Store as a private beta, so there is no public listing to search for — ask me and I'll send you the Store invite. Once it installs it updates itself like any other Store app, and there is no quarantine step.
The web version No install
nodes.cards/app needs no install and works on a phone. Sign in with the same account and your decks are there.
It is deliberately review-only. You can sign in, see your decks, browse your cards read-only, and do reviews — which sync back. You cannot write or edit cards, import, manage decks, change settings, run an exam, generate cards, or see the heatmap. Use it to keep a streak alive on a train; do the real work on desktop.
Get your cards in
An empty app does nothing for you, so this is the step that matters. There are three ways in and they are not equally good for everyone.
-
Bring a deck from Anki
If you already use Anki, this is your route. Export a deck as an
.apkgand drag the file onto the nodes window. Your cards, your media, and — importantly — your review history come across, so the scheduler doesn't start from zero on cards you have known for a year. -
Try the demo deck
A dozen cards that explain the app while you review them. It takes about two minutes and it is the fastest way to understand what a review actually feels like. Delete it afterwards; nothing depends on it.
-
Write your own
Create a deck, then use the Add tab. Front, back, optional tags, ⌘↩ to save, and the form clears itself for the next one. Tab moves between fields.
Decks nest with
::— a deck namedAnatomy::Upper limbbecomes Upper limb inside Anatomy, and studying the parent studies everything under it.
On writing good cards: one fact per card, and the question should have one answer you can say out loud. "List the branches of the facial nerve" is five cards pretending to be one, and it is the single most common reason a card becomes the one you always fail. If a card keeps coming back, it's usually badly written rather than hard.
Your first review
Open a deck and press Start. You'll see the front of a card. Try to actually answer it — out loud, or in your head, but commit to an answer before you reveal. Reading the answer without having tried first is the difference between studying and scrolling.
Press Space (or tap the card) to reveal the back. Then you tell the app how it went, and it is asking one question only: how close were you to failing?
| Button | Key | Means |
|---|---|---|
| Again | 1 | I didn't know it. The card comes back in a few minutes, this session. |
| Hard | 2 | I got there, but slowly and painfully. Comes back sooner than last time. |
| Good | 3 | I knew it. This is the normal answer — most of your reviews should be Good. |
| Easy | 4 | Instant, no effort at all. Pushes the card much further out. |
Space does double duty: it reveals the answer, and pressing it again on a revealed card is Good. So a session where you know everything is just the spacebar.
Two mistakes to avoid. Don't press Easy to move faster — you're not skipping the card, you're telling the scheduler to hide it for months, and it will believe you. And don't be ashamed of Again; it is not a failure, it is the app finding out something useful. A deck where you never press Again is a deck scheduled too conservatively.
Pressed the wrong one? ⌘Z undoes the last answer.
The daily loop
Every deck shows three numbers, and they are three different things:
- New — cards you have never seen. The app feeds these in gradually rather than all at once.
- Learning — cards you met recently and are still nailing down. These repeat within the same day.
- Review — cards you already know that are due for a check-up. On a settled deck this is most of your day.
When all three hit zero the deck says All caught up and the Start button switches off. That is the app telling you to stop. There is no bonus for studying ahead — a card reviewed early is a card reviewed while you still knew it, which teaches the scheduler nothing and costs you the time.
A new day begins at 4 a.m. by default, not midnight, so a 1 a.m. session still counts as the previous day. You can change that hour in Settings.
Sync is manual on desktop. Press the sync button (or Y) when you want your cards on another device. Your collection lives on your own machine; syncing is what puts a copy in the cloud and pulls in what you did elsewhere.
If you fall behind, don't panic and don't grind. Missing a week is normal and the app is built for it. In Deck options there is a spread the backlog action that takes an overdue pile and deals it forward over the coming days at a pace you can actually keep. Use it instead of doing 400 cards in one sitting and quitting the habit.
When you're ready
None of this is needed to use the app. Come back to it when the daily loop is boring and you want more.
Pacing — how a session is shaped
On the deck screen you can swipe between three ways to run a session. Classic studies straight through until the deck is done. Pomodoro works and rests on a timer. Sessions breaks the deck into chunks of N cards with a checkpoint between them — useful when "study the deck" feels too big to start. None of them change scheduling in any way; a card reviewed under one is identical to a card reviewed under another.
Exam practice
A fourth card on that same carousel. Instead of rating your memory, you answer and mark yourself right, wrong, or unsure — and get a score at the end, plus the tags you kept getting wrong. It doesn't touch your review schedule, so you can use it the night before an exam without wrecking anything.
Generate cards
The ✨ button on a deck turns a block of text (or a PDF) into cards. It works in two passes and you are in the middle of both: first it proposes what is worth learning and you untick what isn't, then it writes cards and you approve them one by one. That is deliberate — deciding what matters is where the learning happens, and handing that to a model measurably makes you remember less.
The ✨ on an individual card does a related job: split a card that's secretly three cards, rewrite one that's badly worded, or generate other angles on the same fact so you're not just memorising the first three words of the question.
The knowledge graph
Turn it on in Settings and the app downloads a language model (about 120 MB, once) that runs entirely on your machine — nothing is sent anywhere. After that it can show you which of your other cards are about the same thing, draw them as a graph, and warn you when a card you're writing already exists in the deck.
Easy days
Tell it which days you're busy — every Sunday, or a specific date — and it moves reviews off them in advance instead of letting them pile up. The traffic light next to it tells you honestly how much forgetting the change will cost.
Keyboard shortcuts
Press ⌘/ (or Ctrl/) anywhere in the app for the full, always-current list. The ones worth learning on day one:
| Where | Key | Does |
|---|---|---|
| Anywhere | ⌘/ | Every shortcut there is |
| Anywhere | ⌘, | Settings |
| Home | D A B T | Decks · Add · Browse · Stats |
| Home | Y | Sync now |
| Studying | Space | Reveal, then Good |
| Studying | 1–4 | Again · Hard · Good · Easy |
| Studying | ⌘Z | Undo the last answer |
| Studying | Z | Zoom the card in to read it |
| Studying | Esc | Leave the session |
| Browse | ⌘F | Search |
| Add card | ⌘↩ | Save and start the next one |
When something breaks
"Nodes is damaged and can't be opened"
The quarantine flag. Run the xattr line from
the install section. The download is fine.
My cards aren't on my other device
Sync is manual on desktop, and it has to run on both ends: press sync on the machine you studied on, then again on the one you want the cards to appear on.
Images are blank in the browser version
Media from an .apkg import stays on the machine you
imported it on until you upload it. In Settings there is a one-off
action that mirrors your images to the cloud so the web version can see
them.
I can't create an account on the web
Sign-up happens in the desktop app. Install first, register there, and the same account then works on the web.
Anything else
Use Report a bug in the app. It sends the version and the platform along with your description, which saves a round of "which build are you on?". You can also see your version under Settings.