Utkarsh B.

📱 I build mobile apps that talk to hardware and keep working when the signal drops. Most mobile developers have never shipped an app that pairs with a physical device. I have, and they are live on Google Play today. MW Connect, the companion app for Mobile Warming heated garments, has over 50,000 installs. It pairs several Bluetooth devices at once, names them, reads battery level live from each one, and registers new products to the owner's account. That app runs on every Android brand a customer happens to own, which is where you learn what the documentation does not tell you. DocsInk Care Messenger pairs over BLE with thermometer and INR devices for patients at home. Vitals360 is a handheld medical monitor reading six vital signs. I built its Android application on a custom ROM, including the sensor reads, the upload to the provider cloud, and the offline, single test and multi test modes that let a nurse keep working with no connectivity and sync afterwards. 🔌 Connected devices and BLE Pairing flows that recover from a failed attempt, reconnect logic that does not depend on the framework behaving, GATT operations queued properly so writes are not silently dropped, bonding state handled when it goes stale, and the battery and autostart behaviour of Samsung, Xiaomi, Oppo and Vivo that kills background work unless you plan for it. 📶 Offline-first Local persistence that holds the truth until the server confirms it. Background sync built as eventual and never as a schedule, because Doze decides when work actually runs. Idempotent writes so a retry after a crash cannot duplicate a record, and conflict handling that does not quietly lose data. 🏥 Healthcare Patient apps, provider apps, vitals capture, remote monitoring and device integrations, including work on an ONC certified product. I am used to building where a wrong value is not an inconvenience. 🛠 Core stack Android: Kotlin, Java, Jetpack, WorkManager, Room iOS: Swift, SwiftUI Cross-platform when it genuinely fits: React Native, Flutter Backend and integrations: REST, GraphQL, Firebase Cloud Messaging, Twilio, Stripe Also: QR and barcode scanning, maps and location, push, deep links, in-app purchases, accessibility and localisation Quality: JUnit, XCTest, performance profiling, crash and stability work 🤖 AI, where it earns its place OpenAI API work, in-app assistants, voice features and AI-assisted workflows. I will tell you honestly when AI adds something to your product and when it is decoration. 🎯 Good fits for me Apps that pair with a sensor, wearable or medical device Apps that must work in poor or no connectivity Healthcare and regulated products Rescuing or modernising an app someone else started Taking a product from idea to the store and then onward 🤝 How I work I ask about the product before the stack. I work in small reviewed pull requests with clear written updates, and I say early when something will take longer than expected. I am comfortable working asynchronously from issues and pull requests, and happy on a team with other developers. 📩 Tell me what you are building and what it connects to, and I will tell you straight what I would do and where I think the hard parts sit.