Although the underlying components and technologies are very different, Android provides tools and process flows to support the transition from using ADT to Android Studio.
Unlike the ADT Bundle, which is based on Eclipse IDE and the Apache Ant* build system, Android Studio is powered by IntelliJ* IDEA and the Gradle* build system. For an Android developer currently using ADT, it is good to proactively migrate to the Android Studio IDE since, as we will show you in this article, the migration is fairly straightforward. As the Android developer community was informed, Android Studio will eventually be the official Android IDE. In the past several months, we have seen this new IDE improving. This was changed in recent months after Android Studio (Beta) was announced and available for download. In the past several years, Android had been encouraging and enabling developers to use the Eclipse ADT (Android Developer Tools) Bundle as the app development environment. If you are not comfortable with a Beta product, you may want to stay with the development environment you are currently using, such as the ADT Eclipse. You may encounter not-yet-implemented features and bugs. As a use case, this article discusses the flow of moving an Android project currently developed using Eclipse ADT to using Android Studio.Ĭaution: When this article was written, Android Studio was still in Beta. This article introduces Android* Studio (Beta), the new Android* integrated development environment (IDE), which will eventually replace the Eclipse* ADT* Bundle.
Join our communities for Android, Internet of Things, Intel® RealSense™ Technology, and Windows to download tools, access dev kits, share ideas with like-minded developers, and participate in hackathon’s, contests, roadshows, and local events. Intel® Developer Zone offers tools and how-to information for cross-platform app development, platform and technology information, code samples, and peer expertise to help developers innovate and succeed.
0 kommentar(er)
