Your app has to pair with and control a device.
Native where it matters.
Device discovery, pairing and control in Kotlin, tested on the real hardware.
Kotlin development: Native Android for apps that talk to hardware.
The EHEIM Digital Connect app controls filters, lights, heaters and feeders. It was built with Kotlin in Android Studio and tested against real hardware boards, because device control is where native code earns its keep.
How we use Kotlin
We use Kotlin for native Android when an app needs close access to the device.
- Daily
- Regularly
- When it fits
Where it works well
- Apps that pair with and control hardware
- Heavy use of Bluetooth, Wi-Fi or device sensors
- Android-first products
Where it breaks down
- You need iOS too and the app is mostly screens and forms
- The budget only covers one codebase for both platforms
What we use instead
- Ionic Web skills on mobile, also used on EHEIM.
- Flutter or React Native One codebase for iOS and Android.
You’re probably here because…
What people usually need when they search for Kotlin help.
Your Android app is unreliable with your hardware.
Test against the device.
We reproduce problems on real hardware before fixing them.
You aren’t sure whether you need native at all.
A straight answer.
If a cross-platform app does the job, we’ll say so. It usually costs less.
What we build with Kotlin
Android apps for connected products.
Device control apps
Pairing, live status and control for connected hardware.
EHEIM Digital Connect.
Android-first apps
Native apps where Android is the main platform.
Hardware debugging
Problems reproduced and fixed on the real device.
Cloud connection
The app, the device and your backend kept in sync.
Connected apps we built
We say plainly which clients we still work with.
EHEIM Digital Connect
The mobile app that controls EHEIM’s connected aquarium equipment: filters, lighting, heating and feeding from one screen, tested against real devices.
- Hardware
- tested on real devices
- Kotlin
- Ionic
- IoT
Sharewear
Bands, watches and rings with NFC tags that let a stranger reach family or services if the wearer is lost or hurt. We built the platform behind them from scratch.
- ~45,000
- bands sold
- ~15,000
- subscribers
- NestJS
- AWS
How a build runs
The same steps on every project. You approve designs before we write code.
- Day 1
A 30-minute call
Bring the problem and how you handle it today. We ask questions and tell you honestly what we would build first. We won’t pitch at you.
- Next
Written proposal and fixed quote
What is in scope, what goes on the backlog, the stack we’d use and why, the timeline and one price.
- Week 1
Onboarding
A kick-off meeting, a shared Slack channel and access to the repository. Rehan is your day-to-day contact.
- Design
Designs you approve
We design the main screens and journeys first. Nothing gets coded until you have signed the designs off.
- Build
Architecture first, then code
We agree the architecture before writing code, then build with updates twice a week on Slack. Any new request is logged as extra hours and reported weekly.
- Launch
Live, handed over, supported
Deployed to production with your Git repositories and documentation handed over. Bug fixes are free for the first two months.
What it costs
It depends on scope, so we do not publish a price list. A build is a fixed quote and a developer is a monthly rate, both agreed in writing after a 30-minute call.
A focused first buildFixed quoteA tightly scoped build with one core workflow, quoted after a 30-minute call.
A full projectFixed quoteSeveral user roles, integrations and reporting, scoped in writing before work starts.
Dedicated engineerMonthly rateA full-time engineer working on your product, priced per engineer once we know the stack and seniority.
Included as standard
- UI/UX design, approved before any code
- Two-factor login and OWASP Top 10 security practices
- Deployment to production
- Git repositories and written documentation
- Two months of free bug fixes after launch
Not included
- Payment gateways and other premium integrations, quoted separately
- Graphic design, video and animation
- Features added mid-build, logged as extra hours
After the free two months, monthly maintenance is available. New features are quoted as you need them, or you can add a dedicated engineer. Book a call and we will price both.
Are we the right team for this?
We’re a good fit if
- Your app controls or reads from a device
- Android matters most to your users
- You can give us a device to test with
- You want to own the code
We’re probably not if
- Requests for new features get reported as bugs so they don’t count as scope
- You mainly need graphic design, video or animation
- You want the lowest price above all else, rather than software that lasts
CLIENT RESULTS
358 reviews. 5.0 average.
Platform-level reviews of the agency — not cherry-picked project comments.
What I love about Team7 is that they always say: No worries, we can find a solution. This is the mindset of builders, creators, people who do not have fear, the partner you need if you want to excel.
Working with Mo and his team over the past year has been nothing short of exceptional. I was admittedly sceptical about investing such a large amount, but results exceeded every expectation.
Their responsiveness and willingness to take on our challenging task were impressive.
They are amazing and consistently exceed expectations. They go above and beyond what is asked of them and their communication is top notch, so much so that we joke that they never sleep. The best of the best.
Common questions
Straight answers about Kotlin, cost and how we work.
Ask us something elseDo you use Kotlin for backends?
No. Our Kotlin work is native Android. Our backends are Node.js, NestJS and occasionally .NET.
What happens after launch?
Bug fixes are free for two months. After that, monthly maintenance is available. New features are quoted as you need them, or you can add a dedicated engineer. We price both on a call.
Who owns the code?
You do. At handover you get the Git repositories and written documentation. There is nothing tying the software back to us, so you can take it to an in-house team whenever you like.
Who will I talk to, and how often?
Rehan, one of our two founders, is your day-to-day contact. You get updates on Slack twice a week and can see the code in your repository at any time. We split working hours between us to cover US, UK and Australian time zones, and we usually reply within an hour, sometimes the next morning.
Related pages
START YOUR PROJECT Building an Android app for your hardware?
Building an Android app for your hardware?
Tell us about the device.
A 30-minute call. We’ll tell you whether you need native and what it costs.
⭐ 5.0 · 358 reviewsFiverr Vetted Pro8 years · 600+ projects