# Android Build Target 27 Migration

DevFeed: [Android Build Target 27 Migration](<https://devfeed.tech/articles/android-build-target-27-migration-19192.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/android-build-target-27-migration/>)

Author: Shai Almog

Published: 2018-03-27T00:00:00Z

Content type: tutorial

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [migration](<https://devfeed.tech/topics/migration.md>), [Android](<https://devfeed.tech/topics/android.md>), [API](<https://devfeed.tech/topics/api.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [api](<https://devfeed.tech/tags/api.md>), [article](<https://devfeed.tech/tags/article.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [migration](<https://devfeed.tech/tags/migration.md>)

## AI overview

Codename One plans to migrate its Android builds to API level 27 following Google's requirement to stop accepting applications targeting API levels below 26. The article explains API levels, compatibility with older devices, possible impacts on background behavior and native code, and the need to test before migration.

## Source excerpt

A while back Google announced that starting in August 2018 they will no longer accept applications targeting API levels below 26. With that in mind we plan to migrate our builds to use API level 27 which brings with it a lot of great new features but will probably break some things as we go through the migration. Please read this post carefully, I'll try to cover everything.