Case study · 2026 · beta · solo build Mind Life Puzzle
Fifty-two weekly scripture word searches, one for each week of the 2026 Come, Follow Me schedule.
My roleProduct, design, both native apps
Platforms ● iOS● Android
Built withSwift · SwiftUI · Kotlin · Jetpack Compose
Get it [App Store link] Google Play
The problem
A puzzle has to feel right under the thumb.
[Why a weekly puzzle, who plays it, and why you chose to write it twice instead of sharing one codebase.]
Decisions
The calls I made.
Two native apps, on purpose
SwiftUI on iPhone, Compose on Android. Drag, haptics and timing are where a word game lives, and each platform does them its own way. [What it cost you in time.]
One letter path, eight directions
Selecting a word with one finger in any direction, with a path that snaps to the nearest line. [How you tuned the snapping.]
[A call you’d make differently]
[One honest trade-off.]
+ agent: drafted the change
+ agent: tests pass on both targets
− hebert: not like this. see note.
◐ waiting for hebert
Built with agents
Where agents helped, and where I stepped in.
Agents did[What agents drafted: puzzle generation, content checks, UI tests…]
I did[What you owned: the feel, the content schedule, the release.]
I overrode[One moment the agent was wrong and how you caught it.]
52 weekly puzzles for 2026
2 native apps, one design
[N] [a number you’re proud of]