I’ll be honest: when my Flipper Zero arrived, I opened the box, turned it on, pet the dolphin a few times, and then had absolutely no idea what to do next.
This is a $170 device that can read NFC tags, capture radio signals, clone RFID badges, act as a universal TV remote, and inject keystrokes into a computer via USB. It’s genuinely one of the coolest pieces of hardware I’ve ever held. If you haven’t seen one, it looks like a chunky orange Tamagotchi from 2003 with a tiny monochrome screen and a digital dolphin that levels up the more you use it.
For the first two days, it mostly sat on my desk while I scrolled Reddit threads titled things like “what should I actually do with this thing?”
The gap between cool and useful
Here’s the problem with the Flipper Zero: the distance between “this can do incredible things” and “I know how to make it do those things” is vast. The official docs are decent. The community is helpful. But you’re jumping between radio protocols, modulation types, DuckyScript syntax, and what feels like hundreds of community firmware options all at once. The learning curve isn’t linear. It’s more like a pile.
I learn best by building, and I learn second-best by having things broken into small pieces I can work through at my own pace. So instead of trying to absorb everything from scattered forum posts and YouTube videos, I built myself a curriculum.
Learning by teaching
I used Claude Code to help me build Flipper Zero Academy, an interactive learning app that covers the device from “what are these buttons” to “here’s how RFID frequency hopping works.” Seven modules, quizzes, a DuckyScript sandbox, a searchable protocol reference. Terminal-style cyberpunk aesthetic because if you’re going to build yourself a school for a hacking tool, it should at least look the part.
Building it was the actual learning. You can’t write a lesson about Sub-GHz radio without understanding Sub-GHz radio. Every module I created forced me to go deeper than I would have if I’d just been following a tutorial. I had to understand things well enough to explain them, which is a completely different bar than understanding them well enough to follow along.
The NFC and RFID module was a good example. I kept confusing the two, which is apparently universal. Writing the lesson that explains the difference (NFC is your phone and credit card, RFID is your office badge and your pet’s microchip, they work very differently despite both being “tap to do stuff”) is what finally made it stick. I couldn’t have written that explanation before I built the app. Building the app is what created the understanding.
This is the same pattern I keep coming back to with side projects. The French Press Calculator taught me more about extraction ratios than any article I’d read. SendReady forced me to actually understand SPF record lookup limits instead of just vaguely knowing they existed. The project isn’t the output but the learning method.
What I actually do with it now
Honestly? Absolutely nothing.
I added some IR remotes for fun. I saved one for a snowflake projector that I won’t see again until next December. I ran the frequency analyzer around the house and discovered signals from things I forgot I owned. All of that was interesting and none of it became a habit.
The Flipper is back on my desk. Not in a drawer, but not in my pocket either. It’s in that limbo where I know what it can do, I’m glad I learned how it works, and I don’t really have a daily reason to pick it up.
The thing about building to learn
Which, if you’ve been reading this blog, you already know is a pattern. I wrote about it in The Boring Part Is the Whole Point. Building a thing and actually integrating it into your life are two different projects. I built the Academy specifically to make sure I didn’t just shove the Flipper in a drawer. And it worked, sort of. I understand the device. I can explain how rolling codes work. I learned a ton about wireless protocols I interact with every day without thinking about them.
But do I use the Flipper every day? No. The Academy taught me how to use it. It didn’t give me a reason to. That’s a different problem, and I’m not sure building another app solves it.
If you’ve got a Flipper sitting in a drawer, I get it. And if you want a structured way to at least understand what it does before it goes back in the drawer, I built one of those.