Why a blog
Building software is building products, but it's also building knowledge. Every technical decision we make —Compose vs XML, when to use AI, how to encrypt local data, when to say no to a feature— goes through reasoning that's worth writing down.
This blog is that reasoning, written out. Not to evangelize, but so the next dev (including future us) has the context.
What we'll publish
- Concrete technical notes: why we chose a stack for a specific problem, what surprised us in production, what we walked back.
- Product decisions: when to bet on native vs cross-platform, how to measure if a feature really matters, what to leave out of the MVP.
- Lessons from each project we ship: what worked, what didn't, and the hidden costs we discovered.
We're not going to publish general tutorials that are already well covered elsewhere. Here goes the specific stuff for this studio and the products we build.
How to reach us
If you want to discuss any of these topics, have a project in mind, or just want to say hi, write to us through the contact form. We reply within 24 business hours.