For features that need the phone, not just its screen.
Background services, usage data, widgets, sensors, and data processed on the device so it never reaches a server. We build these in Kotlin and Swift, as a full app or inside your Flutter app.
What we build
- Android apps in Kotlin with Jetpack Compose
- iOS apps in Swift and SwiftUI
- Native modules under an existing Flutter app
- On-device data work that never leaves the phone
At handover
How it runs
Built with Kotlin · Jetpack Compose · WorkManager · Room · Swift · SwiftUI · Core Data
Built on it
The Ami’s Crafts Android app, a client build in development, is Kotlin and Jetpack Compose. Our Swift work so far sits inside Flutter iOS builds, and we would rather say that than stretch it.
Questions we get about this.
Yes, and it is the most common native work we do. A platform channel with a typed contract enforced on both sides, so the Dart side and the native side cannot drift apart silently.
Either. We would rather build one platform exceptionally well than two adequately, and for on-device work the two platforms rarely need the same thing anyway.
They are written against what the app actually does, from the permission list up, not copied from a template. A declaration that does not match behaviour is how apps get pulled after launch.
Tell us what you’re trying to ship.
A 45-minute scoping call, then a written proposal with scope, price and dates within two working days. Every enquiry is read the day it arrives and answered within one working day.
Or email info.kyroninfotech@gmail.com