DOCSLIB.ORG

Codename One and Phonegap, a Performance Comparison

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Codename One and Phonegap, a Performance Comparison Codename One and PhoneGap, a performance comparison Andreas Arnesson Faculty of Computing Blekinge Institute of Technology SE-371 79 Karlskrona Sweden 1 Contact Information: Author: Andreas Arnesson [email protected] University advisor: Nina Dzamashvili Fogelström Department of Software Engineering Faculty of Computing Internet : www.bth.se Blekinge Institute of Technology Phone : +46 455 38 50 00 SE-371 79 Karlskrona Sweden Fax : +46 455 38 50 57 2 ABSTRACT Creating smartphone applications for more than one operating system requires knowledge of several code languages, more code maintenance, higher development costs and longer development time. To make this easier cross-platform tools (CPTs) exist. But using a CPT can decrease performance of the application. Applications with low performance are more likely to get uninstalled and this makes developers lose income. There are four main CPT approaches hybrid, interpreter, web and cross-compiler. Each has different disadvantages .and advantages. This study will examine the performance difference between two CPTs, Codename One and PhoneGap. The performance measurements, CPU load, memory usage, energy consumption, time execution and application size will be made to compare the CPTs. If cross-compilers have better performance than other CPT approaches will also be investigated. An experiment where three applications are created with native Android, Codename One and PhoneGap will be made and performance measurements will be made. A literature study with research from IEEE and Engineering village will be conducted on different CPT approaches. PhoneGap performed best with shortest execution time, least energy consumption and least CPU usage while Codename One had smallest application size and least memory usage. The research available on performance for CPTs is short and not well done. The difference between PhoneGap and Codename One is not big except for writing to SQLite. No basis was found for the statement that cross-compilers have better performance than other CPT approaches. Keywords: cross-platform tools, approach, performance, android 3 Table of Contents Abstract ................................................................................................................................................... 3 1 Introduction .......................................................................................................................................... 6 2 Background and Related work ............................................................................................................. 8 2.1 Background .................................................................................................................................... 8 2.1.1 Performance priority .............................................................................................................. 8 2.1.2 How my code affects performance ........................................................................................ 8 2.1.3 Different CPT approaches ..................................................................................................... 10 2.1.4 Why I chose these CPTs ........................................................................................................ 11 2.1.5 Android ................................................................................................................................. 11 2.2 Related work ............................................................................................................................... 13 3 Research design .................................................................................................................................. 16 3.1 Literature design ......................................................................................................................... 16 3.2 Experiment design ....................................................................................................................... 16 3.2.1 How to test my applications: ................................................................................................ 17 3.2.2 Validity threats ..................................................................................................................... 19 3.2.3 Performance tips from research .......................................................................................... 19 3.2.4 Measuring tools .................................................................................................................... 20 4 Results ................................................................................................................................................ 21 4.1 Literature review ......................................................................................................................... 21 4.1.1 Answer to literature question .............................................................................................. 23 4.2 Experiment .................................................................................................................................. 25 4.2.1 Result from Sony V ............................................................................................................... 25 4.2.2 Samsung Galaxy Trend plus .................................................................................................. 28 4.2.3 Application size ..................................................................................................................... 32 5 Analysis ............................................................................................................................................... 33 5.1 Memory usage ............................................................................................................................. 33 5.2 CPU load ...................................................................................................................................... 34 5.3 Execution time ............................................................................................................................. 34 5.4 Energy consumption .................................................................................................................... 35 5.5 Application size ............................................................................................................................ 35 5.6 Validity threats ............................................................................................................................ 36 4 5.7 Summary...................................................................................................................................... 36 6 Conclusion and future work ............................................................................................................... 38 6.1 Conclusion ................................................................................................................................... 38 6.2 Future work ................................................................................................................................. 38 References ............................................................................................................................................. 39 Appendix A – Bubble sort ...................................................................................................................... 42 5 1 Introduction By Q4, 2014 the smartphone market can be divided into five parts, Android, iOS, Windows phone, Blackberry and other OS’s [30]. Figure 1- Worldwide Smartphone OS Market Share. These four operating systems and others each use different languages to develop applications. For developers and companies who want to expand their market share beyond one OS, they need to maintain several projects instead of one. With this an increase of development time, development cost, maintenance and a bigger knowledge base is needed. Luckily there is hope for developers because nowadays tools are available for developing applications for multiple OS’s at once, so called cross-platform tools (CPTs). They have also been called Write once run everywhere. The pros of using CPTs are: [16] - Less skill required from developer. - Less coding needed. - Less development time and maintenance cost. - Less API knowledge. - Easier to develop one app instead of one for each OS. - More market share. Another problem with smartphones is their limited resources, CPU, memory, battery and data. The worst thing for a developer or company is for their application to get uninstalled from user’s smartphones. There are a number of reasons for this to happen, abusing privacy, unstable behavior, advertisement, no need for it anymore, high memory allocation, poor interface, high battery usage, low performance and sluggish behavior e.tc. Some of these reasons, high memory allocation, poor 6 interface, high battery usage, low performance and sluggish behavior, correlate to performance, CPU usage, memory usage, execution time and battery consumption. This means that if an application has low performance that application has a much higher risk of getting uninstalled and then developers and companies loses income. This is why it’s important for developers to always have in mind the resource use of their applications [31]. Using CPTs can come at a cost of resources. Using CPTs can decrease performance of application compared to native applications [21, 22]. That’s why it
Load more

Recommended publications
  • Create an Uber Clone in 7 Days
    Create an Uber Clone in 7 Days Shai Almog 2018-07-22 Contents Preface. 1 Audience. 1 Prerequisites . 2 What you don’t need to Know . 2 Get this Book for FREE! . 2 How to Read this Book? . 3 Software Prerequisites . 4 Getting Help. 4 Using the Code. 4 Important Notice About Cloning and Copyrights . 5 Thanks and Acknowledgments . 5 1. Hello World . 7 1.1. What’s Codename One?. 7 1.1.1. Build Cloud . 8 1.2. Getting Started. 8 1.2.1. New Project. 8 Running . 11 The Source Code . 12 1.2.2. Run on Device . 18 Signing . 18 Build and Install . 25 1.3. How Does it Work? . 26 1.3.1. Mobile is Different . 26 Density (DPI/PPI) . 27 1.3.2. Performance. 29 App Size . 29 Power Drain . 30 1.3.3. Sandbox and Permissions . 30 1.4. Summary . 31 2. Core Concepts . 33 2.1. The Todo App. 33 2.2. Layouts and Hierarchy . 35 2.2.1. Layout Managers. 44 Terse Syntax . 47 2.2.2. Styles . 47 Designer Tool . 50 2.2.3. Event Handling . 68 Observers and Event Types . 69 Event Dispatch Thread. 71 2.2.4. IO and Storage . 72 2.3. Summary . 74 3. Spring Boot Overview . 75 3.1. What’s Spring Boot? . 75 3.2. Why Spring Boot . 76 3.3. What will we Use? . 76 3.4. Summary . 77 4. Day 1: The Mockup. 79 4.1. Deconstructing Uber . 79 4.1.1. Portrait Only UI . 81 4.1.2. iOS and Android Look Almost Identical .
    [Show full text]
  • Codename One
    Codename One #codename one Table of Contents About 1 Chapter 1: Getting started with Codename One 2 Remarks 2 Examples 2 Installation & Setup 2 Installation 2 Installing Codename One In NetBeans 2 Installing Codename One In Eclipse 5 Installing Codename One In IntelliJ IDEA 6 What is Codename One & How Does it Work? 6 How Does Codename One Work? 7 Why Build Servers? 8 Why ParparVM 9 Windows Phone/UWP 9 JavaScript Port 10 Desktop, Android, RIM & J2ME 10 Lightweight Components 10 Lightweight Architecture Origin 10 In Codename One 10 Versions In Codename One 11 Credits 12 About You can share this PDF with anyone you feel could benefit from it, downloaded the latest version from: codename-one It is an unofficial and free Codename One ebook created for educational purposes. All the content is extracted from Stack Overflow Documentation, which is written by many hardworking individuals at Stack Overflow. It is neither affiliated with Stack Overflow nor official Codename One. The content is released under Creative Commons BY-SA, and the list of contributors to each chapter are provided in the credits section at the end of this book. Images may be copyright of their respective owners unless otherwise specified. All trademarks and registered trademarks are the property of their respective company owners. Use the content presented in this book at your own risk; it is not guaranteed to be correct nor accurate, please send your feedback and corrections to [email protected] https://riptutorial.com/ 1 Chapter 1: Getting started with Codename One Remarks This section provides an overview of what codenameone is, and why a developer might want to use it.
    [Show full text]
  • Ios Push Notification Badge Auto Increment
    Ios Push Notification Badge Auto Increment Stereographical Hebert usually climaxes some Agatha or demarks propitiously. Jasper barbers compliantly? Ammoniacal Dietrich eternizes that hardwood acquired elementarily and box incapably. IP addresses are not stored in any Localytics analytics databases, but the location data generated from an IP lookup is, by default, collected and stored. Do to want but continue? Ensure that following instance is added to your Info. When you send across push notification with custom actions buttons, you may redirect users to incorporate custom feat or view but your app by specifying deep links as custom actions button URLs. If being check mostly and shipping is not included, how determined I get for that? Messaging as follows: request a system font colors based in auto view controller class values recorded only notification badge auto increment ios badge? This key contains the deeplinking URL if deficient during the campaign creation. Who within those one who comments? This is probably part hit the Android Support library. So this fails with an exception. The Invaluable Price Archive for an expansive database of prices realized spanning decades of auction sales from all over our world. Development provisioning profile exists on relay system. This value form be explicitly checked. Android developer, note if not all Android flavors support badges. This will initiate the build on the Codename One build server. Because they was rich user data, profiles are wild for creating audiences to few with personalized messaging. Before switching to new app key, this method suspends the SDK and resumes it inside after. To trip off these changes, we started with the tools that our moderators and power users rely on wood make an Overflow the mint site for developers online.
    [Show full text]
  • Codename Quoi En Savez Vous Que Maintenant Démarrage 1 Sur Le Bouton Installersur Lebouton Zone La Dans Affiché Trouvé Plug-In Et Le Fois Une Cherche
    e n o h P s w o d n i W t e y r r e B k c a l B , d i o r R d e préféré. Vous écrirez une Vous préféré. à apprendrez vous chaine application mobile à succès, nous allons démarrer. Dans ce premier chapitre, Maintenant que vous savez en quoi Codename One peut vous aider à créer la pro- Démarrage 1 sur lebouton cherche. Une fois le etplug-in trouvé affiché dans la zone puis dans la zone Lancez NetBeans. Allez dans le menu utiliser leplug-in. Attention > Sous NetBeans decet qui ouvrage. aété choisilesquelles c’est pour les exemples l’environnement prioritéquice en concerne etjour pour à mises les c’est autres les sur raisons des l’une Beans, Eclipse ou IntelliJ IDEA. Pour information, le plug-in de NetBeans a souvent la différents environnements de développement, mais reste simple que vous utilisiez Net- Le téléchargement du plug-in se fait directement en ligne. L’installation diffère selon les 1.1. Téléchargementetinstallationduplug-in inclus dansleplug-induframework. ticulier des applications Codename One et le mode de fonctionnement du simulateur application Codename One n k A o o , B S - O D i s r n u o o i Vous devez avoir la version 7.x ou version supérieure de NetBeans pour pouvoir installer et p t i a d v É INSTALLER a J 5 1 n 0 e 2 installer le plug-in le installer RECHERCHER r © e p p – o pourlancerl'installation. ensuite lesinstructions. Suivez l u e f première application première de test v o .
    [Show full text]
  • The New Mobile Development Landscape
    The New Mobile Development Landscape © 2017 Progress. All Rights Reserved. All Rights © 2017 Progress. 2018 EBOOK Table of Contents Introduction / 3 Mobile Development The Early Days / 4 Mobile Development Today / 5 Native Development / 6 Browser Development Evolves / 8 Mobile Application Development Platforms (MADP) / 11 Hybrid Mobile Apps / 14 JavaScript-Driven Native Apps / 18 Other Types of Native Apps / 22 Making The Transition / 23 Testing Your Apps / 24 Building Your Mobile App Back-End / 25 © 2018 Progress. All Rights Reserved. All Rights © 2018 Progress. Conclusion / 26 Progress 2 If you poke around on the Internet, you’ll find hundreds or even thousands of frameworks and platforms designed to make platform mobile development easy. There’s almost too many of them to keep track of, and nobody knows which ones are the best, and which ones are worthless. If you’re part of a one to five-person development shop, you can afford to play around at the options to see which works best for you and your apps, potentially even switching approaches between apps. Larger development shops have to think big; the decisions they make around development approach and platform or framework selection have a long term impact on the cost and effectiveness of their development effort. Changing course months or years later means considerable expense migrating off of a flawed or abandoned platform to the shiny new approach. Development organizations must be smart, making the right choice at the app’s creation, knowing that the approach they’ve selected works for the long haul. We’ve created this ebook to help you make smart choices about how you build modern mobile apps.
    [Show full text]
  • Customer Case Study
    Customer Case Study CODENAMEONE “Codename One is developed in NetBeans IDE and has a huge portion of its users within the NetBeans community. The speed with which we have been able to develop the Codename one plugin in the IDE is a testament to the efficiency of the tools it provides.” Company: Codename One Location: Tel Aviv, Israel Executive Summary Url: http://www.Codenameone.com Codename One is an open source platform that allows Java developers to build native mobile applications that run on all mobile devices, such as iOS, iPhone/iPad, Android, RIM, and Windows Phone. Codename One is the only Industry: Cloud Based solution that allows the "write once, run anywhere" experience for Java developers, Mobile Development without the limitations of HTML5 or web based technologies. Oracle Products & Services: Codename One integrates seamlessly with the NetBeans IDE to provide a familiar NetBeans IDE development environment for Java developers. Java Organization Java EE Codename One is a rapidly growing startup, while also boasting an open source Swing developer community that is responsible for code contributions and support. LWUIT Codename One has made its way into Fortune 500 companies, as well as multiple startups and independent developer hands. The Codename One product includes a service that supports Java developers when developing native applications using native platform tools. The Business Issue • Codename One needed a single tool that could help maintain its large code base for its GUI builder, the Codename One Designer. • Codename One had a strong requirement to develop code using an IDE, while also being able to customize their build scripts extensively for release distribution.
    [Show full text]
  • Cross-Platform Mobile Development Frameworks: Choosing the Most Suitable Option for Selected Use Case
    Lappeenranta University of Technology School of Engineering Science Software Engineering Master's Programme in Software Engineering and Digital Transformation Anna Osipova CROSS-PLATFORM MOBILE DEVELOPMENT FRAMEWORKS: CHOOSING THE MOST SUITABLE OPTION FOR SELECTED USE CASE Examiners: Associate professor Jouni Ikonen Assistant professor Antti Knutas Supervisors: Assistant professor Antti Knutas Associate professor Jouni Ikonen TIIVISTELMÄ Lappeenrannan teknillinen yliopisto School of Engineering Science Tietotekniikan koulutusohjelma Master's Programme in Software Engineering and Digital Transformation Anna Osipova Alustariippumattomat mobiilikehitysohjelmistokehykset: parhaan vaihtoehdon valitseminen tiettyyn käyttötapaukseen Diplomityö 94 sivua, 18 kuvaa, 9 taulukkoa, 1 liite Työn tarkastajat: Tutkijaopettaja Jouni Ikonen Apulaisprofessori Antti Knutas Hakusanat: ohjelmistokehitys, mobiilisovellukset, mobiilikehitys, ohjelmistokehykset Keywords: software engineering, mobile applications, mobile development, software frameworks Mobiilisovellusten kehitys on haastavaa johtuen laitteiden ja alustojen pirstoutumisesta. Tämä diplomityö tutkii vaihtoehtoisia ohjelmistokehysvaihtoja tiimille, joka tuottaa B2B mobiilisovelluksia Cordova:n avulla. Tavoitteena on valita ohjelmistokehys, joka parantaisi kehitysprosessia ja tuottaisi toiminnallisempia sovelluksia nopeammin. Kehitysprosessit arvioidaan tuottamalla sama demosovellus usealla eri ohjelmistokehyksellä. Ohjelmistokehykset arvioidaan niiden keskeisten ominaisuuksien ja demosovelluksen kehityksen
    [Show full text]
  • Introduction to Mobile App Development and CN1
    CSc 133 Lecture Notes 2 – Introduction to Mobile App Development and CN1 Computer Science Department California State University, Sacramento CSC 133 Lecture Notes 2 – Programming Environment Overview • Why are we Using a Mobile App Environment? • Why did we choose Codename One (CN1)? • CN1 Features • CN1 vs Java • CN1 Installation • CN1 Hello World App • CN1 and Assignments • Assignment#0 • CN1 Online resources CSc Dept, CSUS 2 CSC 133 Lecture Notes 2 – Programming Environment Why are we Using a Mobile App Programming Environment? • Mobile computing is ubiquitous and allows: . Instant retrieval of information . Constant communication . Easy access to games, company products etc. • Hence, there is an ever growing need for mobile app developers. • Also, knowing how to program in this contemporary environment is fun and cool! CSc Dept, CSUS 3 CSC 133 Lecture Notes 2 – Programming Environment (continued...) • CSC 133 topics are widely applicable to a mobile programming environment. • Hence, using this environment in the lectures and assignments, will help to: . Enhance learning by relating CSC 133 topics to their contemporary use cases . Provide a base for further exploration of this environment (apply it to other CSC topics or create your own brilliant app!) . Build a stronger resume CSc Dept, CSUS 4 CSC 133 Lecture Notes 2 – Programming Environment Why did we choose Codename One (CN1)? • There are various popular mobile programming environments: . Platform specific: o e.g. Android, iOS SDK . Cross-platform (write one program and run it on various platforms - iOS, Android, Windows, etc.): o e.g. Codename One (CN1), PhoneGap, Appcelerator, Xamarin • We choose CN1, because it is: . Java-based .
    [Show full text]
  • With 25M Device Installs, Mobile Development Platform Codename One Announces Version 2.0
    December 25, 2013 Codename One Contact: Shai Almog FOR IMMEDIATE RELEASE [email protected] With 25m Device Installs, Mobile Development Platform Codename One Announces Version 2.0 Tel Aviv, Israel ­ Mobile development platform Codename One is announcing the release of its 2.0 version on Wednesday, December 25th. In the 7 months since the May release of 1.1 Codename One has reached profitability, quadrupled its paying subscriber base and was downloaded by 500,000 developers. Codename One is a one of a kind solution that allows Java developers to build native applications that work on all mobile devices seamlessly. It combines an open source client architecture that integrates seamlessly with all major Java development environments: Eclipse, NetBeans and IntelliJ IDEA. To leverageits one of kind cloud build system. This unique architecture enables Java developers to build iPhone applications without owning a Mac or Windows Phone applications without a Windows 8 machine. Version 2.0 is a major leap forward with containing 300 new features and improvements to the 1.1 version such as: Support for IntelliJ IDEA, Google Play Ads, binary 3rd party libraries and much more. The platform to date has been used to build over 5,000 native mobile applications and has received widespread, viral acclaim in technology and business media including InfoWorld, Slashdot, Hacker News, VentureBeat, Business Insider, The Next Web, Dr. Dobbs and Forbes. “The level of traction we are seeing is astounding, it is amazing that in less than 2 years we have amassed so many applications.” said co­founder and CEO Shai Almog.
    [Show full text]
  • A Mobile Application for Power System Analysis
    A MOBILE APPLICATION FOR POWER SYSTEM ANALYSIS A Project Presented to the faculty of the Department of Computer Science California State University, Sacramento Submitted in partial satisfaction of the requirements for the degree of MASTER OF SCIENCE in Computer Science by Sarang Satish Deshpande FALL 2016 © Fall 2016 Sarang Satish Deshpande ALL RIGHTS RESERVED ii A MOBILE APPLICATION FOR POWER SYSTEM ANALYSIS A Project by Sarang Satish Deshpande Approved by: __________________________________, Committee Chair Dr. Pinar Muyan-Ozcelik __________________________________, Second Reader Dr. Mahyar Zarghami ____________________________ Date iii Student: -Sarang Satish Deshpande I certify that this student has met the requirements for format contained in the University format manual, and that this project is suitable for shelving in the Library and credit is to be awarded for the project. __________________________, Graduate Coordinator ___________________ Dr. Ying Jin Date Department of Computer Science iv Abstract of A MOBILE APPLICATION FOR POWER SYSTEM ANALYSIS by Sarang Satish Deshpande The purpose of this project is to design an educational software that teaches the design and analysis of electric power systems using mobile platforms. To the best of our knowledge, no mobile platform exists for this purpose yet. This project examines the desktop-based application used by CSUS-EEE students (called RadiRing) for electric power systems and makes a subset of the functionalities of this application available on mobile devices. Some of the existing functionalities of RadiRing [14] app include drawing components of an electric power system such as bus, branch and shunt elements and connecting these components to each other. The app also allows user to move the connected components on screen.
    [Show full text]
  • Former Sun Microsystems Engineers Transform App Development Industry with Groundbreaking Tool
    June 04, 2012 Codename One Contact: Zach Cutler FOR IMMEDIATE RELEASE (202) 642-2740 Former Sun Microsystems Engineers Transform App Development Industry With Groundbreaking Tool Tel Aviv, Israel - Veteran software engineers Shai Almog and Chen Fishbein have launched Codename One, the first complete software development kit that allows Java developers to create native mobile applications across multiple mobile operating systems using a single code base. Codename One solves the growing inefficiency within mobile application development by enabling developers to significantly cut time and costs in developing native applications for iOS, Android, Blackberry, Windows 7 and other devices. The Java-based platform is open-source and utilizes lightweight technology, allowing it to produce unique native interfaces highly differentiated from competitive cross-platform mobile development toolkits, which typically use HTML5 or heavyweight technology. By drawing all components from scratch rather than utilizing native widgets, Codename One enables developers to avoid fragmentation – a major hindrance found in the majority of competitors – and additionally allows accurate desktop simulation of mobile apps. Codename One’s founders are internationally recognized for engineering Sun Microsystems’s famous Lightweight User Interface Toolkit, a mobile platform used by leading mobile carriers and industry leaders to this date. “Chen and I are thrilled to be releasing this transformational technology that is filling a growing demand among mobile developers,” said Almog, “The wasteful reality of having to develop the same app multiple times due to the variety of operating systems in the market is coming to a close. With Codename One, developers can write applications just once and run them everywhere.” The product has received high acclaim in the development community and is growing its user base by 50 percent each month.
    [Show full text]
  • Xavier Costa
    Xavier Costa « Write once, run anywhere » 2 Xavier COSTA [CODENAME ONE : « WRITE ONCE, RUN EVERYWHERE] Déclaration Ce travail de diplôme est réalisé dans le cadre de l’examen final de la Haute école de gestion de Genève, en vue de l’obtention du titre de Bachelor en Informatique de Gestion. L’étudiant accepte, le cas échéant, la clause de confidentialité. L'utilisation des conclusions et recommandations formulées dans le travail de diplôme, sans préjuger de leur valeur, n'engage ni la responsabilité de l'auteur, ni celle du conseiller au travail de diplôme, du juré et de la HEG. « J’atteste avoir réalisé seul le présent travail, sans avoir utilisé des sources autres que celles citées dans la bibliographie. » Fait à Genève, le 22.08.2013 Xavier COSTA Xavier COSTA [CODENAME ONE : « WRITE ONCE, RUN EVERYWHERE] 3 Remerciements Tout d'abord de grands remerciements à Monsieur Peter DAEHNE, responsable de mon travail de Bachelor, pour son aide précieuse et pour le temps qu’il m’a consacré lorsque j’en ai eu besoin. Je voudrais aussi remercier tous les professeurs de la Haute Ecole de Gestion que j’ai pu rencontrer tout au long de cette formation, qui ont partagé leurs connaissances et expériences professionnelles lors de leurs cours. 4 Xavier COSTA [CODENAME ONE : « WRITE ONCE, RUN EVERYWHERE] Résumé Codename One est un plug-in pour NetBeans et Eclipse sorti récemment. Il permet de développer en Java, avec un seul et même code, des applications multiplateformes. Nous avons tout d’abord étudié le produit, afin de comprendre comment il fonctionne et de déterminer les inconvénients/avantages qu’il présente.
    [Show full text]