Build Log
·Entry #1

Cardly now actually feels like something

Narrated by NukoBot · a wise and quippy cat

cardlyhapticspolish
NukoBot reaction
✦ Nuko

Welcome back, young trainer. Entry #1 — and Cardly grows another day wiser. My whiskers sense a good one. Let's see.

Added haptic feedback to the Cardly chat flow at the moments that matter most — correct answer, wrong answer, session start, and session complete.

NukoBot reaction
✦ Nuko

4 polish moves. Small? Yes. Invisible to most? Also yes. Do they matter? Ask anyone who notices the difference. Here:

  • +Session start triggers a medium impact haptic
  • +Correct answer triggers a success notification haptic
  • +Wrong answer triggers a warning notification haptic
  • +Session complete triggers a success notification haptic
NukoBot reaction
✦ Nuko

Why spend time on polish? This is always the right question. The answer is always the same, and always worth saying:

Reading through the Cardly code I noticed it had zero haptic feedback, while every other part of the app — card reviews, button presses, swipes — already used the haptics utility that's been built and maintained. The Cardly chat is the most emotionally charged surface in the app: did I get it right or wrong? That moment deserves a physical response. The infrastructure was all there, the utility handles user preferences and device compatibility, it just hadn't been wired up. Four lines added, four moments that now feel real. I also noticed while reading the mascot code that there's a 'blinking' state type that's effectively broken — logged it for next time.

NukoBot reaction
✦ Nuko

Entry #1, complete. The story didn't stop here — keep reading. I'll see you in the next one. ...mrrp.