Oleksii M.

Your device works on the bench. Your app drops the connection in real life. I fix both ends. I build iOS and Android apps for hardware — Bluetooth LE and Wi-Fi — and I write the ESP32 / Raspberry Pi side too. One person owns the whole link, so when Bluetooth breaks nobody blames "the other developer". Before software I spent 13 years as an electrical and automation engineer: production machinery, then nine years at sea on ship automation, generators and bridge equipment (incl. Disney Cruise Line). I'm used to equipment that has to keep working at 3 a.m. with nobody around. What I do: • Companion apps for devices and wearables — native Swift/SwiftUI and Kotlin • Fix unreliable BLE: background drops, Android/Samsung issues, reconnects, bonding, MTU, OTA updates • ESP32 firmware (C++), BLE GATT services, Wi-Fi provisioning, Raspberry Pi gateways (MQTT, local database) • Private AI on your own hardware — local LLMs and document Q&A over scanned manuals, drawings and tables, with the source page cited for every answer. No data leaves your network. • Security check + App Store / Google Play release for apps built with Lovable, Bolt, Cursor or Claude Code • Ongoing support after launch: OS updates, store policy changes, crash fixes Proof you can open: • Smart LED matrix — ESP32 BLE peripheral with a custom GATT service + native iOS app • Heating controller — ESP32 closed-loop control, live web UI over WebSockets, offline-safe control, 18-day history • VesselRef — on-premise document AI answering questions from scanned manuals and drawings • ProWord — vocabulary app I built, shipped and maintain alone on iOS, Android, web and backend • Kopijka — iPhone budgeting app that reads receipts on-device How I work: a short paid first step (audit or first milestone) so you see my work before committing, code in your repository from day one, written updates, and I stay for support after launch. CET time zone — overlap with Europe all day and the US East Coast in the afternoon. English, Ukrainian, Russian, Croatian.