Mobile Application Development: Analysis Of Application Types And Tools

1y ago
6 Views
2 Downloads
6.11 MB
148 Pages
Last View : 1m ago
Last Download : 3m ago
Upload by : Arnav Humphrey
Transcription

POLITECNICO DI MILANOScuola di Ingegneria Industriale e dell InformazioneMaster of Science in Computer EngineeringDipartimento di Elettronica e InformazioneMobile Application Development:Analysis of Application Types and ToolsSupervisor:Prof. Elisabetta Di NittoMaster Graduation Thesis by:Saloni KyalMatricola: 919127Academic Year 2019-2020

- To God for blessing me with such parents, teachers, and friends.- To my parents for their constant support in all forms.- To my teachers for bringing out the best of me.- To my friends for their belief in me.

SummaryMobile applications provide valuable tools to customers and prospects across mobile devices. There are more than a million different types of mobile apps in use,each offering a wide variety of services. As mobile apps grow in the businessworld, the array of application types and tools for mobile app development escalates. With various incoming choices, as we get the flexibility of app development,we also go into the dilemma of choosing a mobile app development approach.This thesis aims to overcome the above confusion by the analysis of applicationtypes and tools used for developing each application type. This thesis performs ananalysis of 5 application types and 12 tools. It is performed by following three approaches: Systematic Literature Review, Google Survey, and the Implementationof the reference applications of each app type using all the tools/frameworks examined in this thesis. The application types can be a mobile website, an advancedmobile website called progressive web apps, native (android) apps, a combinationof native and web apps called hybrid apps, or cross-platform apps that can runin multiple platforms with the same code, unlike native apps. The topmost 2-3tools/frameworks for developing each app type is selected based on the statisticsfrom Google Trend supported by a preliminary survey conducted for mobile appdevelopers. The application types and tools are compared according to variousfactors identified, accompanied by creating a mobile application called WeatherWatch using all the tools analyzed. Another survey intended for users helps tointerpret tools by operating the developed app.The analysis suggests that there is no clear winner for the choice of both application types and tools. Every application type has its strengths and weakness.Likewise, every app development tool has its pros and cons, so there is no definitive judgment. It solely depends on which approach suits an individual’s mobileapp development needs that are comprehended by the acknowledged comparisonfactors in this thesis.Keywords: Mobile Application Development, Approach, Types, Mobile Web,Progressive Web, Native, Android, Hybrid, Cross-platform, Tools, Frameworks,Sencha ExtJS, jQuery Mobile, React, Angular, Android Studio, IntelliJ IDEA,Eclipse, Ionic, Phone Gap, React Native, Flutter, Xamarin.I

SommarioLe applicazioni mobili forniscono strumenti preziosi a clienti e potenziali clienti sudispositivi mobili. Esistono più di un milione di diversi tipi di app mobili in uso,ognuna delle quali offre un’ampia varietà di servizi. Man mano che le app mobilicrescono nel mondo degli affari, la gamma di tipi di applicazioni e strumenti perlo sviluppo di app mobili aumenta. Con varie scelte in arrivo, man mano cheotteniamo la flessibilità dello sviluppo di app, affrontiamo anche il dilemma discegliere un approccio allo sviluppo di app mobili.Questa tesi mira a superare la confusione di cui sopra mediante l’analisi deitipi di applicazioni e degli strumenti utilizzati per lo sviluppo di ciascun tipo diapplicazione. Questa tesi esegue un’analisi di 5 tipi di applicazioni e 12 strumenti. Viene eseguito seguendo tre approcci: Revisione sistematica della letteratura, Google Survey e l’implementazione delle applicazioni di riferimento diciascun tipo di app utilizzando tutti gli strumenti / framework esaminati in questatesi. I tipi di applicazione possono essere un sito Web per dispositivi mobili, unsito Web per dispositivi mobili avanzato denominato app Web progressive, appnative (Android), una combinazione di app native e Web denominate app ibride oapp multipiattaforma che possono essere eseguite su più piattaforme con lo stessocodice , a differenza delle app native. I 2-3 strumenti / framework più in alto perlo sviluppo di ciascun tipo di app vengono selezionati in base alle statistiche diGoogle Trend supportate da un sondaggio preliminare condotto per gli sviluppatori di app mobili. I tipi di applicazioni e gli strumenti vengono confrontati in basea vari fattori individuati, accompagnati dalla creazione di un’applicazione mobiledenominata Weather Watch utilizzando tutti gli strumenti analizzati. Un altrosondaggio destinato agli utenti aiuta a interpretare gli strumenti azionando l’appsviluppata.L’analisi suggerisce che non esiste un vincitore chiaro per la scelta dei tipi diapplicazione e degli strumenti. Ogni tipo di applicazione ha i suoi punti di forzae di debolezza. Allo stesso modo, ogni strumento di sviluppo di app ha i suoi proe contro, quindi non c’è un giudizio definitivo. Dipende esclusivamente da qualeapproccio si adatta alle esigenze di sviluppo di app mobili di un individuo che sonocomprese dai fattori di confronto riconosciuti in questa tesi.II

AcknowledgmentsThis thesis was not the result of the effort of a single soul. I can be as prolificor as adept in my respective field, but this journey was resilient due to the assistance of several individuals. I would like to appreciate all of them for their support.Foremost, I express sincere gratitude to my supervisor, Prof. Elisabetta Di Nitto,who guided me throughout this project. Her guidance, motivation, patience, andappreciation helped me to complete the work much before I expected it to finish.I would also like to thank my friends and family for encouraging me and offeringdeep insight into the study. Their contribution in the distribution of the surveyconducted for the thesis helped me to get significant responses.Finally, I am indebted to the university, Politecnico Di Milano, for allowing me towitness this incredible experience.III

AcronymsAPI Application Programming Interface.APK Android Application Package.CDN Content Delivery Network.CLI Command Line Interface.CMD Command Prompt.CPU Central processing Unit.CSS Cascading Style Sheets.DOM Document Object Model.FCA Formal Concept Analysis.GNSS Global Navigation Satellite System.GPS Global Positioning System.GPU Graphical processing Unit.GWT Google Web Toolkit.HTML Hyper Text Markup Language.IDE Integrated Development Environment.iOS iPhone Operating System.IPA iOS App Store Package.IT Information Technology.JS Java Script.IV

JSON JavaScript Object Notation.JSX JavaScript XML.JVM Java Virtual Machine.MAD Mobile Application Development.MGWT Mobile Google Web Toolkit.MVC Model View Controller.MVVM Model View ViewModel.NFC Near-field Communication.NPM Node Package Manager.OS Operating System.PHP Hypertext Preprocessor.PWA Progressive Web App.QR Quick Response Code.RQ Research Question.SDK Software Development Kit.SIP Session Initiation Protocol.SLR Systematic Literature Review.UI User Interface.URL Uniform Resource Locator.USB Universal Serial Bus.UX User Experience.XAML Extensible Application Markup Language.XML Extensible Markup Language.

List of omparingComparingMobile Web Application Development Tools . . .Progressive Web Application Development ToolsAndroid Application Development Tools . . . . .Hybrid Application Development Tools . . . . .Cross-platform Application Development Tools .19212324263.13.23.33.43.53.63.73.8Developer Survey Result - Respondents Experience & PreferenceSystematic Literature Review approach . . . . . . . . . . . . . .Search Strategy evolution . . . . . . . . . . . . . . . . . . . . .Publication Sources for Selected Studies . . . . . . . . . . . . .Distribution of Selected Studies (Year-Wise) . . . . . . . . . . .Distribution of Selected Studies among Research Questions . . .Choosing a development approach for mobile app . . . . . . . .Comparing Application Types based on Development Model . 114.124.134.144.154.16Weather Watch logo . . . . . . . . . . . . . . . . . . . . . . . . .API response from Open Weather Map . . . . . . . . . . . . . . .Frameworks with the respective technologies used for the implementation process . . . . . . . . . . . . . . . . . . . . . . . . . . .Github repository with pushed implementation code . . . . . . . .Sencha ExtJS - Weather Watch Screenshots . . . . . . . . . . . .jQuery Mobile - Weather Watch Screenshots . . . . . . . . . . . .Angular Framework - Weather Watch Screenshots . . . . . . . . .React Library - Weather Watch Screenshots . . . . . . . . . . . .Android Studio - Weather Watch Screenshots . . . . . . . . . . .IntelliJ IDEA - Weather Watch Screenshots . . . . . . . . . . . .Ionic - Weather Watch Screenshots . . . . . . . . . . . . . . . . .Phone Gap - Weather Watch Screenshots . . . . . . . . . . . . . .React Native - Weather Watch Screenshots . . . . . . . . . . . . .Flutter - Weather Watch Screenshot . . . . . . . . . . . . . . . . .Xamarin - Weather Watch Screenshots . . . . . . . . . . . . . . .Time taken for Learning Technology and Tools & Implementation5.1User Survey Results distribution . . . . . . . . . . . . . . . . . . . . 103VI. 71. 74.7577788082838586889092949597

List of Tables3.13.23.33.43.53.63.7Identifying keywords and synonyms for SLR search . . .Overview of Search Results of Sources . . . . . . . . . . .Comparison of Mobile Web App Development Tools . . .Comparison of Progressive Web App Development ToolsComparison of Android App Development Tools . . . . .Comparison of Hybrid App Development Tools . . . . . .Comparison of Cross-platform Development Tools . . . .383956596264674.14.24.34.44.54.6Implementation using Mobile Web App Development Tools . . .Implementation using Progressive Web App Development ToolsImplementation using Android App Development Tools . . . . .Implementation using Hybrid App Development Tools . . . . . .Implementation using Cross-Platform App Development Tools .Quantitative Analysis of Implemented Application . . . . . . . .7881848891966.16.2Ranking of application types corresponding to each factor . . . . .Implementation parameters effectiveness ranked for each application types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Winning framework for each category in each type of mobile application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Preferred framework for each criteria based on implementation experience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Users perspective based on implementation . . . . . . . . . . . . .Developers Survey Results Combined . . . . . . . . . . . . . . . .User survey Results Combined . . . . . . . . . . . . . . . . . . . .6.36.46.56.66.7. 108. 108. 110.111112113113D.1 Inclusion and Exclusion Criteria corresponding to RQs . . . . . . . 131D.2 Inclusion and Exclusion Criteria for other categories . . . . . . . . . 132VII

msIVList of FiguresVIIList of TablesVII1 Introduction1.1 Context . . . . . . . .1.2 General Overview . . .1.3 Research Approach . .1.3.1 Identification .1.3.2 Implementation1.3.3 Survey . . . . .1.4 Thesis Structure . . . .2 Background2.1 Application Type Description . . . . . . . .2.1.1 Mobile Web App . . . . . . . . . . .2.1.2 Progressive Web App . . . . . . . . .2.1.3 Native Apps . . . . . . . . . . . . . .2.1.3.1 Android Apps . . . . . . . .2.1.3.2 iOS Apps . . . . . . . . . .2.1.4 Hybrid Apps . . . . . . . . . . . . .2.1.5 Cross-platform Apps . . . . . . . . .2.1.6 Hybrid vs Cross-platform Apps . . .2.2 Tools/Frameworks Description . . . . . . . .2.2.1 Most used Tools for Mobile Web AppVIII.11455778. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Development.101011121314151516171818.

edToolsToolsToolsToolsforforforforProgressive Web App Development .Native Apps - Android DevelopmentHybrid Apps Development . . . . .Cross-platform Apps Development .3 Identification - State of the Art3.1 Developers Survey . . . . . . . . . . .3.1.1 Survey Questions . . . . . . . .3.1.2 Target Group . . . . . . . . . .3.1.3 Response . . . . . . . . . . . .3.2 Literature Reviews . . . . . . . . . . .3.3 Systematic Literature Review . . . . .3.3.1 Research Questions . . . . . . .3.3.2 Search Strategy . . . . . . . . .3.3.2.1 Identifying Keywords .3.3.2.2 Defining Search String3.3.2.3 Data Source Selection3.3.3 Inclusion/Exclusion Criteria . .3.3.4 Data Extraction & Analysis . .3.3.5 Selected Studies Overview . . .3.3.6 Combining Results . . . . . . .3.3.6.1 Results for RQ1 . . .3.3.6.2 Results for RQ1.1 . . .3.3.6.3 Results for RQ2 . . .3.3.6.4 Results for RQ2.1 . . .3.3.6.5 Results for RQ2.2 . . .3.3.6.6 Results for RQ2.3 . . .3.3.6.7 Results for RQ2.4 . . .3.3.6.8 Results for RQ2.5 . . .4 Implementation - Experimentation with Tools4.1 Introduction . . . . . . . . . . . . . . . . . . . .4.2 Application Prototype - Weather Watch . . . .4.2.1 User Interface . . . . . . . . . . . . . . .4.2.2 Sensors . . . . . . . . . . . . . . . . . . .4.2.3 Interaction with other Apps . . . . . . .4.2.4 Connectivity . . . . . . . . . . . . . . . .4.2.5 Open Weather Map API . . . . . . . . .4.3 Implementation Experience . . . . . . . . . . .4.3.1 Mobile Web App . . . . . . . . . . . . .4.3.1.1 Sencha ExtJS . . . . . . . . . .4.3.1.2 JQuery Mobile . . . . . . . . .4.3.2 Progressive Web App . . . . . . . . . . 58616365.70707171727272737476777980.

4.44.54.3.2.1 Angular . . . . . .4.3.2.2 React . . . . . . .4.3.3 Native Apps - Android . . .4.3.3.1 Android Studio . .4.3.3.2 IntelliJ IDEA . . .4.3.3.3 Eclipse . . . . . . .4.3.4 Hybrid Apps . . . . . . . .4.3.4.1 Ionic . . . . . . . .4.3.4.2 Phone Gap . . . .4.3.5 Cross-platform Apps . . . .4.3.5.1 React Native . . .4.3.5.2 Flutter . . . . . .4.3.5.3 Xamarin . . . . . .Metrics evaluation . . . . . . . . .Implementation threats to validity .5 User’s Perspective5.1 Categorization . . . . . . . . .5.1.1 User Interface . . . . .5.1.2 User Experience . . . .5.1.3 Run time Performance5.2 Users Survey . . . . . . . . .5.2.1 Survey Questions . . .5.2.2 Target Group . . . . .5.2.3 Response . . . . . . .5.2.4 Threats to validity . 021031056 Discussion & Analysis of Results6.1 Application Types . . . . . . . . . . . .6.1.1 Systematic Review . . . . . . . .6.1.2 Based on Implementation . . . .6.2 Tools/Framework . . . . . . . . . . . . .6.2.1 Systematic Review . . . . . . . .6.2.2 Implementation . . . . . . . . . .6.2.2.1 Developer’s Perspective6.2.2.2 User’s Perspective . . .6.2.3 Survey . . . . . . . . . . . . . . .6.2.3.1 Developer’s Perspective6.2.3.2 User’s Perspective . . .106106106108109109111111112112112113.7 Conclusion1147.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1147.2 Future Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Bibliogrpahy117A Developers Survey Form121B Users Survey form126C List of Search Strings129D Inclusion Exclusion Criteria131E Formal Concept Analysis133F Gartner Hype Cycle134

Chapter 1Introduction“The mobile device has become our communications hub, our diary, our entertainmentportal, our primary source of media consumption, our wallet, and our gateway to real-timeinformation tailored to our needs. The revolution is now!”Nihal Mehta, Founding General Partner at Eniac Ventures1.1ContextMobile applications provide valuable tools to customers and prospects across mobile devices such as smartphones, tablets, and an ever-increasing array of wearabledevices such as smartwatches. There are more than a million different types ofmobile apps in use, each offering a wide variety of services.Sports, games, organizers, shopping, banking, reading, watching, listening,one cannot imagine any of these without mobile devices. Mobile phone users arethe most important factor when we talk about mobile applications because thenumber of mobile phone users defines the usage of mobile applications. Accordingto Statista [1], the current number of smartphone users in the world today is3.5 billion, and this means 45.15% of the world's population owns a smartphonewhereas 4.78 billion people own a mobile phone which is 61.67% of the world'spopulation.The increasing number of mobile phone users makes an increase in the numberof mobile applications in various app stores more significant. There were 500 appson the first version of Apple's App Store and a handful of apps in Google PlayStore in 2008. We have come a long way since then. As of the first quarter of2020 [2], Android users can choose between 2.56 million apps, making GooglePlay App Store the biggest store of mobile applications. Apple’s App Store is thesecond-largest app store with almost 1.85 million available apps for iOS followedby Windows and Blackberry apps.

IntroductionM.A.DThe increasing number of mobile device users and apps has no significance onits own. Apps cannot succeed without downloads. We are seeing growth in appdownloads each year. This trend will continue in the coming years as well. In thesecond quarter of 2020, users downloaded 28.7 million apps from Google Play. Incontrast, the mobile app only generated 9.1 million downloads in the Apple AppStore. The Google Play platform has always made up the bulk of app downloadsbut the Apple App Store is stronger in terms of revenue generation. [3]. That'sa 15% increase from the year prior. Experts predict that there will be a 25%increase in global app downloads by 2022.Talking about the revenue generated by these apps, According to Build fire[4], mobile applications are expected to generate 189 billion dollars by 2020. If weanalyze a portion of the company's sales come from mobile devices then we findout, a mobile-friendly site makes it 67% more likely that a customer will buy aproduct or service online.With all these big numbers of mobile device users, demand for mobile application, and the benefit of revenue received from mobile application development,it is evident how significant mobile apps have become both for developers and theusers. For users, because they get several mobile application options to choosefrom, which makes their life easier in all aspects. For developers, because of therise in demand and revenue each year and increasing options to develop. However,these various choices for developers come with several confusions.As mobile apps grow in the business world, companies face a problem: Misconceptions still surround mobile app development. Many businesses venture intomobile app development without truly understanding the difference between eachapproach. Others enter the mobile app world with false beliefs about the prosand cons of each method, that could cost them hundreds of thousands of dollars.Depending on the business objectives and overall product goals, the decision ofcorrect application type and the tools to develop each type of mobile applicationcan make or break the success of the mobile strategy. With various incomingchoices, as we get the flexibility of development, we also go into the dilemma ofchoosing a mobile app development approach.The purpose of this Master’s thesis is to clear the confusion, to better understand which mobile app approach is right and which tool/framework wouldbe preferable for each approach. Not just for big companies and businesses buteven for small startups or freelance developers or even individuals like studentsor learners, knowing the approach and the preferred tool/framework for each approach would be beneficial. We will go into the pros and cons of each type andtool which will help the reader better understand chronologically which approachwill be best suited, given the following requirements of a company/individual. Foreach approach, the best use case and business model will also be given to buildexamples for better understanding.Various top mobile app development companies prefer native developmentMaster ThesisPage 2

IntroductionM.A.Dwhen organizations think about smooth app performance. Native developmentfacilitates a user to experience inbuilt device features in the app and easily interact with it. For example: For an app concept that needs camera support. Nativedevelopment enables to integrate device camera with the app and use it hassle-free.With the surging enthusiasm towards the development of apps for mobile devices,there has been a myriad of questions & lots of confusion over cross-platform vs native vs hybrid app vs web apps development approaches, particularly from novicedevelopers. The lack of enough end-to-end resources for choosing the right mobileapp approach has continued to serve as a major barrier to find a lasting solutionfor the iOS vs Android battle. Even so, given that both platforms are critical for afruitful mobile app strategy, but with the changing time, things are taking a newshape.Before moving forward, a small introduction of all the types of mobile applications will help to provide a better understanding.1. Mobile Web Application: These are mobile-friendly websites.2. Progressive Web Application: These are the advanced version of mobilefriendly websites that can use a device sensor, can run offline, can be savedon the home screen as a thumbnail, and with more extra features.3. Native Application: These are mobile applications that need to be installedon phones and are platform-specific, meaning separate development is donefor Android, iOS, Windows, and other platforms. Android Application: These are mobile applications that can be installed in android devices.4. Hybrid Application: These are like native applications but with the blend ofweb elements.5. Cross-platform Application: As the name suggests, cross-platform apps aremeant to run in all platforms with the same code.Native, mobile web, hybrid, or cross-platform. For companies considering mobile apps, that is the million-dollar question. The answer is, “It depends”. Itdepends on budget, time to market, reach, functionality, and other factors. Onemight value each option against variables like cost, time, available resources, andthe complexity of the project but no one has been able to optimize for all valuablesand still build something meaningful. It is a saying, Pick two factors out of fourand choose wisely! [5]For each type of mobile app (web/native/hybrid/cross-platform), there are numerous tools, platforms, and technologies to choose from. The selection of platformsmight depend upon the learning curve for each platform, usability, extensibility,etc. It is the next important decision to make once the correct type of mobileMaster ThesisPage 3

IntroductionM.A.Dapplication is selected.1.2General OverviewThis thesis involves the discussion of 2 major topics.The first topic is Analyzing Application Types. The choice among differenttypes of mobile applications is dependent upon several categories, including business needs, app requirements, developer skills, and timelines. In this thesis, weanalyze the types of applications, based on the development model and try tounderstand which approach or type of mobile application is suitable for differentindividuals/companies considering several categories by mentioning about the prosand cons of each type. The analysis is done using the systematic review method (Insimple words, research analysis of current existing work) which helps to categorizethem based on the development model. Also, the results from the implementationprocess of the thesis, where different types of mobile apps are implemented usingseveral tools/frameworks help to validate the results from the scientific reviewmethod. Five different types of applications are analyzed in the thesis- MobileWeb, Progressive Web, Native-Android, Hybrid, and Cross-platform apps. Fornative apps, only the android platform is chosen to be analyzed, because of theunavailability of iOS devices required for iOS apps development.The second topic is Analyzing Tools/Frameworks. Here, the tools/ frameworks for each type of mobile app is analyzed. 2-3 tools/frameworks for each typeof mobile application is selected by Google Trend statistics and compared usingscientific literature review and developing the same reference application with multiple frameworks trying to highlight the main characteristics of these frameworksas they result from the implementation experience. A simple mobile app is madeusing each platform to better understand the platform and technologies used in itto develop different types of mobile applications.There are several other tools/frameworks available for each type of mobile application not covered in the thesis, which can be equally useful given the requirementsof developer and user, but the most used, ranked and trended frameworks amongthem are selected to be analyzed in this thesis. The tools/frameworks analyzedfor each type in this thesis are given below:1. Mobile Web App: Sencha ExtJS, jQuery Mobile2. Progressive Web App: Angular Framework, React Library3. Native - Android: Android Studio, IntelliJ IDEA, Eclipse4. Hybrid App: Ionic, Phone Gap5. Cross Platform App: React Native, Flutter, XamarinMaster ThesisPage 4

Introduction1.3M.A.DResearch ApproachThis thesis follows the following approaches for the analysis of types and tools:Identification (3), Implementation(4), and Survey (3 and 5). Before following theabove approaches the tools to be analyzed are selected by the help of GoogleTrend(2).1.3.1IdentificationThe validation of the selected tools is performed by a preliminary developers surveywhich is followed by identification. Identification means to identify the categoriesand factors based on which they will be differentiated. This work is carried byusing systematic review method [6], where we can find the answer of the researchquestions by reading several papers, articles and work related to that field andthen combining the result to draw conclusions and make decisions.”Scientific review is a review that attempts to collate all empirical evidence thatfits pre-specified eligibility criteria to answer a specific research question using explicit, systematic methods to minimize bias, thus providing more reliable findingsfrom which conclusions can be drawn and decisions made.”Altman 1992, Oxman 1993Analyzing Application TypesAfter following the above method, the set of factors were identified which canbe used to differ the various application types. These categories help the companyor individual to understand which type of mobile application is well-suited fortheir business or need. The following set of factors were identified, a very shortdescription for each of them is provided below:1. Platform compatibility: Mobile app works in a single platform or more thanone platform. Except for native, almost all other apps can work on morethan one platform, but this is also dependent on the platform.2. User friendly: Requirement of the rich and attractive interface and experienceor it can be compromised. Native apps are headliners in UI and UX.3. Native functionality: Access to device sensors, interaction with other applications installed, etc. Here also, native apps are a winner.4. Internet accessibility: It can work with or without internet access. Only forthe mobile web, mandatory internet is required.5. Code portability: This defines the flexibility of the development process.Master ThesisPage 5

IntroductionM.A.D6. Development Cost: The budget varies for each application type, dependingon the available funding, individual/company can decide which type. Nativeis the most expensive, whereas mobile web apps being the least expensive.7. Development Time: The time required for development is also dependentupon the skills of the developers and their knowledge about the technology.8. Performance: The performance of the app, based on interactivity, consistency, power, slow, or fast. Native apps give the best performance.9. Demand: The reach in the market in terms of usage as well as revenue.Analyzing Tools and FrameworksWith the help of the scientif

Likewise, every app development tool has its pros and cons, so there is no de ni-tive judgment. It solely depends on which approach suits an individual's mobile app development needs that are comprehended by the acknowledged comparison factors in this thesis. Keywords: Mobile Application Development, Approach, Types, Mobile Web,

Related Documents:

Strategy 6: Mobile Workload Mobile devices are increasingly driving mainframe workloads April 2014: Mobile Workload Pricing – 60% reduction in mobile workload CPU to R4HA peak MUST be from mobile device MUST show connection to mobile device – Mobile Safari good – Desktop Safari not good Mobile to mainframe is .

The Definitive Guide to Enterprise Mobile Development The definitive guide to Enterprise Mobile Development v1.1 - 2 Table of contents Architecture of a Mobile Platform 3 Push notifications Design and build Mobile services 4 Deploying mobile applications Publish Mobile Services 6 Continuous Integration Connecting to backend data 7 Config Legacy Connectors 8 Cloud or on premises

Tutorial: iOS Object API Application Development Tutorial: Windows Object API Application Development Tutorial: Windows Mobile Object API Application Development Create a mobile business object, then develop a hybrid app package that uses it: Tutorial: Hybrid App Package Development Create an OData mobile application .

2.2. Mobile application Mobile applications are a kind of software application design and developed for mobile device platform, such as smartphone and tablet PC. Native application and web application are the two major categories of mobile applications (Charland & Leroux, 2011). Even though

the mobile marketing activities performed by retailers are the creation of mobile websites and development of mobile shopping applications, mobile customer service, communication through mobile email and messaging, mobile advertising and mobile couponing (Thakur, 2016). The fashion industry is globally worth more than 2 trillion (McKinsey, 2020).

The mobile operating system (MOS) place a key role in the development of mobile application since the application for one MOS is not compatible with other MOS. Therefore, before developing the mobile application for a particular application the MOS must be considered and the application must be developed for the same. T.

Mobile Communication Services . Offerings Detail Samsung SDS America Public Sector Capabilities Mobile ERP Health IT Mobile Groupware SAP Mobile BI Dashboard Oracle/Siebel Mobile CRM for Pharmaceutical Sales Mobile Device Management Mobile Applications (Android OS) . Android Mobile App & UI. 10 Offerings Detail Conceptual .

Field density and field moisture determinations shall be made according to ASTM D 6938. 501.07.04.02 Method A The Contractor is responsible for establishing QC procedures. Page 5 Rev. Date: 11/2014 OPSS.MUNI 501 501.07.04.03 Method B 501.07.04.03.01 General When Method B is specified in the Contract Documents, QC compaction testing shall be based on material placed and compacted in the Work on .