NATIVE ANDROID DEVELOPMENT
From mobile and Android TV to fully offline dedicated devices, use Kotlin and native Android technology to handle system integration, real-time data, hardware capabilities, and existing-app upgrades.
Native Android engineering across device categories
BUILT FOR THE REAL WORLD
When software enters vehicles, field devices, large displays, or enterprise workflows, Android earns its value by integrating reliably with the real environment.
01 / PRODUCT CONTINUITY
Take over Kotlin projects, migrate services approaching shutdown, and integrate features or SDKs without breaking established journeys.
Kotlin · MVVM · Deep Links02 / FIELD OPERATIONS
Handle local data, authentication, roles, device state, and traceable logs in environments with no network connection.
Room · SQLite · Offline-first03 / LARGE SCREEN
Combine streaming video, WebSocket events, maps, and AI model results into clear, responsive large-screen interfaces.
ExoPlayer · WebSocket · Canvas04 / DEVICE INTEGRATION
Connect Bluetooth, cameras, barcode scanners, printers, and vendor SDKs so Android devices participate in operational workflows.
Bluetooth · CameraX · Device SDKSELECTED ENGAGEMENTS
These are the problems and deliverables I owned within client engagements. Each case names the role accurately rather than presenting a client product as my own.
SPECIALIZED DEVICE EXPERIENCE
Android engineering guidance for E Ink devices
Over a two-month industry–academia program, I guided three teams and six students from product concepts to three working Android apps, covering architecture, delivery practice, and device SDK integration.
ENGINEERING CAPABILITIES
Capabilities are combined around the project need—not to add architecture for its own sake.
Review Kotlin or Java code, architecture, and dependencies, then plan features, service migration, or incremental improvement.
Handle synchronization, Room, permissions, and recovery so the app remains usable under real network conditions.
Integrate streaming, live events, maps, and high-performance custom visualization for large displays.
Connect cameras, Bluetooth, barcode scanning, printing, deep links, and vendor-native capabilities.
WAYS TO WORK TOGETHER
A complete greenfield app is not required. We can begin with the issue currently blocking the product.
Review code, dependencies, credentials, and release state before prioritizing risk and improvements.
Deliver an SDK, hardware, real-time, offline, or service-migration scope with explicit acceptance criteria.
Work within the current architecture, source-control, and collaboration practices on independently reviewable Android work.
DELIVERY PATH
Each stage leaves clear technical decisions and reviewable outcomes.
Confirm devices, existing code, system interfaces, and constraints.
Lock responsibility, data flow, risks, and acceptance criteria.
Validate functions and device behavior through working builds.
Complete testing, documentation, handover, and required release support.
FAQ
Yes. I first review architecture, Gradle, dependencies, credentials, and release state, then decide whether to maintain, migrate selectively, or refactor within a practical scope.
Yes. Deep links, Bluetooth, camera, barcode, printing, real-time media, and offline data can be delivered as explicit modules with acceptance criteria.
Yes. My experience includes Android TV, a drone ground station, E Ink devices, and enterprise mobile platforms, with design adapted to input, performance, and deployment context.
I can support test builds, signing, store materials, and release workflows. Account permissions, ownership, and exact responsibilities are agreed before the project starts.
START WITH THE HARD PART
Bring an existing app, a dedicated device, or an integration workflow. We can identify the lowest-risk, most reviewable next step.