توسعه اپلیکیشن اندروید

Android software development is the process by which applications are created for devices running the Android operating system.

Google states that[3] "Android apps can be written using Kotlin, Java, and C++ languages" using the Android software development kit (SDK), while using other languages is also possible.

All non-JVM languages, such as Go, JavaScript, C, C++ or assembly, need the help of JVM language code, that may be supplied by tools, likely with restricted API support.

Some programming languages and tools allow cross-platform app support (i.

e.

for both Android and iOS).

Third party tools, development environments, and language support have also continued to evolve and expand since the initial SDK was released in 2008.

The official Android app distribution mechanism to end users is Google Play; it also allows staged gradual app release, as well as distribution of pre-release app versions to testers.

The Android software development kit (SDK) includes a comprehensive set of development tools.

[5] These include a debugger, libraries, a handset emulator based on QEMU, documentation, sample code, and tutorials.

Currently supported development platforms include computers running Linux (any modern desktop Linux distribution), Mac OS X 10.

5.

8 or later, and Windows 7 or later.

As of March 2015[update], the SDK is not available on Android itself, but software development is possible by using specialized Android applications.

[6][7][8] Until around the end of 2014, the officially-supported integrated development environment (IDE) was Eclipse using the Android Development Tools (ADT) Plugin, though IntelliJ IDEA IDE (all editions) fully supports Android development out of the box,[9] and NetBeans IDE also supports Android development via a plugin.

[10] As of 2015, Android Studio,[11] made by Google and powered by IntelliJ, is the official IDE; however, developers are free to use others, but Google made it clear that ADT was officially deprecated since the end of 2015 to focus on Android Studio as the official Android IDE.

Additionally, developers may use any text editor to edit Java and XML files, then use command line tools (Java Development Kit and Apache Ant are required) to create, build and debug Android applications as well as control attached Android devices (e.

g.

, triggering a reboot, installing software package(s) remotely).

[12][6] Enhancements to Android's SDK go hand-in-hand with the overall Android platform development.

The SDK also supports older versions of the Android platform in case developers wish to target their applications at older devices.

Development tools are downloadable components, so after one has downloaded the latest version and platform, older platforms and tools can also be downloaded for compatibility testing.

[13] Android applications are packaged in .

apk format and stored under /data/app folder on the Android OS (the folder is accessible only to the root user for security reasons).

APK package contains .

dex files[14] (compiled byte code files called Dalvik executables), resource files, etc.

The Android SDK Platform Tools are a separately downloadable subset of the full SDK, consisting of command-line tools such as adb and fastboot.

The Android Debug Bridge (ADB) is a tool to run commands on a connected Android device.

The adbd daemon runs on the device, and the adb client starts a background server to multiplex commands sent to devices.

In addition to the command-line interface,[15] numerous graphical user interfaces exist to control adb.

The format for issuing commands is typically: For example, Android applications can be saved by the command backup to a file, whose name is backup.

ab by default.

[16] In a security issue reported in March 2011, ADB was targeted as a vector to attempt to install a rootkit on connected phones using a "resource exhaustion attack".

[17] Fastboot is a protocol[18] and it has a tool with the same name included with the Android SDK package used primarily to modify the flash filesystem via a USB connection from host computer.

It requires that the device be started in a boot loader or Secondary Program Loader mode, in which only the most basic hardware initialization is performed.

After enabling the protocol on the device itself, it will accept a specific set of commands sent to it via USB using a command line.

[19] Some of the most commonly used fastboot commands include: Code written in C/C++ can be compiled to ARM, or x86 native code (or their 64-bit variants) using the Android Native Development Kit (NDK).

The NDK uses the Clang compiler to compile C/C++.

GCC was included until NDK r17, but removed in r18 in 2018.

Native libraries can be called from Java code running under the Android Runtime using System.

loadLibrary, part of the standard Android Java classes.

[22][23] Command-line tools can be compiled with the NDK and installed using adb.

[24] Android uses Bionic as its C library, and the LLVM libc++ as its C++ Standard Library.

The NDK also includes a variety of other APIs:[25] zlib compression, OpenGL ES or Vulkan graphics, OpenSL ES audio, and various Android-specific APIs for things like logging, access to cameras, or accelerating neural networks.

The NDK includes support for CMake and its own ndk-build (based on GNU Make).

Android Studio supports running either of these from Gradle.

Other third-party tools allow integrating the NDK into Eclipse[26] and Visual Studio.

[27] For CPU profiling, the NDK also includes simpleperf[28] which is similar to the Linux perf tool, but with better support for Android and specifically for mixed Java/C++ stacks.

The Android 3.

1 platform (also backported to Android 2.

3.

4) introduces Android Open Accessory support, which allows external USB hardware (an Android USB accessory) to interact with an Android-powered device in a special "accessory" mode.

When an Android-powered device is in accessory mode, the connected accessory acts as the USB host (powers the bus and enumerates devices) and the Android-powered device acts as the USB device.

Android USB accessories are specifically designed to attach to Android-powered devices and adhere to a simple protocol (Android accessory protocol) that allows them to detect Android-powered devices that support accessory mode.

[29] Development tools intended to help an Android device interact with external electronics include IOIO, Android Open Accessory Development Kit, Microbridge, Triggertrap, etc.

The Android Developer Challenge was a competition to find the most innovative application for Android.

Google offered prizes totaling 10 million US dollars, distributed between ADC I and ADC II.

ADC I accepted submissions from January 2 to April 14, 2008.

The 50 most promising entries, announced on May 12, 2008, each received a $25,000 award to further development.

[30][31] It ended in early September with the announcement of ten teams that received $275,000 each, and ten teams that received $100,000 each.

[32] ADC II was announced on May 27, 2009.

[33] The first round of the ADC II closed on October 6, 2009.

[34] The first-round winners of ADC II comprising the top 200 applications were announced on November 5, 2009.

Voting for the second round also opened on the same day and ended on November 25.

Google announced the top winners of ADC II on November 30, with SweetDreams, What the Doodle!? and WaveSecure being nominated the overall winners of the challenge.

[35][36] There is a community of open-source enthusiasts that build and share Android-based distributions (i.

e.

firmware) with a number of customizations and additional features, such as FLAC lossless audio support and the ability to store downloaded applications on the microSD card.

[37] This usually involves rooting the device.

Rooting allows users root access to the operating system, enabling full control of the phone.

Rooting has several disadvantages as well, including increased risk of hacking, high chances of bricking, losing warranty, increased virus attack risks, etc.

[38] It is also possible to install custom firmware, although the device's boot loader must also be unlocked.

Custom firmware allows users of older phones to use applications available only on newer releases.

[39] Those firmware packages are updated frequently, incorporate elements of Android functionality that haven't yet been officially released within a carrier-sanctioned firmware, and tend to have fewer limitations.

CyanogenMod and OMFGB are examples of such firmware.

On September 24, 2009, Google issued a cease and desist letter[40] to the modder Cyanogen, citing issues with the re-distribution of Google's closed-source applications[41] within the custom firmware.

Even though most of Android OS is open source, phones come packaged with closed-source Google applications for functionality such as the Google Play and GPS navigation.

Google has asserted that these applications can only be provided through approved distribution channels by licensed distributors.

Cyanogen complied with Google's license and continued to distribute its mod without the proprietary software.

It provided a method to backup licensed Google applications during the mod's install process and restore them when the process is complete.

[42] Obstacles to development include the fact that Android does not use established Java standards, that is, Java SE and ME.

This prevents compatibility between Java applications written for those platforms and those written for the Android platform.

Android reuses the Java language syntax and semantics, but it does not provide the full class libraries and APIs bundled with Java SE or ME.

[43] However, there are multiple tools in the market from companies such as Myriad Group and UpOnTek that provide Java ME to Android conversion services.

[44][45][46] Android provides its own GUI classes, and does not provide Java AWT, Swing or JavaFX.

It does not support the full Java Beans API.

[citation needed] Android was created by the Open Handset Alliance, which is led by Google.

The early feedback on developing applications for the Android platform was mixed.

[47] Issues cited include bugs, lack of documentation, inadequate QA infrastructure, and no public issue-tracking system.

(Google announced an issue tracker on January 18, 2008.

)[48] In December 2007, MergeLab mobile startup founder Adam MacBeth stated, "Functionality is not there, is poorly documented or just doesn't work.

.

.

It's clearly not ready for prime time.

"[49] Despite this, Android-targeted applications began to appear the week after the platform was announced.

The first publicly available application was the Snake game.

[50][51] A preview release of the Android SDK was released on November 12, 2007.

On July 15, 2008, the Android Developer Challenge Team accidentally sent an email to all entrants in the Android Developer Challenge announcing that a new release of the SDK was available in a "private" download area.

The email was intended for winners of the first round of the Android Developer Challenge.

The revelation that Google was supplying new SDK releases to some developers and not others (and keeping this arrangement private) led to widely reported frustration within the Android developer community at the time.

[52] On August 18, 2008, the Android 0.

9 SDK beta was released.

This release provided an updated and extended API, improved development tools and an updated design for the home screen.

Detailed instructions for upgrading are available to those already working with an earlier release.

[53] On September 23, 2008, the Android 1.

0 SDK (Release 1) was released.

[54] According to the release notes, it included "mainly bug fixes, although some smaller features were added.

" It also included several API changes from the 0.

9 version.

Multiple versions have been released since it was developed.

[55] On December 5, 2008, Google announced the first Android Dev Phone, a SIM-unlocked and hardware-unlocked device that is designed for advanced developers.

It was a modified version of HTC's Dream phone.

While developers can use regular consumer devices to test and use their applications, some developers may choose a dedicated unlocked or no-contract device.

As of July 2013[update], more than one million applications have been developed for Android,[56] with over 25 billion downloads.

[57][58] A June 2011 research indicated that over 67% of mobile developers used the platform, at the time of publication.

[59] Android smartphone shipments are forecast to exceed 1.

2 billion units in 2018 with an 85% market share.

[60]