Explore The Cell
ProductionApril 1, 2020
The first app I ever deployed to the App Store. Originally "Explore The Cell" — an educational app with cell biology illustrations made in Adobe Illustrator, animated in the app. Years later, expanded to ~22 mini-games exploring scales from subatomic particles to infinity. The first thing I shipped that strangers could download.
Purpose
Made cell biology illustrations in Adobe Illustrator (one of the few uses of those Adobe Creative Cloud skills from the bootcamp recreation project), brought them into a Flutter app with animations and educational content, and deployed it. It was the first app on the App Store under my name. Years later, I expanded it far beyond the cell — adding ~22 games exploring every scale of reality from particles to the cosmos.
Stack
What I Learned
- The first app you deploy is the most important app you deploy — not because it is good, but because it proves the pipeline works. You can write code, package it, submit it, survive the review process, and put it in front of strangers. Every app after the first one is easier because the fear of the process is gone.
- Adobe Illustrator skills from the bootcamp era (the Adobe CC homepage recreation project) directly fed this project — creating vector cell biology assets (mitochondria, nucleus, cell membrane, ribosomes) that scaled cleanly to any device resolution. Vector art for mobile apps is the right choice because it renders crisply at any size without bitmap artifacts.
- Expanding from "Explore The Cell" to 22 games spanning particles to infinity was scope expansion that worked because each game was small and self-contained. Adding one mini-game does not risk the stability of the others. The architecture (separate game modules within a single app) supported growth without refactoring. This is the opposite of the Note Timer scope creep — the expansion was additive, not architectural.
- Educational apps have a specific App Store category with less competition than games or productivity. Positioning "Explore The Cell" as educational gave it discoverability among parents and teachers who actively search for learning apps. The category choice was strategic, not just descriptive.
- The journey from cell biology to particles to infinity mirrors the real scientific journey of discovery — zoom in and you find atoms, zoom further and you find quarks, zoom out and you find galaxies, zoom further and you find the cosmic web. Each scale is a game. Each game is a window into a different level of reality. The app became a tour of the universe disguised as a collection of mini-games.
Key Insights
- The first deployed app connects the beginning and the present of this entire blog. Chrome Save Tabs was the first thing built. Explore The Cell was the first thing shipped to the public. The gap between building and shipping is the gap between a developer and a professional. Closing that gap — submitting to the App Store, waiting for review, getting approved, seeing the listing go live — was the milestone that made everything after it possible.
- The Adobe Illustrator → Flutter pipeline (design assets in professional tools, implement in code) is the same pipeline that the Potatuhs brand uses today. The HIIT Potato drawings, the Potato Pounder animations, the game character sprites — all follow the pattern established here: create art, import it, animate it, ship it. Explore The Cell was the first run through that pipeline.
- Twenty-two mini-games in one app is essentially what Hot Potato Games is — a collection of small, themed games under one umbrella. Explore The Cell was the prototype for the catalog model. The concept of "many small games, one destination" predates the HPG brand by years. The pattern was already in place. It just needed potatoes.
This post was composed through a conversation between Brett Owers and Claude Code (Anthropic). The content reflects Brett's recollection of each project and the lessons drawn from it. Some details may be approximate or omitted — the purpose is to paint an honest picture of a software engineer's development over time, not to serve as a precise historical record.