DOCSLIB.ORG

Edetailing With

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Edetailing With Sustainable Business Relationship Building Through Digital Strategy Solutions Development of Mobile Applications Overview . Introduction . History of Mobile Applications . Current State of Mobile Applications . The Future of Mobile Applications . Development Introduction • A mobile application (or mobile app) is a software application designed to run on smart phones, tablet computers and other mobile devices. History of Mobile Application The history of the mobile app begins, obviously, with the history of the mobile device. The first mobile phones had microchips that required basic software to send and receive voice calls. But, since then, things have gotten a lot more complicated. NX3 Mobile Application Development Services Native And Non-Native Frameworks Native Application Environment: . Android . iOS . Windows Phone 8 . BlackBerry 10 Non-Native Application Environment: . Phone Gap . Titanium Mobile Android . Based on the Linux kernel, Android started life as a proposed advanced operating system for digital cameras until the company realized that the market was limited compared to that for mobile phones. The Open Handset Alliance unveiled the Android operating system in 2007, nearly two years after Google’s acquisition of Android. The launch of Google’s foray into the mobile world was delayed by the launch of the iPhone, which radically changed consumers’ expectations of what a smartphone should do. IOS . Apple’s iPhone set the standard for the new generation of smartphones when it was first released in June 2007 with its touchscreen and direct manipulation interface. There was no native SDK until February of 2008 (Apple initially planned to provide no support for third-party apps). The iOS lineage started with Next STEP, an object-oriented multitasking OS from the late eighties developed by NeXT Computer (acquired by Apple in 1996). The world’s first web browser was developed on Next STEP and proved hugely influential in the formative years of HTML. The main programming language for iOS is Objective C. Development is done through Xcode IDE which has an in-built iOS simulator. Windows Phone 8 . The second generation of the Windows Phone operating system uses the same Metro interface but has an updated architecture based on the Windows NT kernel (like Windows 8) rather than Windows CE (which was used as the basis for Windows Phone 7). You can develop for Windows Phone 8 only on a system running Windows 8 – using Visual Studio 2012 as an IDE. You’re allowed to choose between XAML, Direct3D or a mixture for building UIs; you can write C#, Visual Basic apps on top of .NET; and you can use C++ for native code. Publication is less flexible. Apps need to be put through a review process before being allowed into the store similar to iOS. The low take up of Windows Phone makes this process seem rather onerous. Blackberry 10 . Originally named BBX, BlackBerry 10 is based on the QNX microkernel operating system whose parent company RIM acquired in 2010. BlackBerry 10 uses a system of gestures and touches which is supposed to make physical buttons unnecessary for core functions (e.g. a ‘back’ or ‘home’ button). The OS also has an Android runtime layer so that Android apps can be packaged and distributed on the BlackBerry platform. (The latest versions even allow the direct download of apps via Google Play.) . Native application development utilises an API library in C and a Native API in C/C++ though you can eschew C++ coding through the WebWorks framework (HTML5 and JS), Adobe AIR or Java itself. Again the publishing process is rather onerous: 10 business days are required to approve your app. Non-Native Application Environment . It is of course possible to sidestep the issues that come with developing native apps by instead developing web apps for use on mobile devices. The advantage to developing web-based apps are clear: you immediately solve the proliferation problem; you can ‘write once, run anywhere’; and you can use common web-based languages like HTML5, CSS and JavaScript. Some frameworks allow you to build ‘hybrid’ apps which are not truly native (since their layout rendering is done via web views) or totally webbased (since they’re packaged for distribution and have access to native APIs). The disadvantages of hybrid apps are that you only get limited access to the native functionality of the phone on which the app runs and that such apps are usually slower than ‘pure’ native apps. PhoneGap . PhoneGap supports most major platforms (iOS, Android, BlackBerry, Windows Phone, Palm WebOS, Bada and Symbian) and allows developers to make use of native hardware features like accelerometers, compasses and cameras. A cloud based compilation engine – PhoneGap Build – generates compatible apps for all supported . Platforms but rejection of PhoneGap-built apps by the Apple App Store is still a frequent issue. It’s based on Apache Cordova which also underpins the aforementioned WebWorks. Titanium Mobile . iOS, Android, BlackBerry and Windows Phone apps can all now be created via Appcelerator’s Titanium framework. Application source code is interpreted on the mobile device using a JavaScript engine (Rhino on Android and BlackBerry, Javascriptcore on iOS). Titanium provides fast results, making it a popular prototyping tool but (as with PhoneGap) performance issues abound and code forking is often required (e.g. if iOS then…). The Future of Mobile Application Development . Wearable Technology Miniaturization has made wearable what once would have been unthinkably cumbersome – sophisticated computers and communication devices can now be incorporated into wristbands, glasses or even clothes themselves. The market of ‘wearable tech’ is estimated to exceed $12 billion by 2018. Google Glass Released to developers in 2013 Google Glass is an ‘augmented reality’ device that is set to get a consumer launch at some point this year. David Thompson has seen a demo of Glass and his opinion is that while the product still has a long way to go before fulfilling the promise of genuine AR, the possibilities are exciting. It can record images and video and can almost be entirely controlled by voice alone when in operation. The Future of Mobile Application Development . Galaxy Gear Samsung’s smart watch, like most smart watches released to date (cf. Pebble and Smartwatch 2), met with a universally poor reception when released in September 2013. Fuel Band The Nike+ Fuel Band was a simple but effective foray into the wearable tech space from the sportswear manufacturer. The Fuel Band is worn on the wrist and tracks physical activity, allowing users to share and compare stats via the Nike+ online community. Mobile Application by NX3 - Medilexis • Medilexis is a mobile application designed for medical practitioners to conveniently maintain electronic medical records. It eases the transformation required at the clinic/practice for EMR adoption, eliminates training and allows seamless automation of both clinical and billing functions. That frees physicians from the chores of the practice so they can focus on well being of patients and meeting their revenue targets. Objective Keeping records of patient health information is imperative for medical practitioners. This process is handled through transcription service providers, in house transcriptionists or electronic medical record systems. However, all these are time consuming, costly and cumbersome. Physicians have been finding it convenient to dictate their patient information which can then be transcribed, reviewed, signed and stored easily. The primary objective of medical practitioners is to spend most of their time on patient care. They keep looking for solutions to free up their time from administrative work so they can focus fully on patient care. This application does exactly that. Execution Our team at NX3 with its extensive experience in the healthcare industry and valuable interactions with medical practitioners over the years envisioned and developed the Medilexis App based on the valuable feedback from the doctors themselves. The focus of this app was to eliminate the difficulties the doctors were facing in connection with patient records. The user interface of this application has been designed in such a way that it is seamless and self-explanatory. It does not require any training and can be used easily by just downloading it from the app store into their personal mobile phones. Results Medilexis App allow medical practitioners to add and dictate complete patient encounter directly into their cell phones which includes: . Adding patient demographics . Scheduling appointments . Search for patients . Dictate chief complaint, history of present illness, family history, review of systems, assessment and plan . Add medications with dosage information . Add images and mark them . Add procedural and diagnostic codes Physicians can record their dictation and transcribe the voice into text instantly by tapping a button. They can also type their notes directly and save them. They can do it remotely from anywhere and on the go without requiring any internet connection. The patient encounters can then be synced to our servers at a later time when the internet service is available. The patient data remains available to them to be retrieved anytime from our servers. Thank you. About NX3 NX3 Corporation NX3 is a one stop solution for all your digital needs. Using advanced digital platforms like Marketo and Salesforce for coaching, marketing and enablement, NX3 has a knack for transforming your business in a matter of months. We lay special emphasis on developing a very personal relationship with our customers. At NX3, we aspire to create a customized individualistic experience through our services not only for our customers but for their customers as well in a chain of steps carefully designed in the form of a customer journey. We execute across multiple channels to achieve maximum traction for our clients..
Load more

Recommended publications
  • Texting on a Smartwatch Versus a Smartphone: a Comparison of Their Effects on Driving Performance
    TEXTING ON A SMARTWATCH VERSUS A SMARTPHONE: A COMPARISON OF THEIR EFFECTS ON DRIVING PERFORMANCE A Dissertation by Joel Persinger Master of Arts, Wichita State University, 2014 Bachelor of Science, Eastern Kentucky University, 2005 Submitted to the Department of Psychology and the faculty of the Graduate School of Wichita State University in partial fulfillment of the requirements for the degree of Doctor of Philosophy December 2017 ©Copyright 2017 by Joel A. Persinger All Rights Reserved TEXTING ON A SMARTWATCH VERSUS A SMARTPHONE: A COMPARISON OF THEIR EFFECTS ON DRIVING PERFORMANCE The following faculty members have examined the final copy of this dissertation for form and content, and recommend that it be accepted in partial fulfillment of the requirement for the degree of Doctor of Philosophy, with a major in Psychology. _____________________________________________ Rui Ni, Committee Chair _____________________________________________ Alex Chaparro, Committee Member _____________________________________________ Barbara Chaparro, Committee Member _____________________________________________ Jibo He, Committee Member _____________________________________________ Jeremy Patterson, Committee Member Accepted for the College of Liberal Arts and Sciences _______________________________________________ Ron Matson, Dean Accepted for the Graduate School _______________________________________________ Dennis Livesay, Dean iii DEDICATION To my beautiful wife, who has pushed me to go further than I ever thought I could. She has truly carried me though graduate school with love and encouragement. iv ABSTRACT The National Safety Council reports that 6 percent or more car crashes involved text messaging from a smartphone. In addition, many studies have found that cell phone while driving increases crash risk by 2.8–5 times (Klauer et al. 2006; Redelmeier and Tibshirani 1997; Violanti 1998; Violanti and Marshall 1996).
    [Show full text]
  • Augmented Reality
    Augmented Reality: A Review of available Augmented Reality packages and evaluation of their potential use in an educational context November 2010 Stephen Rose Dale Potter Matthew Newcombe Unlocking the Hidden Curriculum University of Exeter Learning and Teaching Innovation Grants (04/08) 2 Contents 1. Augmented Reality Page 4 2. Augmented Reality in Education 6 3. Augmented Reality Applications 8 3.1 Marker-based Augmented Reality 8 3.2 Markerless Augmented Reality 10 4. Available Augmented Reality Technologies 12 4.1 Current Smartphone Ownership Patterns 12 4.2 Platforms 16 4.3 AR Software 19 5. Technical Considerations 22 5.1 Limitations of Current Platforms 24 6. Choosing an Augmented Reality System 24 7. Glossary 28 8. References 29 9. Appendix 1: Unlocking the Hidden Curriculum - a JISC- 31 funded Learning and Teaching Innovation Project at the University of Exeter This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 2.0 Licence. To view a copy of this licence, visit: http://creativecommons.org/licenses/by-nc-sa/2.0/uk or send a letter to: Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA. 3 1. ‘Augmented Reality’ Every now and again a ‘new technology’ appears which seems to capture the public imagination. Invariably the technology enables a new means of interacting with screen-based entertainment or a computer game - 3DTV, the Nintendo Wii. The proliferation of so-called ‘smartphones’ with their abilities to run once-complex computer applications, in-built cameras and ‘GPS’ capability has unleashed the potential of ‘Augmented Reality’ – to date a regular feature of science fiction or ‘near future’ movies.
    [Show full text]
  • The Usage of Smartphone and Mobile Applications from the Point of View of Customers in Poland
    information Article The Usage of Smartphone and Mobile Applications from the Point of View of Customers in Poland Witold Chmielarz Faculty of Management, University of Warsaw, 00-927 Warsaw, Poland; [email protected] Received: 20 March 2020; Accepted: 15 April 2020; Published: 17 April 2020 Abstract: The main objective of this article was to identify the conditions for the use of smartphones and mobile applications in Poland in the second half of 2018. The scope of the present analysis was limited to a selected sample of more than 470 respondents, and it examined the group of the most active users of smartphones and mobile applications. The author adopted the CAWI (computer associated web interview) method, which was previously verified by a randomly selected pilot sample, in his study. The obtained results were compared with the findings of other studies. They indicated that users of smartphones and mobile applications in Poland do not differ in their assessments from users in Europe and around the world. In this context, the key implication for researchers is the identified level of development of the use of smartphones and mobile applications in Poland at the end of 2018. The main limitation of the research was the selection of the research sample, which consisted only of members of the academic community. The scope of this article aimed to fill a gap in terms of the quantitative and qualitative methods that are applied to examine the use of mobile devices and mobile software. At the same time, this study creates the foundations for further research on intercultural differences.
    [Show full text]
  • Practicalizing Delay-Tolerant Mobile Apps with Cedos
    Practicalizing Delay-Tolerant Mobile Apps with Cedos YoungGyoun Moon, Donghwi Kim, Younghwan Go, Yeongjin Kim, Yung Yi, Song Chong, and KyoungSoo Park Department of Electrical Engineering, KAIST Daejeon, Republic of Korea {ygmoon, dhkim, yhwan}@ndsl.kaist.edu, [email protected], {yiyung, songchong}@kaist.edu, [email protected] ABSTRACT 1. INTRODUCTION Delay-tolerant Wi-Fi offloading is known to improve overall mo- Wi-Fi has become the most popular secondary network interface bile network bandwidth at low delay and low cost. Yet, in reality, for high-speed mobile Internet access on mobile devices. Many we rarely find mobile apps that fully support opportunistic Wi-Fi mobile apps support the “Wi-Fi only” mode that allows the users to access. This is mainly because it is still challenging to develop shun expensive cellular communication while enjoying high band- delay-tolerant mobile apps due to the complexity of handling net- width and low delay. In addition, cellular ISPs are actively de- work disruptions and delays. ploying Wi-Fi access points (APs) to further increase the mobile In this work, we present Cedos, a practical delay-tolerant mobile Internet access coverage [1, 2, 3]. network access architecture in which one can easily build a mo- However, current Wi-Fi usage is often statically bound to the lo- bile app. Cedos consists of three components. First, it provides a cation of mobile devices. While this “on-the-spot” Wi-Fi offloading familiar socket API whose semantics conforms to TCP while the is still effective, recent studies suggest that one can further extend underlying protocol, D2TP, transparently handles network disrup- the benefit of Wi-Fi access if we allow delay tolerance between net- tions and delays in mobility.
    [Show full text]
  • Securing and Managing Wearables in the Enterprise
    White Paper: Securing and Managing Wearables in the Enterprise Streamline deployment and protect smartwatch data with Samsung Knox Configure White Paper: Securing and Managing Wearables in the Enterprise 2 Introduction: Smartwatches in the Enterprise As the wearable device market heats up, wrist-worn devices Industries as varied as healthcare, such as smartwatches are leading the pack. According to CCS Insight, forecasts for global sales of smart wearable devices finance, energy, transportation, will grow strongly over the next five years, with the global public safety, retail and hospitality market reaching nearly $30 billion by 2023.1 are deploying smartwatches for While smartwatches for fitness and activity tracking are popular, consumer demand is only part of the equation. added business value. Enterprises are also seeing business value in wearable devices. In a report by Robert Half Technology, 81 percent of CIOs surveyed expect wearable devices like smartwatches to Samsung has been working to address these concerns and become common tools in the workplace.2 has developed the tools to make its Galaxy and Galaxy Active smartwatches customizable, easily manageable and highly secure for enterprise users. This white paper will look at how these tools address key wearable security and manageability challenges, as well as considerations for smartwatch 81% deployments. of CIOs surveyed expect wearable devices like smartwatches to become common tools in the workplace. Industries as varied as healthcare, finance, energy, transportation, public safety, retail and hospitality are deploying smartwatches for added business value, such as hands-free communication for maintenance workers, task management, as well as physical monitoring of field workers in dangerous or remote locations.
    [Show full text]
  • Taxonomy of Cross-Platform Mobile Applications Development Approaches
    Ain Shams Engineering Journal (2015) xxx, xxx–xxx Ain Shams University Ain Shams Engineering Journal www.elsevier.com/locate/asej www.sciencedirect.com ELECTRICAL ENGINEERING Taxonomy of Cross-Platform Mobile Applications Development Approaches Wafaa S. El-Kassas *, Bassem A. Abdullah, Ahmed H. Yousef, Ayman M. Wahba Department of Computer and Systems Engineering, Faculty of Engineering, Ain Shams University, Egypt Received 13 September 2014; revised 30 May 2015; accepted 3 August 2015 KEYWORDS Abstract The developers use the cross-platform mobile development solutions to develop the Cross-platform mobile mobile application once and run it on many platforms. Many of these cross-platform solutions development; are still under research and development. Also, these solutions are based on different approaches Interpretation approach; such as Cross-Compilation approach, Virtual Machine approach, and Web-Based approach. There Cloud computing; are many survey papers about the cross-platform mobile development solutions but they do not Compilation approach; include the most recent approaches, including Component-Based approach, Cloud-Based Component-Based approach, and Merged approach. The main aim of this paper is helping the researchers to know approach; the most recent approaches and the open research issues. This paper surveys the existing cross- Model-Driven Engineering platform mobile development approaches and attempts to provide a global view: it thoroughly introduces a comprehensive categorization to the cross-platform approaches, defines the pros and cons of each approach, explains sample solutions per approach, compares the cross-platform mobile development solutions, and ends with the open research areas. Ó 2015 Faculty of Engineering, Ain Shams University. Production and hosting by Elsevier B.V.
    [Show full text]
  • Bancontact Payconiq Company
    Bancontact Payconiq Company SEPA Rulebooks Scheme Manuals Remote Domain 46D0 – Schedules 1, 2, and 3 – News 64 Mobile App Security Guidelines Android, iOS Newsletter 64 Classification: Confidential Confidential COPYRIGHT This document is confidential and protected by copyright. Its contents must not be disclosed or reproduced in any form whatsoever without the prior written consent of Bancontact Payconiq Company sa/nv. Except with respect to the limited license to download and print certain material from this document for non-commercial and personal use only, nothing contained in this document shall grant any license or right to use any of Bancontact Payconiq Company sa/nv’s proprietary material. AUTHORS This monthly newsletter is written by NVISO Labs, experts in mobile security, on behalf of Bancontact Company sa/nv. ABOUT NVISO NVISO is a consultancy firm exclusively focusing on IT security. NVISO has a very clear sector focus with several references in the financial and governmental sectors. The Research and Development department of NVISO is NVISO Labs, whose goals are to allow our people to increase their skills and knowledge, to come up with innovative service offerings, to contribute to the security community, and to give valuable insights to our clients. The fundamental values of NVISO are client satisfaction, focus, entrepreneurship, innovation, and ability to adapt. Our mission is to be an innovative and respected partner for our clients. For more information, we are happy to refer you to our website: https://www.nviso.be.
    [Show full text]
  • Apple and Nokia: the Transformation from Products to Services
    9 Apple and Nokia: The Transformation from Products to Services In the mid- to late 2000s, Nokia flourished as the world’s dominant mobile phone – and mobile phone operating software – producer. Founded in 1871 originally as a rubber boots manufacturer, by 2007 Nokia produced more than half of all mobile phones sold on the planet, and its Symbian mobile operating system commanded a 65.6 percent global market share. 1 But within half a decade, Nokia would falter and be surpassed in the smartphone market not only by Apple’s revolu- tionary iPhone but also by competitors including Google and Samsung. And in September 2013, Nokia would sell its mobile phone business to Microsoft for $7 billion. 2 Apple literally came out of nowhere – it sold exactly zero mobile phones before the year 2007 (the year Nokia held more than half of the global market share) – but by the first quarter of 2013, Apple had captured almost 40 percent of the US smartphone market and over 50 percent of the operating profit in the global handset industry.3 In fiscal year 2013, Apple would sell five times more smart- phones than Nokia: 150 million iPhones compared to Nokia’s sales of 30 million Lumia Windows phones. 4 In contrast to Nokia, Apple real- ized it wasn’t just about the mobile device itself, it was about leveraging software to create a platform for developing compelling mobile experi- ences – including not just telephony but also music, movies, applica- tions, and computing – and then building a business model that allows partners to make money alongside the company (e.g., Apple’s iTunes and AppStore) and, in so doing, perpetuate a virtuous cycle of making the iPhone attractive to customers over multiple life cycles through ever-ex- panding feature sets.
    [Show full text]
  • UI Design for Wearable Devices
    FACULTY OF ENGINEERING UNIVERSITY OF PORTO UI Design for Wearable Devices Vitor Mota Master in Informatics and Computing Engineering Supervised by: Miguel Pimenta Monteiro (Assistant professor) Pedro Rocha (GlinttHS) January 2015 2 Abstract Smartwatches have been around for some time now (Ranger 2015), but 2015 is the year this wearable technology will finally get its boom in terms of popularity and growth. Technology giants like Apple, Google and Samsung are betting on their own-line of products such as the Apple Watch, Android Wear and Gear respectively (Apple Inc 2015a; Google Inc 2015b; SAMSUNG 2015). All of these devices are computation capable electronics with very small touch capacitive screens, limited number of hardware buttons with varying screen sizes and even shapes. Our research focused mainly on these constraints and how to successfully develop user friendly GUI’s for such small screens. The goal was to develop a model with guidelines to help developers provide easy to use and user friendly applications at a visual and interaction level to end users. To successfully achieve this, we first took a deep look at the available technology within these devices, including the framework each of the major platforms provide and the underlying hardware capabilities such as sensors like GPS, gyroscope, the use of the touch screen or microphone for user input and whether the shape of the device (round or squared) can have different effects on the design and usability. We also analyzed the impact of placement and arrangement of interface components having in mind that this technology, since it is a wearable watch, can be worn on both wrists and therefore will be used with only one hand that may obscure a different portion of the interface depending on which wrist the user uses it (Chandra and Raghunath 2000).
    [Show full text]
  • Characterizing Smartwatch Usage in the Wild
    Characterizing Smartwatch Usage In The Wild Xing Liu1 Tianyu Chen1 Feng Qian1 Zhixiu Guo23 Felix Xiaozhu Lin4 Xiaofeng Wang1 Kai Chen25 1Indiana University Bloomington 2SKLOIS, Institute of Information Engineering, Chinese Academy of Sciences 3Beijing Jiaotong University 4Purdue ECE 5School of Cyber Security, University of Chinese Academy of Sciences ABSTRACT participants, we conduct an in-depth characterization of three key Smartwatch has become one of the most popular wearable aspects of smartwatch usage “in the wild”: usage patterns, energy computers on the market. We conduct an IRB-approved consumption, and network traffic characteristics. This is to our measurement study involving 27 Android smartwatch users. Using knowledge the most comprehensive and in-depth crowd-sourced a 106-day dataset collected from our participants, we perform in- study of smartwatches. Our key measurement results consist of depth characterization of three key aspects of smartwatch usage “in the following. the wild”: usage patterns, energy consumption, and network traffic. • We characterize the smartwatch usage patterns. An Android Based on our findings, we identify key aspects of the smartwatch watch can stay in one of the four states with diverse power ecosystem that can be further improved, propose recommendations, characteristics: fully awake, dozing (with dimmed watch face and point out future research directions. display and restricted system activity), sleeping (screen further turned off), and charging. We find that smartwatch’s wake-up CCS Concepts period accounts for only 2% of the overall usage period among • → the four states. The wake-up sessions are not only short, but Human-centered computing Ubiquitous and mobile also frequent (72 times per day on average).
    [Show full text]
  • Application Migration Guide - Bada C++ Application with Bada 2.0 to OSP-Compatible Tizen Application
    Application Migration Guide - bada C++ Application with bada 2.0 to OSP-compatible Tizen Application Except as noted, this content - excluding the Code Examples - is licensed under Creative Commons Attribution 3.0 and all of the Code Examples contained herein are licensed under Flora 1.0. For details, see the Content License. Application Migration Guide - bada C++ Application with bada 2.0 to OSP-compatible Tizen Application Table of Contents 1. Converting a bada Application to OSP-compatible Tizen Application ........ 5 1.1. System Migration ...................................................................................................................... 7 1.1.1. Case Sensitivity ........................................................................................................ 7 1.1.2. enum Type Size ........................................................................................................ 7 1.1.3. wchar_t Type Size ................................................................................................. 7 1.1.4. Member Variable Initialization .................................................................................. 7 1.1.5. malloc() Allocation ................................................................................................ 7 1.1.6. Strong Two Phase Construction Mechanism Check ................................................ 7 1.1.7. Pure Virtual Method Implementation ........................................................................ 8 1.1.8. LLVM Compiler ........................................................................................................
    [Show full text]
  • Critical Capabilities for Successful Mobile App Development
    7 Critical Capabilities Your Mobile App Development and Deployment Platform Must Include Speed Mobile App Development and Ensure Wide User Adoption Executive Summary In today's mobile business environment companies are scrambling to quickly mobilize hundreds of B2B and B2E business processes or legacy applications. There are three main approaches developers can use to build mobile business apps: - Responsive web apps - Native app development - "Native quality" hybrid apps This whitepaper explains important differences between these three approaches, outlines 7 mobile capabilities that real-world business apps require today, and identifies the most productive development approach for getting these mobile business apps to market FAST. 1 | P a g e High Demand for Mobile Apps For competitive and productivity reasons, businesses and organizations are embracing mobile more than ever. Gartner forecasts enterprise application software spending to double from $300B in 2013 to over $575B by the end of 2018.1 Yet, Gartner also predicts demand for enterprise mobile apps will outstrip available development capacity by five to one.2 Forrester warns: “The CIO who fails in mobile will lose his job.”3 As a result, companies are trying to find new ways to enable their employees to develop business apps. Everyone from young IT or business workers with basic HTML5 skills, to IT developers with limited mobile experience and business analysts are exploring how to build apps to get routine things mobilized faster. Rising End-User Expectations Complicating the problem is the rising expectations of an increasingly mobile workforce. Employees are adopting mobile devices exponentially and demanding more business apps to do their work.
    [Show full text]