Android apps in Kotlin and Jetpack Compose, with iOS companion apps in Swift and SwiftUI when the product needs both platforms. This work fits best when the app touches device policy, AOSP builds, managed deployments, performance-sensitive native code, or release engineering.
Android apps in Kotlin and Jetpack Compose: app architecture, data layer, background work, permissions, device-policy flows, and testable module boundaries.
iOS companion apps in Swift and SwiftUI when the product needs both platforms: app structure, async workflows, TestFlight builds, App Store Connect setup, and managed-app configuration when MDM is part of the deployment.
Native performance paths where they are justified: JNI and NDK on Android, Swift / Objective-C interop on iOS, profiling traces, and measurements on the target devices.
Privileged and system-level Android apps: device-owner apps, custom launchers, settings-style apps, and apps signed into system_uid when they are part of a custom AOSP image.
Managed-device workflows: Android DPCs, work profiles, managed Play, attestation flows, and iOS managed-app configuration, for the OS versions and MDM you use.
Release support: Play Store app bundles, App Store Connect and TestFlight setup, staged rollout planning, crash triage, and documentation for review or policy responses.
AOSP-integrated apps: apps preloaded into a system partition, paired with platform services or HALs, or dependent on device-owner policy in a dedicated device build.
A conversation on the user story, platform constraints, target devices, release path, and known risks. The output is a proposed scope and open questions.
A written architecture and delivery plan: module boundaries, data layer, platform APIs, testing strategy, and milestone acceptance criteria.
PRs into your Git workflow. We use previews, unit tests, integration tests, and real-device runs where they make sense.
Release support, crash triage, and handoff notes are agreed before launch. If post-launch support is needed, response windows and ownership are written into the engagement.
A device-owner app for a kiosk or single-purpose deployment: silent updates, remote config, Wi-Fi provisioning, and custom OTA triggering when paired with a Custom AOSP build.
An Android pipeline with an NDK-backed processing path under a defined latency budget. The work covers the JNI boundary, profiling, and measurements on target hardware.
Android and iOS companion apps for an enterprise product: DPC or work-profile flows on Android, managed-app configuration on iOS, and aligned release notes for both clients.
Tell us what you're building and where you're stuck. We reply with what we think the work involves, and say so if a smaller engagement or a different route would serve you better.