Flutter developer who likes to build things, break things, and then figure out why they broke.
I have been working with Flutter for 4+ years, building applications for Android, Web, and Android TV.
What I enjoy most is working on problems that aren't really just Flutter problems.
I like working with native Android, hardware, networking, background services, and real-time communication. When a Flutter package isn't enough, I'm comfortable going into Kotlin and figuring things out at the platform level.
I've worked with things like SIP/VoIP, FCM-based calling, MQTT, Push-to-Talk, WiFi and network information, live location tracking, and Flutter ↔ Kotlin communication.
I'm particularly interested in the kind of problems where there isn't an obvious solution and you have to dig into how Android or the underlying system actually works.
- Flutter & Dart
- Native Android & Kotlin
- Firebase & FCM
- SIP / VoIP
- MQTT & Push-to-Talk
- WebSocket
- WiFi & network information
- Device discovery and network scanning
- Live location tracking
- Google Maps
- Background & foreground services
- Flutter ↔ Kotlin communication
- Android TV
- REST APIs
- Hive
- WebRTC
I've worked on mobile calling systems using SIP, WebSocket, FCM, MQTT, and native Android services.
A big part of this work is making sure an incoming call or real-time event still works when the app is in the background or isn't actively being used.
I've also worked with Push-to-Talk communication and real-time event handling.
I enjoy working with WiFi and networking because it often requires going beyond what Flutter provides out of the box.
I've worked with:
- WiFi connection and signal information
- Network information
- Device discovery
- Network scanning
- Connectivity information
- Device-level information
- Native Android networking APIs
A lot of this involves writing native Kotlin code and communicating with Flutter through platform channels.
I've also worked with live location tracking and location-based features, including Google Maps, Firebase, real-time location updates, and background location handling.
One of the things I like about Flutter is that I don't have to stay inside Flutter.
If something requires access to Android APIs, background services, native Activities, hardware, networking, or other platform-level functionality, I'll usually go down to Kotlin and build the missing part there.
That's probably the part of mobile development I enjoy the most — understanding what's actually happening underneath the UI.
Most of the applications I've worked on professionally are private.
The source code includes production logic, internal architecture, business-specific features, and integrations that I can't publish publicly.
So, if you look through my GitHub and don't find the source code for some of the things I've mentioned above, that's the reason.
If you'd like to see what I've worked on, discuss the technical side of a project, or just talk about a difficult problem you're trying to solve, feel free to reach out.
I'm happy to share more about my work privately when possible.
I'm currently spending time learning and experimenting with:
- Agora
- Real-time communication
- Live location systems
- More native Android functionality
- Hardware and device-level communication
Flutter · Kotlin · Native Android · Hardware · Networking · VoIP · FCM · MQTT · Live Location
Last updated: August 2026