I make the tools that make the apps that make your life easier.
Somewhere in that chain, I'm having a great time.

I'm a mobile engineer with 6 years of experience who has a particular obsession with building things other developers use — SDKs, public APIs, dev tooling. If it ships as a dependency in someone else's pubspec.yaml, Package.swift, or build.gradle, I'm probably more excited about it than the end-user product.

That said, I'm not just a tools person. I've shipped full consumer products, contributed meaningfully to open source, and spent enough time across Android, iOS, and cross-platform to have real opinions about all three — and enough humility to know which tool actually fits the job.

By day (and honestly, also by night), I work across:

Flutter / Dart  ████████████████████  my happy place
Kotlin          ██████████████████░░  Android native, no fear
Swift           ██████████████████░░  iOS when it calls
TypeScript      ██████████████████░░  for the RN sides of things / probably web
Python          ████████████░░░░░░░░  scripting, AI pipelines
Bash            ██████████░░░░░░░░░░  CI/CD, automation, the glue between things
+ whatever LLMs can write faster than me (honestly, respect)

📦 SDKs & Public APIs
There's something deeply satisfying about writing an abstraction that other developers actually adopt. Good SDK design is an underrated skill — you're making decisions your consumers can't easily undo, so you have to get the ergonomics right. I find that challenge genuinely fun.

🤖 AI Products
I build AI-powered things. Not the "we added a GPT call to a button" kind — the kind where the intelligence is the product. I'm experimenting constantly; some of it ships, some of it teaches me something worth knowing.

🌍 Open Source
Active contributor. If you've ever had a stranger leave a thoughtful review on your PR at midnight, you know why people do this. That's the energy.

• Cross-platform without the excuses — I can go deep on Flutter for shared logic, drop to Kotlin for Android-specific performance work, and write idiomatic Swift when iOS needs native behaviour. I don't pretend one solution fits everything.
• SDK design experience — I think carefully about public API surfaces, versioning, breaking changes, and developer ergonomics. I've felt the pain of badly designed libraries. I try not to inflict that on others.
• Full-stack enough to ship — Python for AI pipelines and tooling, Bash/CI for automation, TypeScript for React Native or web surfaces. I can own a feature end-to-end without waiting on someone else to unblock me.
• Open source track record — Real commits, real reviews, real collaboration in the open. Easy to verify.

• 🔨 Building CircleBox — a native flight recorder SDK for mobile apps
• 📱 Going deeper into Desktop apps
• 🤖 Tinkering with AI-native experiences
• 🌱 Contributing to open source whenever I can steal time from my calendar
• 🤝 Open to collaborating on SDKs, dev tools, or anything that ships as a library

• 🏗️ I genuinely believe API design is an art form — and most people treat it like a first draft
• 🐛 My bug-to-feature ratio has improved significantly since year 1 (I think)
• 📖 I read PRs the way some people read novels — with opinions and margin notes
• ☕ Fuelled by coffee and the irrational confidence that this time the build will pass on the first try

If you're building a mobile SDK, an open source library, or an AI product and want to collaborate — or just want to argue about state management architecture — reach out:

_{This README was written by a human. Mostly.}