Lab
Questions we have not finished answering.
Work that is not a product yet, kept visible on purpose. Each entry states the question, what we did about it, and what we actually learned — including the entries where the answer was no, and the ones still open.
- EXPERIMENT
Borrowing a solver instead of rewriting the rules
When a demo needs a product’s logic, is copying the real code in safer than rewriting a simplified version of it?
4 findings
- LAB
What a demo may claim when the product is not finished
Can a product that does not work yet still have a demo that is worth running and not misleading?
4 findings
- EXPERIMENT
Shipping the real engine, not a recreation
Does letting a visitor play the actual game — the same engine that runs in the app — prove more than any screenshot gallery can?
4 findings
- LAB
Producing twenty-nine voiced locales offline
Can a full multi-language voice set for a children’s app be produced locally on one GPU, with no paid speech API and no per-character billing?
3 findings
- LAB
Sprint form analysis without a server
Can a phone analyse sprint mechanics well enough to coach from, without uploading the video anywhere?
2 findings
Why this page exists
A studio that only shows finished work is not showing you very much.
These are open questions, not case studies. Some of them turned into something that shipped, one of them has a finding that reads “this does not generalise”, and at least one is still unresolved. Keeping them here is the difference between a portfolio and a place where work is actually happening.