LingoDeck

LingoDeck: practice when a word is due

LingoDeck is a native Android flashcard app for language learners. Instead of asking people to repeat an entire deck, it schedules each card's next review from their previous answer and shows the cards that are due.

• My role: Android development and contribution to user testing.
• Collaborator: Diana Simonicova, UI/UX design.
• Stack: Kotlin, Jetpack Compose, Room Database.

The problem and approach

The challenge: A static deck gives every word the same attention, even when some are already familiar and others need another review.

The approach: Keep the review flow simple while storing a due date, interval, and ease factor for each card. A remembered card returns later; a missed card comes back sooner.

System Architecture & Design

I separated the study screens, scheduling rules, and local storage so the review logic can change without being tied to the interface:

• Study flow: Reveal an answer, grade recall, and update the card's next review date.
• Architecture: Jetpack Compose screens use ViewModels and a repository, while Room stores decks, cards, and review state on the device.
• Scheduling: Review rules are kept separate from UI code, making them easier to adjust and test.

Testing the review flow

I contributed to user testing alongside Diana. Our test plan focused on a crucial first-use question: would learners understand when to tap, when to swipe, and what each swipe meant?

• Discoverability: The review card gives explicit tap and swipe instructions, with directional colour cues for correct and incorrect answers.
• A clearer starting point: The deck screen labels the main action according to whether cards are due or the learner is starting a practice session.

What I learned and what is next

The project brought together interaction design and persistent state: a simple gesture only works well when its meaning is clear and each review updates the right card data. Keeping the scheduling rules separate from Compose screens made those responsibilities easier to reason about.

Possible next steps:

• Cloud sync: Let learners continue their decks across devices.
• Progress views: Show study patterns and upcoming workload over time.