DOCSLIB.ORG

Building Blocks: Utilizing Component-Based Software Engineering in Developing Cross-Platform Mobile Applications

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Building Blocks: Utilizing Component-Based Software Engineering in Developing Cross-Platform Mobile Applications KTH Computer Science and Communication Building Blocks: Utilizing Component-Based Software Engineering in Developing Cross-Platform Mobile Applications Master of Science Thesis Interactive Media Technology at KTH Royal Institute of Technology By Oskar Andersson ([email protected]) Supervisor at KTH: Vasiliki Tsaknaki Supervisors at Ericsson Research: Michal Koziuk & Johan Sjöberg Acknowledgements I would like to thank Stefan Ålund and Ericsson Research for the opportunity to work with this thesis. In particular, I have to thank my supervisors, Michal Koziuk & Johan Sjöberg, for their help and support during my time there. I would also like to thank my supervisor at KTH, Vasiliki Tsaknaki, for her constructive criticism and valuable feedback. Thank you! Oskar Andersson October 3 2014, Stockholm 2 Abstract Contemporary approaches to cross-platform mobile application development, such as hybrid apps from PhoneGap and generated native apps from Xamarin, show promise in reducing development time towards Android, iOS and other platforms. At the same time, studies show that there are various problems associated with these approaches, including suffering user experiences and codebases that are difficult to maintain and test properly. In this thesis, a novel prototype framework called Building Blocks was developed with the purpose of investigating the feasibility of utilizing component-based software engineering in solving this problem. The prototype was developed towards Android along with a web interface that allowed users to assemble an Android app using software components. The report concludes that component-based software engineering can be – and already is – utilized successfully to improve cross-platform mobile app development with special regards to user experience. Qualitative data indicate that Building Blocks as a concept is flexible and shows promise for mobile app development in which functionality is often reused, such as enterprise apps. Rapid prototyping using the web-based visual editing tool was another promising area. However, future use of Building Blocks would require further work on the prototype to improve its ease of use. 3 Table of contents LIST OF FIGURES ......................................................................................................................... 5 DEFINITIONS ............................................................................................................................... 6 1. INTRODUCTION ....................................................................................................................... 7 1.1 Problem background ....................................................................................................... 7 1.2 Purpose ........................................................................................................................... 8 1.3 Delimitations ................................................................................................................... 9 1.4 Problem definition ........................................................................................................... 9 2. BACKGROUND ....................................................................................................................... 10 2.1 Web apps ...................................................................................................................... 10 2.2 Hybrid apps ................................................................................................................... 12 2.3 Cross-platform mobile app development ...................................................................... 13 2.4 Component-based software engineering ...................................................................... 14 3. METHODOLOGY .................................................................................................................... 17 3.1 Literature study ............................................................................................................. 17 3.2 State of the art analysis ................................................................................................ 17 3.3 Prototype framework ..................................................................................................... 17 3.4 Qualitative evaluation of the prototype .......................................................................... 18 4. STATE OF THE ART ANALYSIS ................................................................................................. 19 4.1 Enterprise products ....................................................................................................... 19 4.2 Research projects ......................................................................................................... 21 5. PROPOSED FRAMEWORK: BUILDING BLOCKS ......................................................................... 24 5.1 Guidelines ..................................................................................................................... 24 5.2 Proposed framework architecture ................................................................................. 24 5.3 Prototype architecture ................................................................................................... 25 6. RESULTS .............................................................................................................................. 33 6.1 Building Blocks .............................................................................................................. 33 6.2 Qualitative study ........................................................................................................... 34 7. RESULT ANALYSIS ................................................................................................................. 38 7.1 Method discussion ........................................................................................................ 38 7.2 Result discussion .......................................................................................................... 38 7.3 Differences to existing approaches ............................................................................... 40 8. CONCLUSION ........................................................................................................................ 41 8.1 Answer to the research question .................................................................................. 41 8.2 Future research ............................................................................................................. 41 REFERENCES ........................................................................................................................... 42 APPENDIX ................................................................................................................................. 46 Interview questions ............................................................................................................. 46 4 List of figures FIGURE 1. A JAVASCRIPT EXAMPLE FOR ACCESSING A NATIVE ACCELEROMETER IN A HYBRID APP (APACHE CORDOVA API DOCUMENTATION, N.D.). .................................................................................... 12 FIGURE 2. SHOWCASES WHAT TECHNOLOGIES COULD BE USED WHERE IN A HYBRID APP (TRAEG, 2013). ...... 13 FIGURE 3. A WEB COMPONENT SEARCH ENGINE (POLYMER, 2014). ........................................................... 15 FIGURE 4. A SCREENSHOT FROM THE COMPONENT EXPLORER OF THE 2008 CBSE AND VISUAL COMPONENT COMPOSITION STUDY (WULF, PIPEK AND WUN, 2008). ............................................................... 15 FIGURE 5. CROSS-PLATFORM APP DEVELOPMENT PRODUCTS. .................................................................... 21 FIGURE 6. CROSS-PLATFORM APP DEVELOPMENT RESEARCH PROJECTS. .................................................... 23 FIGURE 7. A THEORETICAL OVERVIEW OF BUILDING BLOCKS WITH TWO PLATFORMS. ................................... 24 FIGURE 8. A SIMPLIFIED OVERVIEW OF THE BUILDING BLOCKS ARCHITECTURE. ............................................ 25 FIGURE 9. INITIAL VIEW WHERE ONE CAN SEARCH FOR AND ADD BLOCKS TO THE APP. .................................. 27 FIGURE 10. SECOND VIEW. HERE ONE CAN CUSTOMIZE THE EVENTS AND METHODS OF EACH BLOCK. .............. 27 FIGURE 11. AVAILABLE EVENT WITH NO REGISTERED METHOD. ..................................................................... 28 FIGURE 12. EVENT WITH A METHOD CALLED “STARTNEWCOMPONENTSCREEN” REGISTERED TO IT. ................ 28 FIGURE 13. A METHOD CALLED “GETFRIENDNAME” WITH A STRING PARAMETER “USERID”. “FISKBOKLOGIN” IS THE BLOCK FROM WHICH THIS METHOD ORIGINATES. .................................................................. 28 FIGURE 14. THIRD AND LAST VIEW. THE SOURCE CODE (JSON) OF THE APP COMPOSITION IS SHOWN. ............ 29 FIGURE 15. A SIMPLIFIED OVERVIEW OF THE BUILDING BLOCKS ANDROID RUNTIME. ...................................... 30 FIGURE 16. A CLASS DIAGRAM OF THE FISKBOK LOGIN BLOCK. FISKBOKLOGINMODEL IS THE BASE MODEL CLASS WITH PUBLIC METHODS. THE FISKBOKMODEL OBJECT REFERENCE IS RETRIEVED FROM THE (NOT SEEN HERE) BINDER CLASS. ..................................................................................................... 31 5 Definitions Throughout this thesis a number of technical key terms will be used. Here are the definitions that will be used throughout the report. Cross-platform mobile Development of software that aims to target development several
Load more

Recommended publications
  • Amazon Silk Developer Guide Amazon Silk Developer Guide
    Amazon Silk Developer Guide Amazon Silk Developer Guide Amazon Silk: Developer Guide Copyright © 2015 Amazon Web Services, Inc. and/or its affiliates. All rights reserved. The following are trademarks of Amazon Web Services, Inc.: Amazon, Amazon Web Services Design, AWS, Amazon CloudFront, AWS CloudTrail, AWS CodeDeploy, Amazon Cognito, Amazon DevPay, DynamoDB, ElastiCache, Amazon EC2, Amazon Elastic Compute Cloud, Amazon Glacier, Amazon Kinesis, Kindle, Kindle Fire, AWS Marketplace Design, Mechanical Turk, Amazon Redshift, Amazon Route 53, Amazon S3, Amazon VPC, and Amazon WorkDocs. In addition, Amazon.com graphics, logos, page headers, button icons, scripts, and service names are trademarks, or trade dress of Amazon in the U.S. and/or other countries. Amazon©s trademarks and trade dress may not be used in connection with any product or service that is not Amazon©s, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. AWS documentation posted on the Alpha server is for internal testing and review purposes only. It is not intended for external customers. Amazon Silk Developer Guide Table of Contents What Is Amazon Silk? .................................................................................................................... 1 Split Browser Architecture ......................................................................................................
    [Show full text]
  • Tests of Graphics Rendering in Browsers
    3 Tests of Graphics Rendering in Browsers JAAK HENNO Tallinn University of Technology HANNU JAAKKOLA, Tampere University of Technology, Pori Department JUKKA MÄKELÄ, University of Lapland, Rovaniemi, Finland Web browsers have become one of the most commonly used software and are important communication tool to access our data- driven, increasingly visual Internet. Browser graphics speed is essential for many commercial web applications – e-commerce sites, web portals, content management systems (CMS’s), therefore web developers should well understand their possibilities. Browsers can be seen as multi-input (HTML-text, images, CSS, Scripts) multi-output (code for processor, graphics card, sound system) translators, but little is known about their 'internal life', especially how they render graphics. Browsers interpreting HTML5 documents have two graphic modes: Retained Mode (images defined in HTML text and animated with CSS) and Immediate Mode (images created on canvas and animated with JavaScript). In order to understand differences of these modes in animation rendering speed were created nine different versions of an animation of Lunar Eclipse which were tested in six major PC and Android mobile phone browsers. Results indicate, that there are no significant differences in major browsers except that IE and Edge (still) lag behind in implementing novel graphics/video formats and that in all tested browsers Retained Mode is at least two times quicker than Immediate Mode. Categories and Subject Descriptors: I.3.6 [Computer graphics]: Methodology and Techniques; I.3.4 [Computer graphics] Graphics Utilities General Terms: Browser, Visualization, Layout Engine, Rendering Engine, Retained mode, Immediate Mode Additional Key Words and Phrases: HTML5, CSS3, JavaScript, SVG, rendering 1 INTRODUCTION The first program what (usually) everyone opens when starting a computer, tablet or internet-enabled phone is a browser.
    [Show full text]
  • Readme OSS Weather Extension Module for Desigocc
    Smart Infrastructure Note to Resellers: Please pass on this document to your customer to avoid license infringements. Third-Party Software Information for Weather Extension Module for Desigo CC, 5.0 This product, solution or service ("Product") contains third-party software components listed in this document. These components are Open Source Software licensed under a license approved by the Open Source Initiative (www.opensource.org) or similar licenses as determined by SIEMENS ("OSS") and/or commercial or freeware software components. With respect to the OSS components, the applicable OSS license conditions prevail over any other terms and conditions covering the Product. The OSS portions of this Product are provided royalty-free and can be used at no charge. If SIEMENS has combined or linked certain components of the Product with/to OSS components licensed under the GNU LGPL version 2 or later as per the definition of the applicable license, and if use of the corresponding object file is not unrestricted ("LGPL Licensed Module", whereas the LGPL Licensed Module and the components that the LGPL Licensed Module is combined with or linked to is the "Combined Product"), the following additional rights apply, if the relevant LGPL license criteria are met: (i) you are entitled to modify the Combined Product for your own use, including but not limited to the right to modify the Combined Product to relink modified versions of the LGPL Licensed Module, and (ii) you may reverse-engineer the Combined Product, but only to debug your modifications. The modification right does not include the right to distribute such modifications and you shall maintain in confidence any information resulting from such reverse-engineering of a Combined Product.
    [Show full text]
  • Angular Vs React.Js Vs Vue.Js
    EVERYTHING YOU NEED TO KNOW TO MAKE AN EDUCATED DECISION ABOUT YOUR TECHNOLOGY STACK ANGULAR VS REACT.JS VS VUE.JS + Our evaluation of UI Frameworks, Tools & Technologies 2019 3 What’s inside? 1 Preface 3 2 Angular, ReactJS & Vue JS - Comparison 4 3 Angular, ReactJS & Vue JS - Pros & Cons 6 4 Angular, ReactJS & Vue JS - Conclusion 11 5 UI Technoverse 13 a.Frameworks 15 b.Technologies 19 c.Tools 22 2 Are you a front-end superstar, excited to build feature-rich beautiful UI? Join Us 3 STATE OF FRONTEND TECHSTACKS 2019 PREFACE Preface he only constant in the web frontend development landscape is that it is in constant flux year after year. So, it becomes paramount to reevaluate the tools, frameworks, Tlibraries and practices after every few quarters. As of this writing most of the web frontend development happens in either Angular, ReactJS or VueJS. Compared to our previous evaluation in 2018 which only had Angular and ReactJS as major players, now, we also have VueJS with significant traction. As always a direct comparison between Angular, ReactJS and VueJS alone will not be sufficient. So, it will not be an individual comparison but a comparison of their respective ecosystems on the whole. 3 Are you a front-end superstar, excited to build feature-rich beautiful UI? Join Us Angular, React.JS & Vue.JS - Comparison In this section, we compare all three frameworks using a plethora of parameters to highlight how they fare against 2each other. STATE OF FRONTEND TECHSTACKS 2019 COMPARISON Angular ReactJS VueJS Type JavaScript Framework JavaScript Library JavaScript Library Web development and Web development and Web development and Hybrid mobile app Native mobile app Hybrid mobile app Used for development (Ionic) development (React development Native) (Onsen UI) Maintained by Google & Community Facebook & Community Community TypeScript Javascript (Also Javascript (Also Coded in supports Typescript) supports Typescript) Steep learning curve Easier Easiest among the three Ease of Learning since it is an end to end framework.
    [Show full text]
  • Controlpoint 5.6.1 Open Source and Third-Party Software License
    ControlPoint Software Version 5.6.1 Open Source and Third-Party Software License Agreements Document Release Date: December 2018 Software Release Date: December 2018 Open Source and Third-Party Software License Agreements Legal notices Copyright notice © Copyright 2015-2018 Micro Focus or one of its affiliates. The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Documentation updates The title page of this document contains the following identifying information: l Software Version number, which indicates the software version. l Document Release Date, which changes each time the document is updated. l Software Release Date, which indicates the release date of this version of the software. You can check for more recent versions of a document through the MySupport portal. Many areas of the portal, including the one for documentation, require you to sign in with a Software Passport. If you need a Passport, you can create one when prompted to sign in. Additionally, if you subscribe to the appropriate product support service, you will receive new or updated editions of documentation. Contact your Micro Focus sales representative for details. Support Visit the MySupport portal to access contact information and details about the products, services, and support that Micro Focus offers. This portal also provides customer self-solve capabilities.
    [Show full text]
  • Webgl: 3D Application Development
    WebGL: 3D application development This chapter covers ■ Developing a WebGL engine ■ Communicating with a graphics card ■ Creating 3D shapes Web developers have been trying for years to overcome 3D limitations to create bet- ter interactive games, education tools, and infographics. In the past, plug-ins such as Unity, Flash, and Quicksilver created Google Maps and online 3D explorations programs. Plug-ins can be useful, but they leave you at the browser vendor’s mercy for updates, usually lack hardware acceleration, and are often proprietary. To solve these issues, the Khronos Group created a Web Graphics Library (WebGL). WebGL, as mentioned in chapter 1, gives you the ability to create awesome 3D applications like X-Wing, shown in figure 9.1, without plug-ins. Several developers have even used WebGL to make drawing interfaces that create 2D images and rotate those creations in 3D. WARNING! You should be very familiar with Canvas and JavaScript object- oriented programming (OOP) before working through this chapter’s sam- ple application. If you aren’t, please go through chapter 6 on 2D Canvas first, because the concepts we cover here build on chapter 6’s application, mainly because WebGL builds on top of the Canvas API. 267 268 CHAPTER 9 WebGL: 3D application development Figure 9.1 A simple WebGL application called X-Wing created by OutsideOfSociety. He worked on the popular WebGL project http://ro.me. You could learn basic 3D programming elsewhere, but we’ve provided it all for you— all in one place—along with thorough explanations of 3D programming concepts, mathematics, diagrams, and more.
    [Show full text]
  • Phonegap-Beginners-Guide.Pdf
    PhoneGap Beginner's Guide Build cross-platform mobile applications with the PhoneGap open source development framework Andrew Lunny BIRMINGHAM - MUMBAI PhoneGap Beginner's Guide Copyright © 2011 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: September 2011 Production Reference: 1160911 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-849515-36-8 www.packtpub.com Cover Image by Asher Wishkerman ([email protected]) Credits Author Project Coordinator Andrew Lunny Joel Goveya Reviewers Proofreader Paul McCrodden Aaron Nash Andrey Rebrov Indexer Acquisition Editor Hemangini Bari Usha Iyer Production Coordinator Development Editor Aparna Bhagat Meeta Rajani Cover Work Technical Editors Aparna Bhagat Pallavi Kachare Priyanka Shah About the Author Andrew Lunny is a software developer based in Vancouver, BC, where he is "Chief N00b" at Nitobi Software.
    [Show full text]
  • Sqamia2017 Henno Jaakkola
    1 Tests of Graphic Rendering in Browsers JAAK HENNO Tallinn University of Technology HANNU JAAKKOLA, Tampere University of Technology, Pori Department JUKKA MÄKELÄ, University of Lapland, Rovaniemi, Finland Web browsers have become one of most commonly used software, important communication tool to access our data-driven, increasingly visual Internet-based ecosystem. Browsers can be seen as multi-input (html-text, images, CSS, Scripts) multi- output (code for processor, graphics card, sound system) translators, but little is known about their 'internal life', especially how they produce graphics '. For creating visual images browsers use two modes: Retained Mode and Immediate Mode. In order to understand differences in these modes, especially in differences in speed, we created nine different versions for animation of Lunar Eclipse on 20.03.2015 and tested them in six major PC and Android mobile phone browsers. Results indicate, that there are no significant differences in major browsers except that IE and Edge (still) lag behind in implementing novel graphics/video formats and that Retained Mode (images inserted in html text or animated with CSS3) is at least twice quicker than Immediate Mode (Javascript animation on Canvas) in all tested browsers. Categories and Subject Descriptors: • Information systems~Browsers • Computing methodologies~Computer graphics • Computing methodologies~Graphics file formats General Terms: Browser, Visualization, Browser's Layout Engine, Browser's Rendering Engine, Retained mode, Immediate Mode Additional Key Words and Phrases: HTML5, CSS3, JavaScript 1 INTRODUCTION The first program what (nearly) everyone open when sitting behind a computer, starting a tablet or internet-enabled phone is browser. Browsers have become the most common communication/interaction tool for all Internet-connected Mankind - more than half of whole Mankind.
    [Show full text]
  • How to Enable Javascript in Your Browser and Why
    How to enable JavaScript in your browser and why EN HR DE NL ES PT IT NO RU FR CZ JA KO HU TH PH TR ID SK PL How to enable JavaScript in your browser Nowadays almost all web pages contain JavaScript, a scripting programming language that runs on visitor's web browser. It makes web pages functional for specific purposes and if disabled for some reason, the content or the functionality of the web page can be limited or unavailable. Here you can find instructions on how to enable (activate) JavaScript in five most commonly used browsers. Internet Explorer Mozilla Firefox Google Chrome Opera Apple Safari Javascript is enabled in your web browser. If you disable JavaScript, this text will change. Instructions for web developers You may want to consider linking to this site, to educate any script-disabled users on how to enable JavaScript in five most commonly used browsers. You are free to use the code below and modify it according to your needs. <noscript> For full functionality of this site it is necessary to enable JavaScript. Here are the <a href="http://www.enable-javascript.com/" target="_blank"> instructions how to enable JavaScript in your web browser</a>. http://enable-javascript.com/[3/11/2015 11:29:50 AM] How to enable JavaScript in your browser and why </noscript> On enable-javascript.com we optimize the script-disabled user experience as much as we can: The instructions for your browser are put at the top of the page All the images are inlined, full-size, for easy perusing This developer-centric message is out of the way.
    [Show full text]
  • Fruit of the Accessibility Tree Presentation Slides (PDF)
    The Fruit of the Accessibility Tree 1 1. A little background 2. The browser path Agenda 3. The creation of the tree 4. Looking at the accessibility tree 5. Bring it on home 2 Why should we care about this junk “A firm grasp of the technology is paramount to making informed decisions about accessible design.” - Léonie Watson “As a web developer, learning the internals of browser operations helps you make better decisions and know the justifications behind development best practices.” - Paul Irish, Chrome Developer Relations 3 A little background 4 When everything was text • Personal computers originally relied on text based operating systems (e.g. DOS aka Disk Operating System). • Assistive technology could access the text directly from the screen. Image by Mega super editorman / CC BY (https://creativecommons.org/licenses/by/4.0) 5 Then came Graphic User Interfaces (GUI) • Graphical Interfaces for operating systems become popular (e.g. Windows, Apple Macintosh) “draw” information on the screen. • Assistive technology had to rely on heuristics to understand what was being presented to users. • Accessibility Application Programming Interfaces (APIs) were introduced to operating systems to more reliably and accurately pass information to assistive technologies. • As new browsers were introduced in the mid 2000’s they began integrating with the Accessibility APIs of different operating systems. 6 The Accessibility APIs Windows: Apple: Linux: • Microsoft Active • NSAccessibility (AXAPI) • Accessibility Toolkit (ATK) Accessibility (MSAA) • Assistive Technology Service • IAccessible2 (IA2) Provider Interface (ATK-SPI) • UI Automation (UIA) 7 Different paths: the browser 8 Browser breakdown • Browser requests HTML/CSS/JavaScript resources • Browser’s render engine parses the HTML/CSS/JavaScript and creates the Document Object Model (DOM) from the HTML and CSS Object Model (CSSOM) from the CSS.
    [Show full text]
  • DEVELOPMENT of HYBRID MOBILE APPS Using Ionic Framework
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Theseus Andrea Sánchez Blanco DEVELOPMENT OF HYBRID MOBILE APPS Using Ionic framework Bachelor’s Thesis Information technology May 2016 DESCRIPTION Date of the bachelor's thesis 23.05.2016 Author(s) Degree programme and option Andrea Sánchez Blanco Information Technology Name of the bachelor's thesis DEVELOPMENT OF HYBRID MOBILE APPS Using Ionic Framework Abstract The purpose of the current study is to analyse the advantages and disadvantages of web-based hybrid apps. This thesis explains from the beginnings of mobile phones how and why it has been created this solution, and how mobile’s history has evolved to need an intermediate approach. It is also studied the general principles of good mobile user interfaces, in order to create a full good user experience from appearance to performance and usability, and how to implement the server side in an Ionic mo- bile application. These have been done providing a general context about the first mobile phones to the latest ones, going through the different mobile OSs and focusing on an intermediate approach, hybrid web-based apps. After that I have explained Ionic Framework and the User Interface guidelines. Finally I have documented my practical part, associating it with the theoretical part, and explaining how I did the server side implementation on my app. The conclusions I took are more general than I thought at the beginning. I have studied this solution with Ionic Framework, with which I have had an overall good experience.
    [Show full text]
  • Evaluation of Cross-Platform Tools for Mobile Development Bachelor of Science Thesis in Software Engineering and Management
    Evaluation of Cross-Platform Tools for Mobile Development Bachelor of Science Thesis in Software Engineering and Management ALIREZA PAZIRANDEH EVELINA VOROBYEVA University of Gothenburg Chalmers University of Technology Department of Computer Science and Engineering Göteborg, Sweden, June 2013 The Author grants to Chalmers University of Technology and University of Gothenburg the non-exclusive right to publish the Work electronically and in a non-commercial purpose make it accessible on the Internet. The Author warrants that he/she is the author to the Work, and warrants that the Work does not contain text, pictures or other material that violates copyright law. The Author shall, when transferring the rights of the Work to a third party (for example a publisher or a company), acknowledge the third party about this agreement. If the Author has signed a copyright agreement with a third party regarding the Work, the Author warrants hereby that he/she has obtained any necessary permission from this third party to let Chalmers University of Technology and University of Gothenburg store the Work electronically and make it accessible on the Internet. Evaluation of Cross-Platform Tools for Mobile Development Alireza Pazirandeh Evelina Vorobyeva © Alireza Pazirandeh, June 2013. © Evelina Vorobyeva, June 2013. Examiner: Morgan Ericsson University of Gothenburg Chalmers University of Technology Department of Computer Science and Engineering SE-412 96 Göteborg Sweden Telephone + 46 (0)31-772 1000 Department of Computer Science and Engineering Göteborg,
    [Show full text]