A mobile learning app for product managers. Flashcards, real product stories, practice reps, and forward-looking PM signals — built around one idea: PMs don’t need more content, they need better judgment.
↳ Build 9 went live on iOS. Android is still working through review.
↳ iOS is live now — the Android link lands once it clears review.
Six small modules. One core loop: discover a concept, understand it quickly, connect it to a real example, practice the thinking, return often enough to build instinct.
↳ every module is one idea, not a kitchen sink.
This is a working version of one card from the app. Tap to flip. Same content, same structure, same product thinking.
What is the Impact vs. Effort Matrix and when is it most useful?
👆 Tap card to reveal 1 / 108↳ this exact card lives in the app. The full deck has 108 of them, across 9 categories.
Captured from the device, not a mockup. Three deep-dive screens — the kind of secondary states the module grid couldn’t show.
I work in product. Building this meant wearing every other hat too: design, UX, engineering, QA, and plenty of “wait, why did that break?” moments. AI became the rest of the team.
↳ own QA budget. own bug list. own 11 PM Sunday.
↳ A few of the visible milestones. There were many more in between — the build that finally went to review is build 9.
BUILD 9 · live on the App Store · May 28, 2026
This wasn’t writing code. It was conversations — plain English, repeated until the AI got it right.
“Okay, so here are both the screenshots, right? I mean, look at the real estate spacing above the bottom nav bar on the Samsung and the iPhone 16 Pro Max. You tell me, is this acceptable? But here’s the important thing — I don’t want us to break everything else and redo the entire format. At the end of the day, this is the home screen. I want it to be pleasing on the eye.”
→ resulted in: the home flashcard layout, post-Build 4f
“I come to the flashcard screen and after maybe three, four, five seconds the card automatically expands. The bottom nav bar disappears too. Why? On the homepage — three seconds, five seconds, seven seconds, no change. The card length is static. So why this behavior on Browse and Gym? Don’t make any changes yet. Let’s first discuss please.”
→ resulted in: the flashcard resize fix across Browse + Gym
“Why are we changing the process? Why don’t you just give me the QR code which I can scan using the Expo Go app and then test it? It should be as simple as that, right? Walk me through the exact steps.”
→ resulted in: the Expo Go testing loop used to validate every build
↳ no magic. just plain English, repeated until the AI got it right.
Before any code, I sketched the experience. Margin notes captured the reasoning. The sketches stayed close to the final build — most decisions held up.
↳ hover (or tap) to lean in. The notes in the margins are where the thinking lives.
Building this let me ship the things I used to only spec. I’m still learning what the AI actually built on my behalf, where my own judgment mattered most, and where I’d do things differently next time.
iOS is live now — you can download it on the App Store. Android is still working through review; the Play Store link lands here the moment it clears.
↳ one store down, one to go.