Games First, Then the Long Game
Why the studio chapter funds everything else — and how taste, systems, and AI tooling fit together.
Games first, then the long game
The first chapter is not a distraction from the bigger plans. It is the engine.
Lemon Tree Studio, mobile games, and an AI-native way of making are how I learn production at scale: retention, taste, shipping cadence, and the humility of analytics. Those muscles matter whether you are building entertainment or infrastructure.
What “AI-native” means here
Not replacing taste with autocomplete. It means collapsing friction between idea and playable prototype so more of the week is spent on judgment — what feels good, what is worth keeping, what should die early.
Funding the next chapters
A durable studio creates optionality. Research compute, better city systems, ambitious community projects — none of that gets far without proof that you can make something people return to, again and again.
Shipping as a practice
The blog, the gallery, and the unfinished roadmap are all the same habit: leave evidence. The long game is patient, but it is not vague.