Challenge
Answers stay in the chat window. Flashcard apps make you build the cards; AI tools never ask you again.
Portfolio · Consumer AI · iOS · 2026
People ask AI the same question again and again. I designed and built MemQ, an iOS app that turns your own material into cards and brings each one back just before you would forget it.
Challenge
Answers stay in the chat window. Flashcard apps make you build the cards; AI tools never ask you again.
Solution
Your own material becomes cards. A schedule brings each back on time, in five kinds of question, with a character that reacts to how it went.
Outcome
Version 1 live on the App Store. Version 2.0 rebuilt end to end: new visual language, rigged mascot, spaced-retrieval scheduler and progress charts.
Deliverables
01 / Overview
I owned every layer: research, product scope, visual language, the character, motion, and the code that ships it. That matters for this case, because most decisions below were made where design and engineering meet.





02 / The problem
I use Anki, but making the cards takes longer than actually learning. So I just don’t make them.
Language learner, foundational interview.
03 / Research
8 interviews and 24 survey responses across students, language learners and professionals, many already using Anki, Quizlet, ChatGPT or Claude. Then two rounds of usability testing on the prototype (6 and 5 sessions, 3 returning) and 15 TestFlight users on reminders and subscription.
People spent longer making cards than studying them. → AI drafting became the main path, manual entry the fallback.
They wanted help with the busywork and control over the study. → AI fills fields; the learner edits and keeps.
Sceptical first, convinced once extraction was right. → Show the work: slips picked out, answers overrulable.
Visible mastery was rated high-value in every round. → Today leads with what is due; You gets charts from an answer log.
04 / Principles
Cards come from what you looked up, read or asked. Ready-made decks are not the enemy; they are just not yours.
Generation, extraction and marking all land in editable places, and the learner can overrule.
Open the app and the main action is found in the first glance. Stats come second.
Streaks and goals count reviews. No lives, no coins, no punishment for a missed day.
The character reacts and keeps you company, and always stays smaller than the content.
05 / Direction
Type before chrome. One accent, used only for state.
Calm and credible, but nothing on the screen invited you back tomorrow.
Colour lives in details. A first character, kept subordinate to content.
Quieter still. The character was a sticker, not part of the product.

Lime sky, purple content. Depth by one rule. A character that reacts.
Now the bar: playful must still read as made for adults.
For 2.0 I wrote a brief for five deliberately different directions, each tested with the same home screen, the same quiz and the same numbers, so the comparison was about design rather than nicer sample data. Each had to say what you see first, where you start, and what gets pushed back, and why.
06 / Design language
A playful style falls apart fast when every component improvises its own depth. So the system has exactly one: a ledge. Every raised surface is a face on a darker shell, offset upward. Switch the treatments below to see why the other two were rejected, and press the button.
Ledge. Face plus shell, offset upward. The lip is the only depth in the app.
Press the button: the face drops onto its shell, so pressing is the ledge disappearing.
#F6FF7CGround gradient#6C3CBCLead action, icons#4B2C78Button shell, mascot ink#301A50Titles and body#795BA3Secondary text#F0E4FCPale purple ground#F4FAB1Picked answer#FFBA00Mascot marks only07 / Inkling
Inkling started as a drawing in Figma and ended as a rig: separate parts, each turning about its own point, driven by springs and linked so the tail, horns and hands follow the body. This is the app’s own rig running in your browser. Take it apart, show the skeleton, switch the state the app is in, or tap it.
08 / The loop
Play the card below. Answer as if it came due, miss one, or set an exam date and watch the remaining looks close up. The curve is illustrative; the stages are the real ones.
A new card. Its first look is tomorrow.
A card is taken through look, recognise, produce: a new card gets all three, a familiar one only the last. Each step has several forms. Watch them play one at a time, or move your pointer in and answer them yourself.
A new card is seen once before anything is asked.
Tap to turn it over, then say how it went. Drag right for I got it, left for Need review; let go short of the line and it springs back. The two buttons do the same.
A rebuild of the practice screen at the app’s own layout, using its own marking and matching code, on demonstration content. The app reads open answers for sense with a model; that step is simulated here.
typed: “accomodate”typed: “acomodete”typed: “quit trying”typed: “let it go”Every chart on the You page leads with a single figure and a line saying what it means; the chart is there to back the sentence up, not to be read like a spreadsheet. One purple ramp runs through all of them: the deeper, the further along. They grow in when the numbers change, not on every visit, and stand still with reduced motion.
09 / Now building
This is what I am working on now. People already learn by asking Claude or ChatGPT; what they ask there is gone a week later. The aim: the conversation is summarised into knowledge cards, and MemQ makes sure you remember them. MemQ becomes the memory of the chats you learn in, not one more place to type.
MemQ skill → list_lessons // is there a lesson these belong in?
{"surfaceUpdate":{"surfaceId":"memq-cards","components":[
{"id":"root","component":{"Column":{"children":{"explicitList":["where","cards","add"]}}}},
{"id":"where","component":{"MultipleChoice":{"selections":{"path":"/destination"},"options":[
{"label":{"literalString":"Add to Everyday Italian (recommended)"},"value":"lesson:everyday-italian"},
{"label":{"literalString":"New lesson: Italian verbs"},"value":"new:Italian verbs"}]}}},
{"id":"cards","component":{"List":{"children":{"template":{"componentId":"card","dataBinding":"/cards"}}}}},
{"id":"card","component":{"MemQCard":{"kind":{"path":"kind"},"term":{"path":"term"},"selected":{"path":"selected"}}}},
{"id":"add","component":{"Button":{"child":"addLabel","action":{"name":"add_to_memq","context":[
{"key":"destination","value":{"path":"/destination"}},{"key":"cards","value":{"path":"/selected"}}]}}}}]}}
{"dataModelUpdate":{"surfaceId":"memq-cards","contents":[{"key":"destination","valueString":"lesson:everyday-italian"}, …]}}
{"beginRendering":{"surfaceId":"memq-cards","root":"root","catalogId":"memq"}}
← userAction {"name":"add_to_memq","context":{"destination":"lesson:everyday-italian","cards":["c1","c2","c3"]}}
→ MemQ tool: add_cards_with_practice // or create_lesson_with_practice for a new lesson; cards and questions saved togetherIn the AI app, add MemQ as a connector. MemQ’s own setup sheet asks which app first, then shows only that app’s steps.
The app sends you to MemQ to sign in and say yes. Nothing is shared until you do, and writes can ask again each time.
Ask the way you already do. When something is worth keeping, say so: MemQ suggests a lesson, shows the cards in the chat, and you add the ones you want in one go.
This is the direction, shown as it should work rather than as it runs today. It is in design and not released.
10 / Results
I do not yet have usage data for 2.0, so I am not claiming retention gains. The first thing to measure is whether people come back for the second and seventh day’s reviews.
11 / Reflection