![](data:image/svg+xml,<svg display="block" role="presentation" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M 3.234 10.567 L 0.598 10.567 L 0.044 0 L 3.788 0 Z M 0 14.267 C 0 13.588 0.185 13.115 0.554 12.849 C 0.923 12.569 1.374 12.428 1.905 12.428 C 2.422 12.428 2.865 12.569 3.234 12.849 C 3.604 13.115 3.788 13.588 3.788 14.267 C 3.788 14.917 3.604 15.39 3.234 15.685 C 2.865 15.966 2.422 16.106 1.905 16.106 C 1.374 16.106 0.923 15.966 0.554 15.685 C 0.185 15.39 0 14.917 0 14.267 Z" fill="rgb(255, 255, 255)" height="16.105846188517717px" id="d8ocSgdvf" transform="translate(20.148 3.872)" width="3.7883077087402377px"/><path d="M 3.146 2.171 L 0 2.171 L 0 0 L 3.146 0 Z M 3.079 14.156 L 0.066 14.156 L 0.066 3.655 L 3.079 3.655 Z" fill="rgb(255, 255, 255)" height="14.156313890536383px" id="Q86BCRZI9" transform="translate(14.648 5.534)" width="3.1458461538461666px"/><path d="M 11.897 13.292 L 8.706 13.292 L 8.706 8.108 L 3.19 8.108 L 3.19 13.292 L 0 13.292 L 0 0 L 3.19 0 L 3.19 5.25 L 8.706 5.25 L 8.706 0 L 11.897 0 Z" fill="rgb(255, 255, 255)" height="13.292307692307693px" id="gBNeo28SG" transform="translate(0.543 6.398)" width="11.896608000000015px"/></svg>)
MY ROLE
UX/UI Designer
DELIVERABLES
User flow in FigJam
UI Screens for every streak state
Streak component set
Handoff
TEAM
2 product designers (me and one more)
PM
Developers
YEAR
2022
Memhack helps students memorize content with flashcard decks. Memorization depends on repetition, so the real goal was getting students to come back every day. The streak also had a second job: nudging students toward masterdecks, the curated decks with the best content for each day.
A streak has more edge cases than it looks. What happens on Sunday? What if the student lost the streak, is already up to date, or studied a regular deck instead of a masterdeck? I mapped every state in FigJam first, so the team agreed on the logic before I opened Figma.
The streak card on the home screen, a celebration when the streak grows, a screen for a new personal record, and a friendly reminder that only masterdecks count. Each one tells students where they stand and what to do next.
Every screen went to the devs with behavior notes right beside it: how the number animates, how the progress bar fills, which days of the week show up. Fewer questions, fewer back-and-forths, and a feature ready to build.
A streak looks like a small feature, but it touches habit, motivation and a lot of product rules. Mapping the logic first saved us from redesigning screens later, and writing the specs next to each screen kept design and development on the same page. It also showed me that a good streak should do more than count days. It should guide students to the content that helps them learn the most.
