An Android developer keeps your Kotlin app working across devices and API levels

Yes. Apps on Google Play's closed, open and production tracks all complete it, and an app that collects no data says so there and links its privacy policy. Apps active solely on internal testing are exempt. Google Play shows the answers on the store listing, so they have to match what the SDKs inside the app actually collect.

Yes. Android apps are not tied to one store, but some Google services are tied to Google Play. Firebase Cloud Messaging, for example, works only on devices with the Google Play Store app installed, so push on other devices needs another route. The developer checks which of your SDKs depend on Google Play services before a second store is added.

Usually the logic rather than the screens. Google supports Kotlin Multiplatform for sharing business logic between Android and iOS, such as networking, storage and validation rules, while each platform keeps its own interface. Whether to share, and how much, is agreed with whoever builds your iOS app, because they will be reading Kotlin too.

Through the Play Integrity API, which checks that a request comes from your genuine app, installed by Google Play, on a genuine Android device. Your server reads the verdict and decides what to allow. Obfuscating the code with R8 only makes it harder to read; it does not stop a modified copy from calling your API.

Each year Google Play raises the API level that new apps and updates must target; since 31 August 2026 it is Android 16. An app that misses it cannot ship updates until it catches up, and apps left further behind stop appearing for new users on newer phones. The developer reads the behaviour changes early, because raising the target changes how the app behaves, not only a number in Gradle.

Not in one go. Compose and the older View system run side by side, so new screens can be written in Compose while existing ones move when they next change. A full rewrite stops feature work for a long stretch and seldom pays for itself. The developer starts with the screens that change most often, where Compose saves the most time.

Usually, file by file rather than as a project. Java and Kotlin compile into the same app, so a file moves when someone next works on it and the rest keeps shipping. Kotlin's null safety removes a whole class of crashes, and Google's Jetpack libraries are written for Kotlin first. At Photoweb, our engineers moved the Android app from Java to Kotlin as part of taking it over.

Because Google Play counts them. An ANR happens when the app stops responding to input for five seconds, and users see a dialog offering to wait or close it. Android vitals tracks the user-perceived ANR rate beside the crash rate, and past Google Play's bad behaviour threshold an app can be shown less in search and carry a warning on its listing.

Yes. Many clients start with one senior engineer to cover a specific capability or capacity gap, then add specialists only when the roadmap requires them.

Yes. Adding an engineer follows the same route as the first, and you interview them. Reducing the team follows the notice period agreed in the contract, and the work is handed over in your repository before anyone leaves.

Yes. You manage priorities and day-to-day work directly, in your own channels and delivery process.

Yes. You interview every candidate using your own process and make the final decision about who joins the team.

Our engineers are ImproveIT employees and long-term contractors working through our teams in Poland and Ukraine. We are not a freelance marketplace and do not resell developers from other vendors.

Replacement terms are defined in the contract upfront, so it does not become a negotiation.

You do. IP assignment is included in the contract, and we can sign an NDA before discussing the project.

We sign an NDA before discussing the project, and confidentiality and IP assignment are part of the contract. Engineers work in your repositories, cloud accounts and tools with the access your team grants, so you can narrow or revoke it at any time.

Yes. Our engineers work with teams across Europe and the US. We agree the required working-hour overlap before matching candidates.

Our developers work in English with international product and engineering teams every day. English level is included in the candidate information you receive before the interview.

Rates depend on the role, seniority, experience, and engagement model. You receive the rate, availability, and candidate profile in writing before making any commitment.

Both are agreed before the engagement starts and included in the proposal and contract. We are flexible in that and usually agree on the terms suitable for a client.