Shared flashcard decks for teachers: build a vocabulary set once, keep it alive all year

Every language teacher has some version of the same folder: vocabulary lists for unit 3, a slightly different list for last year's group, a corrected copy with the typo in entschuldigen fixed, and a printout that no longer matches any of them. The material is fine. Keeping it consistent across groups, and keeping it in front of students between lessons, is the hard part.

A better setup is one shared flashcard deck per class or student: you maintain it, students study it, and spaced repetition decides when each word comes back.

The real problem is maintenance, not creation

Making a good card set takes an afternoon. The friction shows up later.

• A new cohort starts. The syllabus moved, so last year's deck is 80% right. You rebuild it, or you hand out a stale copy.
• You find an error in week 6. With exported files, every student now owns a frozen copy of the mistake. Anki teachers know the routine: export a new .apkg, email it, hope everyone re-imports it correctly. Deleted cards never propagate at all; the Anki manual tells deck authors to contact users and ask them to delete cards by hand.
• The deck needs to grow weekly. Vocabulary comes out of lessons. If adding ten words means another export-and-email round, most teachers stop bothering by October.

Web-based tools solved distribution but moved the cost to students. Quizlet put Learn and Test behind a subscription, so a free class set no longer guarantees your students can actually study it.

How shared decks work in Memor More

Memor More treats a shared deck as a living document with one author.

1. Build the deck on iPhone, iPad, or Mac. Cards can carry images and text-to-speech audio, which matters when pronunciation is half the point.
2. Generate a share code for the deck and send it to a group or an individual student. A code is a short string, so it travels through whatever channel you already use: the class chat, an email, or a slide at the end of the lesson.
3. Students redeem the code in their own app. The cards land in their library and enter their personal review queue.
4. You keep editing. Fix a definition, or add the words that came up in Tuesday's lesson. Your updates sync to everyone who redeemed the code. Nobody re-imports anything.

Because the code is per-deck, you can run separate decks for separate groups: the A2 evening class gets one code, your private student gets another with her specific gaps, and both keep receiving your updates. The deck sharing guide walks through the mechanics in more detail.

Each student studies on their own schedule

Sharing copies the cards, not the schedule. Every student runs their own spaced-repetition queue, so a student who confuses ser and estar sees those cards again tomorrow, while a classmate who has them down sees them next week. This is the point of the method: intervals track each learner's forgetting, not the group average. Short daily sessions of active recall replace the pre-test cram.

Students also get their own numbers. The app shows what is due, which cards keep failing, and how retention develops over time. "Which words do I actually not know" stops being a feeling and becomes a list, and students can act on it themselves before you ever see a quiz result.

Two honest limits. Review data belongs to each student and stays on their device, so there is no teacher dashboard where you watch the whole class live. If you want a mid-unit check, ask students to open their stats screen. It takes ten seconds and tends to start a useful conversation. And Memor More runs on iPhone, iPad, and Mac only; for a classroom full of mixed devices that matters, for 1:1 tutoring it rarely does.

Deck patterns that hold up over a term

| Setup | What to do | |---|---| | One class, one syllabus | A single class deck you extend weekly; students add private decks for personal weak spots | | Several parallel groups | One deck per group, shared by code, so pacing differences don't collide | | Private students | One small deck per student, grown after every lesson from their actual mistakes | | Pronunciation-heavy courses | Put audio on the prompt side; shared audio travels with the deck | | Exam groups | A shared core deck plus each student's own error cards from past papers |

Keep cards atomic: one fact per card. Big "unit 5 overview" cards feel efficient to write and are miserable to review. The same rules from flashcards for exam revision apply to teacher-made decks.

What it costs and where the data lives

Deck sharing, unlimited cards, audio, images, and daily reviews are free, for you and for students. Premium adds AI card generation and deeper statistics, but a class can run entirely on the free tier.

There are no student accounts to create or manage. Students redeem a code; their review history lives on their own device and in their own iCloud. For teachers who have spent evenings resetting forgotten passwords on classroom platforms, this is the feature.

Getting started

Pick one group and one upcoming unit. Build a 30–40 card deck, share the code in your next lesson, and add to the deck every week from what actually happens in class. If you want a head start, the public deck library has ready-made sets you can point students at today.

A deck you maintain for a year quietly becomes one of your best teaching assets: a current, corrected record of exactly what your students need to remember, with audio where it counts. Build it once, then keep it alive.