DOCSLIB.ORG

Evaluating Frameworks for Creating Mobile Web Apps

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Evaluating Frameworks for Creating Mobile Web Apps Evaluating Frameworks for Creating Mobile Web Apps Henning Heitkotter,¨ Tim A. Majchrzak, Benjamin Ruland and Till Weber Department of Information Systems, University of Munster,¨ Munster,¨ Germany [email protected], [email protected], benjamin.ruland, tillweber1986 @gmail.com { } Keywords: App, Mobile Web App, Framework, Cross-platform, Comparison, Evaluation, User Interface. Abstract: Mobile Web apps are an alternative to native apps when developing mobile applications for more than one platform. They can be accessed from almost any current smartphone and tablet using a browser. However, de- veloping a Web app adapted to the particularities of mobile devices such as limited screen size and touch-based interaction requires consideration and effort. Several frameworks with different strengths and weaknesses sup- port creating mobile Web apps. In this paper, we develop a set of criteria to be met by mobile Web frameworks of high quality. Based on these criteria, we evaluate jQuery Mobile, Sencha Touch, The-M-Project, and Google Web Toolkit combined with mgwt, thereby assessing their suitability for certain situations. We find Sencha Touch suited for mobile Web apps of moderate and increased complexity, while jQuery Mobile is a good starting point for apps primarily concerned with a mobile user interface. 1 INTRODUCTION using a platform’s source development kit (SDK) and should be employed if truly native performance and look & feel are desirable. Unfortunately, the require- Mobile devices such as smartphones and tablets are ments for Web apps on mobile devices differ from still gaining popularity among consumers and enter- Web apps in general. To effectively implement them prises (Gartner, 2012). In some areas they are already or to make existing Web apps suitable for mobile de- replacing – rather than just complementing – PCs and vices, sophisticated framework support is advisable. laptops. For software developers, mobile devices are An abundance of available frameworks hampers an a blessing and a curse at the same time. Obviously, easy selection, though. Moreover, there is hardly any there is a demand for new apps, and the devices of- guidance for informed decision-making. fer novel possibilities such as GPS positioning and – of course – truly mobile usage. At the same time, To fill this gap, it is important to evaluate frame- a variety of platforms such as Android or iOS (Lin works based on sound criteria. In this paper, we and Ye, 2009), a variety of frameworks, and a lack describe our criteria-based evaluation process, which of best practices make it cumbersome to implement can be sketched as follows: Based on typical require- them. If multiple platforms have to be supported, ef- ments of apps and on an extensive set of information fort increases almost linearly with the number of plat- resources, we derive eleven qualitative criteria. These forms. This leads to a need for cross-platform devel- criteria, accompanied by corresponding assessment opment. guidelines, are then used to evaluate four frameworks. In the last decade, companies have significantly Background information and, more importantly, own invested in Web technology (Chatterjee et al., 2002; experience are the foundation for judging to what de- Basu et al., 2000). More and more, applications that gree a framework fulfills a certain criterion. do not require rich clients for profound reasons (e. g., Our paper makes a number of contributions. First, integrated development environments or professional we describe a novel set of evaluation criteria use- media editing tools) are provided as Web apps. Users ful beyond their application in this paper. Second, merely require a Web browser to use them. we evaluate the frameworks in detail and give oper- The ambition to support multiple platforms and ationalizable decision advice. Third, we contribute to existing knowledge of Web technologies make Web the theory with a discussion of implications of our re- apps an interesting choice for app development. In search. By outlining which approaches look promis- general, they promise to offer almost as good plat- ing and where current frameworks lack features, we form support as native apps. The latter are developed highlight areas for further research and development. 209 Presented at WEBIST 2013. WEBIST2013-9thInternationalConferenceonWebInformationSystemsandTechnologies This paper is structured as follows. Related work to make a decision on a higher-level: Web app or not. is studied in Section 2. Section 3 introduces the con- The research design is similar to this article, while cept of mobile Web apps and presents the frameworks the outcome is of course different. Ohrt and Turau analyzed later, including their general characteristics. (2012) present a broad comparison of cross-platform Our evaluation criteria are developed in Section 4 and development tools, but do not consider mobile Web then used in Section 5 to evaluate the frameworks. apps. Section 6 discusses and summarizes the findings, be- fore we conclude in Section 7. 3 MOBILE WEB APPS 2 RELATED WORK This section examines mobile Web apps as a cross- platform approach to app development and introduces Our kind of research is literature-driven. There- four frameworks that will be analyzed later. fore, relevant citations are provided in the corre- sponding paragraphs throughout this paper. In this 3.1 General section, we distinguish our work from existing ap- proaches. The main observation is that there are no A Web application, short Web app, is a Web site all-encompassing reviews based on scientific criteria. that provides an application within browsers, as op- Rather, many papers evaluate single frameworks in posed to static content (Connors and Sullivan, 2010, isolation or a combination thereof. This most likely Sect. 1.3.2). It is built with Web technologies such as is owed to the novelty of the field of research. Nev- HTML5, CSS, and JavaScript to enable a dynamic ex- ertheless, these papers have made valuable contribu- perience. A mobile Web app is intended to be used on tions and in parts have been influential for our work. mobile devices. It may be a mobile-optimized version Several papers evaluate technologies for Web apps of an existing Web app. In contrast to standard mo- such as HTML5 (HTML5, 2012). With additions like bile apps, mobile Web apps are not installed on the offline support, HTML5 is particularly suited for mo- device (e. g., via an app store) but accessed through bile Web apps. This is also reflected in recently pub- the browser. Although built with the same set of tech- lished textbooks (e. g., (Oehlman and Blanc, 2011)). nologies, special requirements due to the mobile en- Assessment of HTML5 is positive (Harjono et al., vironment call for a different approach and specific 2010; Melamed and Clayton, 2009). Obviously, it is optimizations. mature enough for widespread usage (Lubbers et al., Mobile-specific requirements mainly stem from 2011). Typically, HTML5 and JavaScript are utilized limited screen size available on mobile devices, a dif- together (Meyer, 2011). ferent style of user interaction through touch gestures, Frameworks are often evaluated in the context of and the mobile context. The smaller screen of smart- app development. For example, in a comparison of phones and, to a lesser extent, of tablets requires a Web apps and native apps it makes sense to mention different user interface (UI) layout and mobile ver- jQuery mobile (Charland and Leroux, 2011). This sions of typical HTML elements. For example, a does not help to compare jQuery mobile to compet- multi-column layout is usually not feasible in mo- ing approaches, though. The same applies to work bile Web apps; instead, fixed toolbars for header or on HTML5 that includes framework recommenda- footer can provide universal navigation. Users inter- tions (e. g., (Curran et al., 2012)). The paper by act with their devices primarily through touch inter- Smutny goes a step further and briefly compares sev- action, which replaces the traditional pointer-based eral frameworks (Smutny, 2012). However, he does interaction combined with keyboard input. This re- not propose a catalogue of criteria for doing so. quires several adaptations. UI elements have to be Another thread of research is scenario-based eval- of sufficient size if users shall select them. Mobile uation of existing technologies. For example, Zibula Web apps should not expect the user to enter a large and Majchrzak (2012) use HTML5, jQuery Mobile, amount of text. They should, however, support ges- and PhoneGap to build an app for smart metering. tures as an additional means of interaction. The mo- However, while such papers help to understand the bile context includes more particularities that have to feasibility of possible technology stacks, they do not be accounted for such as limited hardware resources provide a greater image such as our work. and instable or slow network connections. Hence, Our previous paper on evaluating cross-platform mobile Web apps should optimize network requests. development approaches in general (Heitkotter¨ et al., Combined with nearly 100 best practices recom- 2012) presents complementary work. It thereby helps mended by the World Wide Web Consortium (W3C) 210 EvaluatingFrameworksforCreatingMobileWebApps for developing mobile Web pages (Connors and Sul- interface and high-class JavaScript to a wide range livan, 2010; Rabin and McCathieNevile, 2008), the of mobile devices. All prevalent operating sys- aforementioned requirements highlight the need for tems, namely Android, iOS, BlackBerry OS, Win- Web frameworks that support the development of mo- dows Phone and Symbian, are supported. Mobile bile Web apps. Hence, there are various suchlike Web apps using jQuery Mobile can also be packaged frameworks. In order to select promising frameworks with PhoneGap. The framework uses progressive en- for evaluation, we studied Web sites and literature hancement (Firtman, 2012), which adjusts the presen- dealing with mobile Web frameworks. jQuery Mo- tation according to supported features of displaying bile and Sencha Touch were mentioned most often devices.
Load more

Recommended publications
  • Sencha Touch and Ext JS Developer Description
    Sencha Touch and Ext JS Developer Description: Health Outcomes Worldwide (HOW), a diverse and rapidly growing Canadian company seeks a motivated developer to work with an agile virtual team creating cutting-edge web and mobile applications for use by healthcare professionals. HOW provides solutions used by nurses in healthcare environments across Canada. The mobile application is a hybrid HTML5 (Sencha Touch)/Cordova solution designed for tablet devices (iOS and Android). Plans for a revamped browser-based solution (using ExtJS 5) are also in development. The selected developer will play an integral role in both mobile and desktop solution design and development using Sencha tools. The ideal candidate will have: • 4+ years of extensive experience with Sencha Ext JS framework and 2+ experience with Sencha Touch framework. • In-depth knowledge of javascript. • Experience building iOS, Android, Windows and Blackberry apps with PhoneGap/ Cordova platform. • Solid knowledge of HTML5, CSS3, EcmaScript 6 and their integration in a standards-based fashion with each other. • Proficiency with the DOM and asynchronous event programming model. • Experience with cross-platform (PC/Mac, desktop, laptop, tablet) and cross-browser (IE, Firefox, Chrome, Safari) development. • Experience with AJAX, JSON and RESTful web services. • Server-side development with ASP.NET WebForms, ASP.NET MVC and Node.js. • Database design and programming using MS SQL Server and SQLite. • Familiarity with Design Patterns, particularly Model-View-Controller (MVC). • Experience with mobile development and Touch interfaces. • Solid understanding and experience with Agile software development methodologies. Qualified, interested parties should submit a resume to [email protected].
    [Show full text]
  • 85324630.Pdf
    About NetTantra NetTantra is a creative technology and design company based out of India, US and UK. We provide web based solutions and mobile solutions to various industries like manufacturing, consulting, education. We have expertise in various sectors of the web including an array of server-side languages, OpenSource CMS/Blog frameworks, Linux/UNIX system administration, production server backup and recovery solutions, cloud infrastructure set-up and much more. Our expertise in providing WordPress based solutions has been acclaimed by many of our clients and the OpenSource community. We also provide cloud based solutions like migrating existing applications and building cloud applications for public or private cloud setups. We are known among our clients for on-time delivery and extraordinary quality of service. In mobile based solutions, we have expertise in developing native applications for iOS and Android platforms. We also develop cross-platform mobile applications using Sencha Touch and jQuery Mobile frameworks. 2 of 14 pages Why Hire Us ✔ Technology ◦ We have expertise in the most cutting edge tools and technologies used in the industry with special focus on OpenSource Technologies ◦ We pay special attention to web and network security for all projects ◦ Our team follows highly optimized project delivery life cycles and processes ✔ Cost ◦ We offer the best price to quality ratio ✔ Infrastructure ◦ Advanced workstations ◦ Cutting edge computing and network systems ◦ Power packed online servers ◦ Smart communications systems ◦ Conference halls, CBT and video learning facilities ◦ High-speed uninterrupted Internet connection ✔ Quality of Service ◦ Guaranteed client satisfaction ◦ Real-time customer support with the least turn-around in the industry ◦ Pre-sales technical and business related support to partners and agencies ✔ Ethics and Principles ◦ We ensure confidentiality in all our dealings.
    [Show full text]
  • ODOT Default Web Application Architecture
    The Ohio Department of Transportation (ODOT) Division of Information Technology ODOT Default Web Application Architecture Filename:ODOT Web Application Architecture.doc Version: 8.0 Author: Michael Jordan Last Modified: 11/16/2017 Project Site: Document Summary: Prepared by the ODOT Division of Information Technology (DoIT) [Document Header] Contents 1 Introduction ......................................................................................................................... 3 1.1 About This Document ..................................................................................................... 3 1.2 Document Location ......................................................................................................... 3 2 Architecture ......................................................................................................................... 4 2.1 A Layered Approach ....................................................................................................... 4 2.1.1 User Interface Layer ............................................................................................... 4 2.1.2 Domain Layer ......................................................................................................... 4 2.1.3 Service Layer .......................................................................................................... 5 3 Technologies ....................................................................................................................... 6 3.1 Microsoft .NET Platform.................................................................................................
    [Show full text]
  • What Is Dart?
    1 Dart in Action By Chris Buckett As a language on its own, Dart might be just another language, but when you take into account the whole Dart ecosystem, Dart represents an exciting prospect in the world of web development. In this green paper based on Dart in Action, author Chris Buckett explains how Dart, with its ability to either run natively or be converted to JavaScript and coupled with HTML5 is an ideal solution for building web applications that do not need external plugins to provide all the features. You may also be interested in… What is Dart? The quick answer to the question of what Dart is that it is an open-source structured programming language for creating complex browser based web applications. You can run applications created in Dart by either using a browser that directly supports Dart code, or by converting your Dart code to JavaScript (which happens seamlessly). It is class based, optionally typed, and single threaded (but supports multiple threads through a mechanism called isolates) and has a familiar syntax. In addition to running in browsers, you can also run Dart code on the server, hosted in the Dart virtual machine. The language itself is very similar to Java, C#, and JavaScript. One of the primary goals of the Dart developers is that the language seems familiar. This is a tiny dart script: main() { #A var d = “Dart”; #B String w = “World”; #C print(“Hello ${d} ${w}”); #D } #A Single entry point function main() executes when the script is fully loaded #B Optional typing (no type specified) #C Static typing (String type specified) #D Outputs “Hello Dart World” to the browser console or stdout This script can be embedded within <script type=“application/dart”> tags and run in the Dartium experimental browser, converted to JavaScript using the Frog tool and run in all modern browsers, or saved to a .dart file and run directly on the server using the dart virtual machine executable.
    [Show full text]
  • TIBCO Activematrix® BPM Web Client Developer's Guide Software Release 4.3 April 2019 2
    TIBCO ActiveMatrix® BPM Web Client Developer's Guide Software Release 4.3 April 2019 2 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. ANY SOFTWARE ITEM IDENTIFIED AS THIRD PARTY LIBRARY IS AVAILABLE UNDER SEPARATE SOFTWARE LICENSE TERMS AND IS NOT PART OF A TIBCO PRODUCT. AS SUCH, THESE SOFTWARE ITEMS ARE NOT COVERED BY THE TERMS OF YOUR AGREEMENT WITH TIBCO, INCLUDING ANY TERMS CONCERNING SUPPORT, MAINTENANCE, WARRANTIES, AND INDEMNITIES. DOWNLOAD AND USE OF THESE ITEMS IS SOLELY AT YOUR OWN DISCRETION AND SUBJECT TO THE LICENSE TERMS APPLICABLE TO THEM. BY PROCEEDING TO DOWNLOAD, INSTALL OR USE ANY OF THESE ITEMS, YOU ACKNOWLEDGE THE FOREGOING DISTINCTIONS BETWEEN THESE ITEMS AND TIBCO PRODUCTS.
    [Show full text]
  • Attacking AJAX Web Applications Vulns 2.0 for Web 2.0
    Attacking AJAX Web Applications Vulns 2.0 for Web 2.0 Alex Stamos Zane Lackey [email protected] [email protected] Blackhat Japan October 5, 2006 Information Security Partners, LLC iSECPartners.com Information Security Partners, LLC www.isecpartners.com Agenda • Introduction – Who are we? – Why care about AJAX? • How does AJAX change Web Attacks? • AJAX Background and Technologies • Attacks Against AJAX – Discovery and Method Manipulation – XSS – Cross-Site Request Forgery • Security of Popular Frameworks – Microsoft ATLAS – Google GWT –Java DWR • Q&A 2 Information Security Partners, LLC www.isecpartners.com Introduction • Who are we? – Consultants for iSEC Partners – Application security consultants and researchers – Based in San Francisco • Why listen to this talk? – New technologies are making web app security much more complicated • This is obvious to anybody who reads the paper – MySpace – Yahoo – Worming of XSS – Our Goals for what you should walk away with: • Basic understanding of AJAX and different AJAX technologies • Knowledge of how AJAX changes web attacks • In-depth knowledge on XSS and XSRF in AJAX • An opinion on whether you can trust your AJAX framework to “take care of security” 3 Information Security Partners, LLC www.isecpartners.com Shameless Plug Slide • Special Thanks to: – Scott Stender, Jesse Burns, and Brad Hill of iSEC Partners – Amit Klein and Jeremiah Grossman for doing great work in this area – Rich Cannings at Google • Books by iSECer Himanshu Dwivedi – Securing Storage – Hackers’ Challenge 3 • We are
    [Show full text]
  • Cliente Twitter Con Compresión De Datos
    PROYECTO FIN DE GRADO GRADO EN INGENIERÍA INFROMÁTICA CLIENTE TWITTER CON COMPRESIÓN DE DATOS Autor: Plácido Fernández Declara Tutores: Luis Miguel Sánchez García Rafael Sotomayor Fernández Colmenarejo, Febrero de 2013 RESUMEN La popular red social Twitter es usada hoy en día en diversos lugares y momentos, gracias también a las redes móviles que nos proporcionan conexión a internet en casi cualquier lugar. Twitter permite publicar y mandar mensajes cortos de texto plano con un máximo de 140 caracteres, así como la lectura de estos mensajes cortos de otros usuarios a los que podemos seguir para tal propósito. Hacer uso de este servicio en zonas con buena cobertura, o cuando usamos Wi-fi no supone generalmente ningún problema. Es cuando nos encontramos en zonas de poca cobertura cuando vemos problemas para hacer uso de este servicio, ya que las velocidades de descarga pueden disminuir hasta el punto de necesitar decenas de segundos para disponer de los mensajes cortos, los “Tweets”. A esto hay que añadir que los planes de datos actuales están limitados de alguna forma (al alcanzar un número de Mb), por lo que la cantidad de Mb usada es hoy también un factor importante. Para ello esta aplicación ofrece la experiencia de un cliente Twitter sencillo en el que consultar los “Tweets” de a quien seguimos, así como publicar “Tweets”, haciendo uso de un Proxy que comprime estos datos considerablemente de forma que se reducen los tiempos de descarga para las zonas de poca cobertura y además se reduce el número de Mb consumidos por el dispositivo móvil. Índice de contenido RESUMEN .................................................................................................................................
    [Show full text]
  • Towards Secure and Reusable Web Applications
    Mashups and Modularity: Towards Secure and Reusable Web Applications Antero Taivalsaari Tommi Mikkonen Sun Microsystems Laboratories [email protected] http://research.sun.com/projects/lively 2 Evolution of the Web 1) Simple pages with text and static images only (e.g., http://www.google.com) 2) Animated pages with plug-ins (e.g., http://www.cadillac.com) 3) Rich Internet Applications (e.g., docs.google.com) What's Next? 3 Web Applications – Implications • Web-based software will dramatically change the way people develop, deploy and use software. • No more installations! > Applications will simply run off the Web. • No more upgrades! > Always run the latest application version. • Instant worldwide deployment! > No middlemen or distributors needed. • No CPU dependencies, OS dependencies, ... > The Web is the Platform. 4 Unfortunately... • The web browser was not designed for running real applications. > It was designed in the early 1990s for viewing documents, forms and other page-structured artifacts – not applications. > Programming capabilities on the web were an afterthought, not something inherent in the design of the browser. • Various Rich Internet Application (RIA) technologies have been introduced recently to retrofit application execution capabilities into the web browser. 5 Web Development vs. Conventional Software The Impedance Mismatch Web Development Conventional SW Development - Documents - Applications - Page / form oriented interaction - Direct manipulation - Managed graphics, static layout - Directly drawn, dynamic
    [Show full text]
  • Diseño De Un Sistema De Monitorización De Dispositivos Móviles
    Departamento de Informática PROYECTO FIN DE GRADO DISEÑO DE UN SISTEMA DE MONITORIZACIÓN DE DISPOSITIVOS MÓVILES Autor: Antonio Becerra López Tutor: Luis Miguel Sánchez García Colmenarejo, Septiembre de 2012 1 Diseño de un sistema de monitorización de dispositivos móviles Título: Diseño de un sistema de monitorización de dispositivos móviles Autor: Antonio Becerra López Director: EL TRIBUNAL Presidente: Vocal: Secretario: Realizado el acto de defensa y lectura del Proyecto Fin de Carrera el día __ de _______ de 20__ en Leganés, en la Escuela Politécnica Superior de la Universidad Carlos III de Madrid, acuerda otorgarle la CALIFICACIÓN de VOCAL SECRETARIO PRESIDENTE 1 2 Diseño de un sistema de monitorización de dispositivos móviles Resumen AndroidMonitor es un sistema cuya finalidad consiste en monitorizar distribuidamente dispositivos móviles con el sistema operativo Android. Los teléfonos móviles en la actualidad son un elemento indispensable más de las personas junto con las llaves de casa y la cartera con los documentos personales. En el año 2011, la población total de la Tierra superaba la asombrosa cantidad de siete mil millones de personas. En ese mismo año, se calculaba que el número de teléfonos móviles en el mundo era superior a los 5.600 millones. Los dispositivos móviles cuentan con gran variedad de sensores: acelerómetro, sensor de luz, sensor de temperatura, barómetro, sensor de gravedad, sensor de presión; Sensores que recopilan información de su entorno que puede ser utilizada para comprar la situación del terminal. El objetivo de este proyecto es el análisis, el diseño y el desarrollo de un sistema para monitorizar remotamente los valores de los sensores de dispositivos móviles.
    [Show full text]
  • Download the Index
    Dewsbury.book Page 555 Wednesday, October 31, 2007 11:03 AM Index Symbols addHistoryListener method, Hyperlink wid- get, 46 $wnd object, JSNI, 216 addItem method, MenuBar widget, 68–69 & (ampersand), in GET and POST parameters, addLoadListener method, Image widget, 44 112–113 addMessage method, ChatWindowView class, { } (curly braces), JSON, 123 444–445 ? (question mark), GET requests, 112 addSearchResult method JUnit test case, 175 SearchResultsView class, 329 A addSearchView method, MultiSearchView class, 327 Abstract Factory pattern, 258–259 addStyleName method, connecting GWT widgets Abstract methods, 332 to CSS, 201 Abstract Window Toolkit (AWT), Java, 31 addToken method, handling back button, 199 AbstractImagePrototype object, 245 addTreeListener method, Tree widget, 67 Abstraction, DAOs and, 486 Adobe Flash and Flex, 6–7 AbstractMessengerService Aggregator pattern Comet, 474 defined, 34 Jetty Continuations, 477 Multi-Search application and, 319–321 action attribute, HTML form tag, 507 sample application, 35 Action-based web applications Aggregators, 320 overview of, 116 Ajax (Asynchronous JavaScript and XML) PHP scripts for building, 523 alternatives to, 6–8 ActionObjectDAO class, 527–530 application development and, 14–16 Actions, server integration with, 507–508 building web applications and, 479 ActionScript, 6 emergence of, 3–5 ActiveX, 7 Google Gears for storage, 306–309 Add Import command Same Origin policy and, 335 creating classes in Eclipse, 152 success and limitations of, 5–6 writing Java code using Eclipse Java editor,
    [Show full text]
  • Arcgis API for Javascript: Building Native Apps Using Phonegap and Jquery
    Building Native Apps with ArcGIS API for JavaScript Using PhoneGap and jQuery Andy Gup, Lloyd Heberlie Agenda • Getting to know PhoneGap • jQuery and jQuery mobile overview • jQuery and ArcGIS API for JavaScript • Putting it all together • Additional information Technical workshops at Dev Summit • Web - Building Mobile Web Apps with the ArcGIS API for JavaScript • Hybrid - You are here! • Native - Search the agenda for “Runtime SDK” Application comparison: Native vs. Web • ArcGIS Runtime SDK for Android • https://developers.arcgis.com/android/guide/native-vs-web.htm • ArcGIS Runtime SDK for iOS • https://developers.arcgis.com/ios/objective-c/guide/native-vs-web.htm Hello Cordova and Resources Lloyd Heberlie Enable Safari remote web inspection What is PhoneGap? • Application container technology • Core engine is 100% open source • Web view container, plus JS API • HTML5, CSS3, JS = Native App PhoneGap PhoneGap architecture PhoneGap PhoneGap Application Native Plugins Code App PhoneGap Plugins PhoneGap Plugin options Setup a developer machine Code quality and verification web server Source Control Preparing for PhoneGap Installing PhoneGap and Apache Cordova Check versions of PhoneGap and Apache Cordova Updating PhoneGap and Apache Cordova Creating your first PhoneGap CLI project phonegap create path/to/my-app "com.example.app" "My App" Hello Cordova (cont.) Lloyd Heberlie PhoneGap: Featured Apps Featured Apps: Tripcase, Untappd Agenda • Getting to know PhoneGap • jQuery and jQuery mobile overview • jQuery and ArcGIS API for JavaScript •
    [Show full text]
  • Apache Cordova Training
    Apache Cordova Cross-Platform Mobile Application Development Duration: 3 Days (Face-to-Face & Remote-Live), or 21 Hours (On-Demand) Price: $1695 (Face-to-Face & Remote-Live), or $1495 (On-Demand) Discounts: We offer multiple discount options. Click here for more information. Delivery Options: Attend face-to-face in the classroom or remote-live attendance. Students Will Learn The jQuery Mobile Toolkit Introduction to Apache Cordova (PhoneGap) Style Class Manipulation Using the Contacts Database API DOM Manipulation Using the the Cordova File API Introduction to Ajax Accessing the Camera with Cordova Using jQuery Mobile Lists, Forms, Buttons and Themes Using the Accelerometer Overview of Geolocation Course Description Apache Cordova (formerly PhoneGap) is an open-source is a mobile application development framework. It utilizes HTML5, CSS3 and JavaScript to create apps for a variety of mobile platforms. Students will learn how to build applications using jQuery Mobile and Apache Cordova that run on a variety of mobile platforms including iOS, Android and Windows Mobile. Comprehensive hands on exercises are integrated throughout to reinforce learning and develop real competency. Course Prerequisites Knowledge of HTML and JavaScript equivalent to attending the Website Development with HTML5, CSS and Bootstrap and JavaScript Programming courses. Course Overview The Mobile Landscape Technology Stack Devices Types HTML5 Main Objectives Browser-Side Data Storage Smartphones Tablets Declaring HTML5 Device Convergence Detecting Support for HTML5
    [Show full text]