Mobile app development


Mobile app development is the act or process by which a mobile app is developed for one or more mobile devices, which can include personal digital assistants, enterprise digital assistants, or mobile phones. Such software applications are specifically designed to run on mobile devices, after considering many hardware constraints. Common constraints include central processing unit architecture and speeds, available random-access memory, limited data storage capacities, and considerable variation in displays and input methods. These applications can be pre-installed on phones during manufacturing or delivered as web applications, using server-side or client-side processing to provide an "application-like" experience within a web browser.
The mobile app development sector has experienced significant growth in Europe. A 2017 report from the Progressive Policy Institute estimated there were 1.89 million jobs in the app economy across the European Union by January 2017, marking a 15% increase from the previous year. These jobs include roles such as mobile app developers and other positions supporting the app economy.

Overview

To facilitate developing applications for mobile devices, and the consistency thereof, various approaches have been taken.
Most companies that ship a product provide an official software development kit. They may also opt to provide some form of software testing and/or quality assurance. In exchange for being provided the SDK or other tools, it may be necessary for a prospective developer to sign some form of non-disclosure agreement, which restricts the sharing of privileged information.
As part of the development process, mobile user interface design is an essential step in the creation of mobile apps. Mobile UI designers consider constraints, contexts, screen space, input methods, and mobility as outlines for design. Constraints in mobile UI design, which include the limited attention span of the user and form factors such as a mobile device's screen size for a user's hand. Mobile UI context includes signal cues from user activity, such as the location where or the time when the device is in use, that can be observed from user interactions within a mobile app. Such context clues can be used to provide automatic suggestions when scheduling an appointment or activity or to filter a list of various services for the user.
The user is often the focus of interaction with their device, and the interface entails components of both hardware and software. User input allows for the users to manipulate a system, and the device's output allows the system to indicate the effects of the users' manipulation.
Overall, mobile UI design's goal is mainly for an understandable, user-friendly interface. Functionality is supported by mobile enterprise application platforms or integrated development environments.
Developers of mobile applications must also consider a large array of devices with different screen sizes, hardware specifications, and configurations because of intense competition in mobile hardware and changes within each of the platforms.
Today, mobile apps are usually distributed via an official online outlet or marketplace and there is a formalized process by which developers submit their apps for approval and inclusion in those marketplaces. Historically, however, that was not always the case.
Mobile UIs, or front-ends, rely on mobile back-ends to support access to enterprise systems. The mobile back-end facilitates data routing, security, authentication, authorization, working off-line, and service orchestration. This functionality is supported by a mix of middleware components, including mobile app servers, mobile backend as a service, and service-oriented architecture infrastructure.

Platform

The software development packages needed to develop, deploy, and manage mobile apps are made from many components and tools which allow a developer to write, test, and deploy applications for one or more target platforms.

Front-end development tools

Front-end development tools are focused on the user interface and user experience and provide the following abilities:
  • UI design tools
  • SDKs to access device features
  • Cross-platform accommodations/support
Notable tools are listed below.

First party

First party tools include official SDKs published by, or on behalf of, the company responsible for the design of a given hardware platform, and any third-party software that is officially supported for the purpose of developing mobile apps for that hardware.
PlatformProgramming languageDebuggers availableEmulator availableIntegrated development environment availableCross-platform deploymentInstaller packaging optionsDevelopment tool cost
AndroidJava but portions of code can be in C, C++,
Kotlin
Debugger integrated in Eclipse, standalone debugging monitor availableEclipse, IntelliJ IDEA, Android Studio, Project Kenai Android plugin for NetBeansAndroid only, because of Dalvik VM, March 2009apkFree, IntelliJ IDEA Community Edition - Free
BlackBerryJavaDebugger integrated in IDEEclipse, BlackBerry JDEBlackBerry only, because of RIM APIalx, codFree
iOS SDKObjective-C, SwiftLLDB debugger integrated in Xcode IDEBundled with iPhone SDK, integrated with Xcode IDEXcodeiPhone, iPad, iPod TouchOnly via App Store, needs review and approval by Apple Inc.Apple tools are available for free for development on Mac. Applications can be run in a simulator or on a device. Some advanced abilities need a paid developer account.
iOS SDKObject PascalDebugger integrated in Xcode IDEIncluded in Delphi XE2 professional or higherEmbarcadero Delphi XE2iPhone, iPad, iPod TouchOnly via App Store, needs review and approval by Apple Inc.Development requires Intel-based Mac besides the IDE on Windows. Design is on Windows. Compiling and deploying is on Mac. Simulator testing is free, but installing on a device needs a fee for a developer signing key

Second party

Third party

Back-end servers

Back-end tools pick up where the front-end tools leave off, and provide a set of reusable services that are centrally managed and controlled and provide the following abilities:
  • Integration with back-end systems
  • User authentication-authorization
  • Data services
  • Reusable business logic
Available tools include:
PlatformProgramming languageIntegrated development environment availableCross-platform deploymentDeployment optionsDevelopment tool cost
Altova MobileTogether ServerBrowser-based interfaceProprietary IDEServer available for Windows, Linux, macOS. Supports mobile devices running Android, iOS, Windows 8, Windows 10 Windows Phone, HTML5 browser-based clientOn-prem, cloud, or hybridDevelopment tools are free, commercial license needed for deployment
GO!AppZone by Globo plcJavaScript. Custom integrations connectors/server-side logic: C#, VB.NETYes, GO!AppZone StudioAndroid, BlackBerry, iOS, Windows Phone, 8.x, RTOn-prem, cloud or hybridDevelopment tools are free, commercial license or subscription needed for deployment
IBM MobileFirst ServerHTML5, CSS3, JavaScript, and native SDK languages w/ Native Worklight APIEclipse plugin, Eclipse-based stand-aloneAndroid, iOS, BlackBerry 6,7, & 10, Windows Phone 7.5 & 8, Windows 8, Adobe AIR, Mobile Web App, desktop browser web pageOn-premDeveloper edition free via Eclipse Marketplace, commercial license for deployment
MetismoJavaEclipseAndroid, iOS, Java ME, BREW, BlackBerry, Nintendo DS, Palm/webOS, Sony PSP, Samsung bada, Symbian, Windows Mobile, Windows Phone 7, Windows Desktop, OS XOn-premCommercial licenses available
WakandaJavaScriptUse Wakanda StudioAndroid, iOS, Windows Phone 10, HTML5 appOn-prem or cloudCommunity and commercial editions
Verivo AkulaJavaUse any front-end IDEAndroid, iOS, Windows Phone7On-prem, cloud, or hybridFree development licenses; per-CPU deployment licenses. Replaced by Appery.io
WebORB Integration ServerC#, VB.NET, Java, PHP, ActionScript, JavaScript, Objective-C,
XML
Works with Eclipse, Visual Studio, intelliJ IDEA and Amethyst IDEAndroid, iOS, BlackBerry Playbook, Windows Phone 7On-premFree development licenses; free and commercial deployment licenses

Security add-on layers

With bring your own device becoming the norm within more enterprises, IT departments often need stop-gap, tactical solutions that layer atop existing apps, phones, and platform component. Features include
  • App wrapping for security
  • Data encryption
  • Client actions
  • Reporting and statistics

    System software

Many system-level components are needed to have a functioning platform for developing mobile apps.
PlatformProgramming languageDebuggers availableEmulator availableIntegrated development environment availableCross-platform deploymentInstaller packaging optionsDevelopment tool cost
Adobe AIRActionScript, HTML, CSS, JavaScriptFlash Builder, Flash Professional, IntelliJ IDEAAndroid, iOS, BlackBerryThe native distribution format of each platformFlash Builder, Flash Professional, IntelliJ IDEA - commercial licenses available Adobe AIR SDK - Free
BREWC; the APIs are provided in C with a C++ style interfaceDebugger support for the native ARM target code. Can use Visual Studio to debug the x86 testing codeNo Emulator for the target ARM code, has a simulator for the x86 testing codeVisual Studio 6.0, Visual Studio 2003.NET, Visual Studio 2005Compile for the specific BREW version available on the handsetOTARelated dev fees typically needed for Brew App Certification - VeriSign annual fee for becoming a certified developer. Realview ARM compiler for BREW. TRUE BREW testing fee for distributing the application.
Firefox OSHTML5, CSS, JavaScriptNo, but simulator available.Firefox browser, FirebugWeb browser on other platformFirefox Marketplace, Web URLDevelopment requires Mozilla Firefox and the simulator add-on
.NET Compact FrameworkC#, VB.NET, Basic4ppcFree emulator, source code available, also bundled with IDEVisual Studio 2008, 2005, 2003, Basic4ppc IDEWindows Mobile, Windows CE, Symbian-based devices via third-party toolsOTA deployment, CAB files, ActiveSyncMost tools free, but commercial editions of Visual Studio needed for visual designers
OpenFLHaxe IntelliJ IDEA, FlashDevelopAndroid, iOS, BlackBerry Playbook, WebOS, HTML5, Flash, Windows, LinuxThe native distribution format of each platformFree
Palm OSC, C++, PascalOS 1.0–4.1: free emulator provided by PalmSource ; OS 5.0: - 5.4 device-specific simulators provided by Palm Palm OS Development System, CodeWarrior, PocketStudio, HB++, Satellite FormsPalm OS handhelds, or Windows Mobile with StyleTap emulatorPRC files, PalmSource Installer Free, or commercial, or various commercial rapid-development frameworks
PythonPythonAdd-on to Nokia EmulatorSeveral, including plugins for EclipseInterpreted language available natively only on Nokia Series60 though ports exist to other mobile platforms, including Palm OSSis deployment with py2sis or can use Python RuntimeFree
SymbianC++Free emulatorMany choicesCompile per targetSIS deploymentCommercial and free tools available
TizenWeb-based: HTML5, CSS, JavaScript Native: C, C++Free emulatorTizen SDKWeb-based app to be available on web browserTizen through App store, Web URLDevelopment needs Windows, OS X, or Ubuntu Desktop
Ubuntu TouchWeb-based: HTML5, CSS, JavaScript Native: QML, C, C++Ubuntu SDKHTML5 app to be available web browser.Ubuntu Touch through App store, Web URLDevelopment requires Ubuntu Desktop 12.04 or higher, Free
webOSJavaScript, CSS, HTML, C and C++ through the PDKFree emulatorEclipsewebOS, Palm onlyOTA deployment, webOS through App store, Web URL, Precentral,.ipkFree
Windows MobileC, C++Free emulator, also bundled with IDEVisual Studio 2010, 2008, 2005, eMbedded VC++, Satellite FormsWindows Mobile, Windows CEOTA deployment, CAB files, ActiveSyncFree command-line tools or eMbedded VC++, or Visual Studio
Windows PhoneC#, Visual Basic, C, C++Free emulator, also bundled with IDEVisual Studio 2012, Visual Studio 2010Windows PhoneOTA deployment, XAP files

Criteria for selecting a development platform usually include the target mobile platforms, existing infrastructure, and development skills. When targeting more than one platform with cross-platform development, it is also important to consider the impact of the tool on the user experience. Performance is another important criterion, as research on mobile apps indicates a strong correlation between application performance and user satisfaction. Along with performance and other criteria, the availability of the technology and the project's requirements may drive the development between native and cross-platform environments. To aid the choice between native and cross-platform environments, some guidelines and benchmarks have been published. Typically, cross-platform environments are reusable across multiple platforms, leveraging a native container while using HTML, CSS, and JavaScript for the user interface. In contrast, native environments are targeted at one platform for each of those environments. For example, Android development occurs in the Eclipse IDE using Android Developer Tools plugins, Apple iOS development occurs using the Xcode IDE with Objective-C and/or Swift, Windows and BlackBerry each have their own development environments.