Mobile app development: Difference between revisions

Revision as of 19:14, 29 April 2025

Revision as of 07:08, 11 May 2025

Line 1:

{{shortShort description|Process to build apps for various mobile operating systems}}

{{Use dmy dates|date=September 2020}}

'''Mobile app development''' is the act or process by which a [[mobile app]] is [[software development|developed]] for one or more [[mobile device]]s, which can include [[personal digital assistant]]s (PDA), [[enterprise digital assistant]]s (EDA), or [[mobile phone]]s.<ref>{{Cite web |title=Introduction to Mobile Application Development {{!}} IBM |url=https://www.ibm.com/topics/mobile-application-development |access-date=2023-06-24 |website=www.ibmIBM.com |language=en-us}}</ref> Such software applications are specifically designed to run on mobile devices, takingafter numerousconsidering many hardware constraints into consideration. Common constraints include [[central processing unit]] (CPU) architecture and speeds, available [[random-access memory]] (RAM), limited data storage capacities, and considerable variation in displays (technology, size, dimensions, resolution) and input methods (buttons, keyboards, touch screens with or without styluses).<ref>{{Cite web |date=2016-10-03 |title=Essential Aspects to Consider While Designing Mobile Apps {{!}} GlobalLogic UK |url=https://www.globallogic.com/uk/insights/blogs/essential-aspects-to-consider-while-designing-mobile-apps/ |access-dateplace=2023-06-24United Kingdom |website=GlobalLogic |language=en-gb |access-date=2023-06-24}}</ref> These applications (or 'apps') can be [[Installation (computer programs)|pre-installed]] on phones during manufacturing or delivered as web applications, using server-side or client-side processing (e.g., [[JavaScript]]) to provide an "application-like" experience within a [[web browser]].<ref>{{Cite web |title=What is a mobile app (mobile application)? – TechTarget Definition |url=https://www.techtarget.com/whatis/definition/mobile-app |access-date=2023-06-24 |website=WhatIs.com |language=en}}</ref>

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]] (EU) 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.<ref>{{Cite web |lastlast1=Atkinson |firstfirst1=Robert D. |title=The App Economy in Europe: Leading Countries and Cities, 2017 |date=October 2017 |url=https://www.progressivepolicy.org/wp-content/uploads/2017/10/PPI_EuropeAppEconomy_2017_.pdf |website=Progressive Policy Institute |access-date=3 October 2024}}</ref>

== Overview ==

Line 37:

Notable tools are listed below.

==== First-Party party ====

First party tools include official [[software development kit|SDK]]s published by, or on behalf of, the company responsible for the

Line 90:

|}

==== Second Partyparty ====

{| class="wikitable sortable" style="font-size:90%"

Line 112:

|}

==== Third Partyparty ====

{| class="wikitable sortable" style="font-size:90%"

Line 404:

|-

! [[Unity (game engine)|Unity]]

| [[C Sharp (programming language)|C#]], [[JavaScript]], [[Boo (programming language)|Boo]], other [[.NET Framework|.NET]]-based languages

| {{Yes}}

| Remote used to simulate device interaction before app is uploaded to the device.

Line 413:

|-

! [[Verivo]] AppStudio

| WYSIWYG, graphical drag and drop, [[JavaScript]], [[.NET Framework|.NET]]-based languages.; Replacedreplaced by Appery.io

| {{Yes}}

| Test right in browser or device

Line 431:

|-

! [[V-Play Engine]]

| [[Objective -C]], [[C++]], [[JavaScript]], [[QML]], [[Java (programming language)|Java]]

| {{Yes}}

| {{Yes}}

Line 440:

|-

! Wakanda

| [[HTML5]], [[JavaScript (programming language)|JavaScript]]

| {{Yes}}

| {{Yes}}

Line 452:

| {{Yes}}

| {{Yes}}

|Xamarin Studio (Mac only; deprecated), Visual Studio (Windows only), Visual Studio for Mac (Mac only; replaced Xamarin Studio)<ref name="xamarinrebrand">{{cite webnews |last1=Linev |first1=Roman |date=2016-11-14 |url=https://winaero.com/microsoft-rebrands-xamarin-studio-as-visual-studio-for-mac/ |title=Microsoft rebrands Xamarin Studio as Visual Studio for Mac |first=Roman |last=Linev |date=2016-11-14 |work=Winaero |accessdateaccess-date=2023-03-05 }}</ref><ref name="zdnetxamarin">{{cite webnews |last1=Foley |first1=Mary Jo |date=2017-05-10 |url=https://www.zdnet.com/article/microsoft-makes-visual-studio-for-mac-generally-available/ |title=Microsoft makes Visual Studio for Mac generally available |work=ZDNet |quote=Microsoft is making its Visual Studio for Mac --– a rebranded version of Xamarin Studio for the Mac --– generally available. |first=Mary Jo |last=Foley |access-date=2017-05-10 |accessdate=2023-04-02 |work=ZDNet }}</ref>

|Android, iOS, Windows Phone, Windows Store apps

|The native distribution of each platform

Line 515:

|-

! Wakanda

| [[JavaScript (programming language)|JavaScript]]

| Use Wakanda Studio

| Android, iOS (iPhone, iPad), Windows Phone 10 (soon), HTML5 app

Line 684:

Mobile applications are first tested within the development environment using emulators and later subjected to [[field testing]]. [[Emulator]]s provide an inexpensive way to test applications on mobile phones to which developers may not have physical access. The following are examples of tools used for testing applications across the most popular [[mobile operating system]]s.

* '''Google Android Emulator''' -– an [[Android (operating system)|Android]] emulator that is patched to run on a Windows PC as a standalone app, without having to download and install the complete and complex [[Android SDK]]. It can be installed and Android compatible apps can be tested on it.

* '''The official Android SDK Emulator''' -– a mobile device emulator which mimics all of the hardware and [[software]] features of a typical mobile device (without the calls).

* '''TestiPhone''' -– a [[web browser]]-based [[simulator]] for quickly testing [[iPhone]] [[web applications]]. This tool has been tested and works using [[Internet Explorer 7]], [[Firefox 2]] and [[Safari 3]].

* '''iPhoney''' -– gives a [[pixel]]-accurate web browsing environment and it is powered by [[Safari (web browser)|Safari]]. It can be used while developing [[web sites]] for the [[iPhone]]. It is not an iPhone simulator but instead is designed for web developers who want to create 320 by 480 (or 480 by 320) websites for use with iPhones. iPhoney will only run on [[OS X]] 10.4.7 or later.

* '''BlackBerry Simulator''' -– There are a variety of official BlackBerry simulators available to emulate the functionality of actual BlackBerry products and test how the device software, screen, keyboard and [[trackwheel]] will work with the application.

* '''Windows UI Automation''' -– To test applications that use the Microsoft UI Automation technology, it requires Windows Automation API 3.0. It is pre-installed on Windows 7, Windows Server 2008 R2 and later versions of Windows. On other operating systems, you can install it using Windows Update or download it from the [[Microsoft]] Web site.

* '''MobiOne Developer''' Developer -– a [[mobile Web]] [[integrated development environment]] (IDE) for [[Windows]] that helps developers to code, test, debug, package and deploy mobile [[Web application]]s to devices such as [[iPhone]], [[BlackBerry]], [[Android (operating system)|Android]], and the [[Palm Pre]]. MobiOne Developer was officially declared End of Life by the end of 2014.<ref>{{cite web |title=MobiOne Developer 1.0 M4: Create App Store-ready Mobile Web Applications, Experience True Device Behavior on Windows |url=https://www.prweb.com/releases/iphone/10/prweb2980934.htm |archive-url=https://web.archive.org/web/20091008093929/http://www.prweb.com/releases/iphone/10/prweb2980934.htm |url-status=dead |archive-date=8 October 2009 |website=PRWeb |access-date=31 May 2021}}</ref>

Tools include

* [[Eggplant (GUI testing tool)|eggPlantFunctional]]: A– GUI-based automated test tool for mobile apps across all operating systems and devices.

* [[Ranorex]]: – Test automation tools for mobile, web and desktop apps.

* [[Testdroid]]: – Real mobile devices and test automation tools for testing mobile and web apps.

== Design principles ==

According to a 2020 Industry Report on Applications, 46% of [[mobile app]] users have stated that they have stopped using or uninstalled an app due to poor performance.<ref name=":0">{{Cite web |date=2020-01-06 |title=Apps Statistics, Usage & Downloads (2020 report) |url=https://saasscout.com/statistics/apps-statistics/ |access-date=2024-02-20 |website=SaaS Scout (formerly SoftwareFindr) |language=en-US}}</ref> Design experts advocate for the following design principles to create successful and effective mobile apps:

'''Clutter-free screens:''' – Keeps interactions quick and simple, allowing users to focus on one specific task rather than being overwhelmed with multiple features and tasks. Design experts strongly advocate for one task per screen and recommend breaking down long forms into pages and progressively revealing new tasks or fields to minimize clutter.<ref name=":1">{{Cite web |title=15 Mobile App Design Best Practices |url=https://www.thoughtspot.com/data-trends/best-practices/mobile-app-design-best-practices |access-date=2024-02-20 |website=ThoughtSpot |language=en}}</ref>

'''Reduce cognitive load:''' – Makes userthe journeyuse throughof the app as seamless as possible, and preserves natural flow through the app. Design experts suggest incorporating [[autocomplete]], [[Spell checker|spell-check]], [[Predictive text|predictionpredictive text]] assistance]], and [[dropdown menu]]s to reduce cognitive load. Design experts also recommend the state of the app be preserved when users temporarily leave the app and re-enter so that users can continue their journeyuse from where they have left off.<ref name=":1" /><ref name=":2">{{Cite web |lastlast1=Cordini |firstfirst1=Marcelo |date=2021-01-06 |title=The best mobile app design: Examples |url=https://qubika.com/blog/mobile-app-design/ |access-date=2024-02-20 |website=Qubika |language=en-US}}</ref>

'''Simple navigation:''' – Around 11% of people have uninstalled apps due to their complicated [[Interface (computing)|interface]].<ref name=":0" /> Design experts state it is paramount to present the navigation bar visibly in your app to help users navigate to frequently used and high-priority screens instantly. They suggest the use of recognizable icons specific to the device operating system to help users easily take actions such as opening a menu, changing settings, going back a screen, and searching within a page. According to them, a user should not be confused while navigating the app, so an orderly, clear, and logical navigation flow drives engagement and discovery in the app.<ref name=":1" /><ref name=":2" />

'''Notifications:''' – It’s reported that around 19% of users uninstall an app due to frequent push notifications.<ref name=":0" /> Notifications should be sent with careful planning according to design experts. Experts state notifications should be sent at a time most convenient to users in their time zone and the messages should be personalized to bring great value to them.<ref name=":1" />

'''Speed Appearance:'appearance'' – About 19% of people uninstall apps due to hang up issues.<ref name=":0" /> Design experts state it’s important to make sure the app is fast and responsive so that users don’t have to wait for content. They state developers should deliver content faster or give the perception of progress. Some approaches suggested by the experts are the use of skeleton screens which show the layout of the app with content grayed out, [[progress bar]]s or loading spinners, tasks being carried out in the background and delivering the content quickly when the user requests for it, or giving users some tasks or content while they are waiting for a page to load.<ref name=":1" />

'''Usability:''' – Approximately 85% of mobile users use their phone with one hand,<ref name=":0" /> thus design experts state it is important that the top-level menu, frequently used controls, and common action items are within the reach of the user’s thumb. They also stress the importance of readability and it’s recommended that the text size is at least 11 point font so that users can read it at the typical reading distance without zooming in.<ref name=":1" /> It is recommended that headers and titles on the app screens be [[San Francisco font|San Francisco]] 17pt and [[Roboto]] 16sp for operating systems [[iOS]] and [[Android OS(operating system)|Android]] respectively.<ref name=":2" /> The experts also state there should be 4.5:1 minimum [[contrast ratio]] between text and the background color.<ref name=":1" /> Design experts strongly encourage developers to make apps accessible for all users including people with [[Disability|disabilities]], so they suggest features such as [[Virtual assistant|voice navigation]], [[screen reader]] compatibility, and user interface adaptability in mobile apps.<ref name=":2" />

==Patents==

Line 739:

==References==

{{reflistReflist}}

{{Mobile operating systems}}

{{Mobile phones}}