I build mobile systems where interaction, trust, and state converge.

Focused on Kotlin-first Android development, while designing systems that handle real-world constraints — performance, consistency, and failure.

I care about how systems behave under pressure.

• Where assumptions leak
• Where state becomes inconsistent
• Where performance degrades
• Where attackers look first

If it handles money, identity, or user-generated content — it must be predictable, observable, and resilient.

• Kotlin/Jetpack Compose mobile applications
• Interactive apps for creatives (comics, storytelling, content experiences)
• Android-first fintech platforms
• Payment SDKs and wallet infrastructure
• Secure authentication and session systems
• API-driven mobile architectures

Before going Kotlin-native, I built and shipped production apps using:

• Flutter (Dart)
• React Native (TypeScript/JavaScript)

This informs how I design: • shared abstractions
• predictable state systems
• cross-platform-ready architectures

• Jetpack Compose performance and recomposition internals
• Kotlin coroutines and Flow (state + concurrency)
• Cryptographic primitives from first principles
• Secure key management on mobile
• Rendering performance for content-heavy apps (e.g. comics, media)

I’m interested in systems that combine:

• interaction (UX)
• state (consistency)
• trust (security)

Especially where failure is not obvious — until it matters.