DOCSLIB.ORG

Rhomobile Suite 4.0 RCR

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Rhomobile Suite 4.0 RCR RhoMobile Suite 4.0 RCR Revision History Authors Date RMS_4.0.0.beta1 Geoff, Evgeny, Lars, Darryn 23rd Jan 2013 RMS_4.0.0.beta2 Geoff, Evgeny, Lars, Darryn 25th Jan 2013 RMS_4.0.0.beta3 Geoff, Evgeny, Lars, Darryn 6th Feb 2013 RMS_4.0.0.beta4 Geoff, Evgeny, Lars, Darryn 20th Feb 2013 RMS_4.0.0.beta5 Geoff, Evgeny, Lars, Darryn 8th March 2013 RMS_4.0.0.beta6 Geoff, Evgeny, Lars, Darryn, 22nd March 2013 Paul Henderson RMS_4.0.0.beta7 Geoff, Evgeny, Lars, Darryn, 26nd March 2013 Paul Henderson RMS_4.0.0.beta8 Geoff, Evgeny, Lars, Darryn, 5 April 2013 Paul Henderson RMS_4.0.0.beta9 Geoff, Evgeny, Lars, Darryn, 5 April 2013 Paul Henderson RMS_4.0.0.beta10 Geoff, Evgeny, Lars, Darryn, 19 April 2013 Paul Henderson 1 | Page RMS_4.0.0.beta11 Geoff, Evgeny, Lars, Darryn, 22 April 2013 Paul Henderson RMS_4.0.0.beta12 Geoff, Evgeny, Lars, Darryn, Not given to T&V Paul Henderson RMS_4.0.0.beta13 Geoff, Evgeny, Lars, Darryn, 3 May 2013 Paul Henderson RMS_4.0.0.beta14 Geoff, Evgeny, Lars, Darryn, Paul Henderson RMS_4.0.0.beta21 Geoff, Evgeny, Lars, Darryn, 5 June 2013 Paul Henderson RMS_4.0.0.beta28 Geoff, Evgeny, Lars, Darryn, 18 June 2013 Paul Henderson RMS_4.0.0.beta31 Geoff, Evgeny, Lars, Darryn, 26 June 2013 Paul Henderson RMS_4.0.0.beta35 Geoff, Evgeny, Lars, Darryn, 5 July 2013 Paul Henderson RMS_4.0.0.beta39 Geoff, Evgeny, Lars, Darryn, 12 July 2013 Paul Henderson RMS_4.0.0.beta43 Geoff, Evgeny, Lars, Darryn, 19 July 2013 Paul Henderson 2 | Page 3 | Page Contents Overall Notes Build Schedule RMS 4.0 PRD Requirements Trace Log Stories completed from SPB Stories complete from UK RhoConnect RhoConnect Push Server RhoConnect Java Bindings RhoStudio Moto - WebKit SPRs CQCM EMBPD SR Updates (Performed) SR Updates (Rejected) Output from Continuous Integration Known Issues 4 | Page Overall Notes RhoMobile Suite 4.0 is the first major release of RhoMobile Suite since its launch and is the first to properly amalgamate all device capabilities and align properly with RhoConnect. Build Schedule Build # Version One Mapping 1 RMS_4.0.0.beta1.exe Internal developer build RMS_4.0.0.beta1.dmg 2 RMS_4.0.0.beta2.exe Sprint 58, Sprint 13 RMS_4.0.0.beta2.dmg 3 4.0.0.beta.3 Sprint 59, Sprint 14 4 4.0.0.beta.4 Sprint 60, Sprint 15 5 4.0.0.beta.5 Sprint 61, Sprint 16 6 4.0.0.beta.6 Sprint 62, Sprint 17 7 4.0.0.beta.8 Sprint 63, Sprint 18 8 4.0.0.beta.10 Sprint 64, Sprint 19 9 4.0.0.beta.11 Sprint 64, Sprint 19 10 4.0.0.beta.12 Not given to T&V 11 4.0.0.beta.13 Sprint 65, Sprint 20 12 4.0.0.beta.14 Sprint 66 5 | Page 13 4.0.0.beta.21 Sprint 68 14 4.0.0.beta.28 Sprint 69 15 4.0.0.beta.31 Sprint 69 16 4.0.0.beta.35 Sprint 70 17 4.0.0.beta.39 Sprint 71 18 4.0.0.beta.43 Sprint 71 6 | Page RMS 4.0 PRD Requirements Trace Log Please see Version One for this information, stories are allocated to sprints. For a mapping of deliverable build number to sprint number see the previous table. Requirement Requirement Description T&V Testable in Build ID Validation Version Requried 7 | Page 8 | Page Stories completed for Rhodes This section lists the features, bugs and documentation updates for Rhodes. Build# Change Log 4.0.0.beta1 Internal developer build Gem: rhodes-4.0.0.bet a1.gem 4.0.0.beta2 ● Gem: rhodes-4.0.0.bet a2.gem 4.0.0.beta3 ● E-07284 provide build.yml flag to control hardware acceleration - SPR23230 Gem: ● E-07045 RhoConnect Client as native extension rhodes-4.0.0.bet ● E-07193 separate views for Windows Mobile in scaffolding a3.gem ● 4.0.0.beta4 ● B-98748 - Rho.System: Implement WM / CE Common API Set 9 | Page ● B-100158 Android: support stock browser and rhoelements Gem: extension on ET1. So Barcode and Scanner should work with rhodes-4.0.0.bet Stock browser a4.gem ● B-97290 Rho.System : Implement Windows Phone 8 APIs ● B-97815 WP8: Support HTTPS 4.0.0.beta5 ● E-07201 - support build for Windows XP Embedded ● E-07524 "native browser" option for Windows Mobile and Gem: WinCE rhodes-4.0.0.bet ● B-98845 Rho::System for iOS a5.gem ● B-98797 Rho::System for Android 4.0.0.beta6 ● Network module(AsyncHttp part) for All platforms ● Database module for all platforms Gem: ● RhoConnectClient module for all platforms(except WP8) rhodes-4.0.0.bet ● WebView module for Windows and iOS a6.gem 4.0.0.beta8 ● JS API support callbacks for all platforms ● WebView module for Android Gem: ● Barcode for iOS rhodes-4.0.0.bet ● Camera for iOS a8.gem ● Log for all platforms ● E-07761 support for SSL with self-signed certificates to 10 | Page Rhoconnect client - SPR 23631 4.0.0.beta9 ● Fix build issue with Windows Mobile: CQ EMBPD00094904 Gem: rhodes-4.0.0.bet a9.gem 4.0.0.beta10 ● Signature Capture for iOS with Common API ● RhoConnect client for WP8 with Common API Gem: rhodes-4.0.0.bet a10.gem 4.0.0.beta13 ● Signature Capture for Android with Common API Gem: rhodes-4.0.0.bet a13.gem 4.0.0.beta21 ● Database Common API Gem: rhodes-4.0.0.bet a21.gem 4.0.0.beta28 ● WebView Common API ● Application Gem: 11 | Page rhodes-4.0.0.bet ● Log a28.gem ● Network ● System ● NavBar ● Barcode for iOS 4.0.0.beta31 ● NativeMenuBar Common API ● Notification for iOS, Android, WM/CE, Win32 Gem: ● NativeTabbar rhodes-4.0.0.bet ● NativeToolbar a31.gem ● File for iOS, Android, WM/CE, Win32 4.0.0.beta35 ● File for WP8 ● ScreenOrientation Gem: ● System (RhoGallery) rhodes-4.0.0.bet ● Rho ORM a35.gem ● RhoConnectClient for iOS, Android, Win32 ● iOS7 ● Javascript Application ● Persistent CAB installation on WM/CE ● JQM 1.3.1 migration ● Shared Runtime with Common API for WM/CE ● rhodes-4.0.0.bet ● RhoConnectClient for WM/CE a39.gem ● iOS7 Beta 3 support iOS Simulators 12 | Page ● Javascript Application with Shared Runtime and Windows RhoSim ● MediaPlayer ● Sensor for iOS, WM/CE rhodes-4.0.0.bet ● Push for iOS, Android a43.gem ● RhoConnect Push for WM/CE (RPS), Android Stories complete for RhoElements This section lists the features, bugs and documentation updates for RhoElements. Build# Change Log 4.0.0.beta.1 Internal developer build. Gem: 4.0.0.beta.1 4.0.0.beta.2 ● The new WebKit has implemented B-0360 which allows us to Gem: 4.0.0.beta.2 specify the AcceptLanguage HTTP Header returned by the browser. You configure this in the config file via Navigation\\AcceptLanguage. The string you give is returned by the browser in the AcceptLanguage header, eg. en-GB,en-US;q=0.8,en;q=0.6,af;q=0.4. For more information see the 13 | Page W3C spec at http://www.w3.org/International/questions/qa-accept-lang-locale s ● B-94286. T&V can now commence on the MK31xx product line. Engineering testing has been carried out on an MV unit. ● B-94367. T&V can now commence on the MC45 product line. Engineering testing has been carried out on MV units. ● B-94373. T&V can now commence on the VC70 product line. Engineering testing has been carried out on MV units. Note, we have also implemented the Sensor API & 3D gesturing on MPA3 platforms (ie where there are physical sensors on the device). This was done to properly support MPA3 devices. 4.0.0.beta.3 ● B-94366. Engineering verification of the MC67 is complete and it Gem: 4.0.0.beta.3 can be validated by T&V ● B-94368. Engineering verification of the MC40 is complete and it can be validated by T&V ● B-97429. Engineering verification of the WT41N0 is complete and it can be validated by T&V ● B-97785. CORS has been implemented in RE1 push API ● B-94401. Component versions have been removed to support move to semantic versioning. ● Note: The changes made to the product for Walgreens have not yet been merged back into the product 14 | Page 4.0.0.beta4 ● B-94369. Engineering verification of the SB1 is complete and it can be validated by T&V. Please reach out to Steve Sutton in Gem: the first instance if there are any questions on SB1, even rhoelements-4.0. though Ben Kennedy is listed as the owner. Scope of T&V 0.beta4.gem validation is ‘outside the shell’, i.e. the SB1 shell is outside the scope of T&V and validation should not be performed on it. Run RE on the SB1 in the same way you would run it on any other device. ● B-98968. Walgreens fixes have been merged into the main branch. Please be aware that the cardReader interface is obviously being slightly reworked for the common API effort but if you want to test these new additions in RhoElements 1 format then the help file is at: http://compass.mot-solutions.com/cgi/fetch/379029436/44 2600925/cardreader.html (only the read event has changed) ● B-98719. Barcode API from common API set. The up to date help for this is not available on edgedocs however I have put the latest help doc here: http://compass.mot-solutions.com/doc/442583473/Rhomo bile___Barcode.pdf.
Load more

Recommended publications
  • Rhomobile Solution
    Rhomobile Solution Mobile and Desktop cross-platform development with Ruby Intro You like Ruby and Ruby on Rails ? You want to develop mobile cross-platform application based on Ruby ? Let me introduce Rhodes solution ! RUBY + RHODes Ruby on mobile devices Mobile Ruby solutions on market Native, like https://github.com/mobiruby Xamarin, Appcelerator limited functionality MobiRuby Native app like http://ruboto.org/ Xamarin, Appcelerator limited functionality Cross-platform. Native, like http://www.rubymotion.com/ Xamarin, Appcelerator. Development only on Mac OS RubyMotion Working solution Cross-platform hybrid, like PhoneGap (Cordova), http://tau-technologies.com/ but with Ruby controllers on the local server. Linux, Sailfish Complete solution Mobile cross-platform solutions Mobile applications architectures SImple not cross-platform Web Native Hybrid Mixed Hybrid Native Application cross-platform Application cross-platform Application cross-platform Application cross-platform Application Platform Browser UI Framework WebView Framework WebView platform dependent or UI HTML/CSS/JS code cross-platform UI + Logic code HTML/CSS/JS UI + Logic code Native code UI + Logic HTML/CSS/JS Logic Logic code cross-platform code cross-platform code Framework Framework Framework Platform API Platform API Platform API Platform API iOS: ObjC, Swift, C++ a lot of Xamarin (C#) Cordova/PhoneGap RhoMobile Android: Java, C++ HTML/CSS/JS frameworks Appcelerator (JS) (in pure hybrid mode) RhoMobile (Ruby) WinCE/WM: C#, C++ React Native (JS) + a lot of + a lot of
    [Show full text]
  • Cross-Platform Development of Smartphone Application with Rhomobile
    Masaryk University Faculty of Informatics Cross-platform development of smartphone application with RhoMobile Master’s Thesis Bc. Adam Melkus Brno, Spring 2016 Masaryk University Faculty of Informatics Cross-platform development of smartphone application with RhoMobile Master’s Thesis Bc. Adam Melkus Brno, Spring 2016 Declaration Hereby I declare that this paper is my original authorial work, which I have worked out on my own. All sources, references, and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Bc. Adam Melkus Advisor: Ing. Mgr. et Mgr. Zdeněk Říha, Ph.D. i Acknowledgement I would like to thank my supervisor Ing. Mgr. et Mgr. Zdeněk Říha, Ph.D. for enabling me to write this thesis and being patient with my erratic progress. I would also like to express gratitude to my technical consultant with Y Soft Mgr. Juraj Michálek and Mgr. Jaroslav Klech for the frequent insightful consultations, valuable advice and guidance. And finally thank you to my loving family and girlfriend. iii Abstract The aim of this thesis is to develop a showcase application to demon- strate the possibilities RhoMobile cross-platform development frame- work offers. Other goals include evaluation of the support, quality of documentation, community, and overall viability for commercial use. iv Keywords smart phone, Android, iOS, Windows Phone 8, RhoMobile, cross- platform v Contents 1 Introduction 1 2 Cross-platform Development of Mobile Applications 3 2.1 Motivation and Caveats ....................3 2.2 Approaches ..........................4 2.3 Overview of Frameworks ...................5 2.3.1 Hybrid Application Frameworks .
    [Show full text]
  • Motorola Rhomobile Suite V5.0.38
    11/2/2016 Motorola RhoMobile Suite MOTOROLA RHOMOBILE SUITE V5.0.38 CONTENTS 1. Description 2. Release Notes 3. Device Compatibility 4. Components 5. Installation 6. Usage Notes 7. Known Issues 8. Usage Notes for 2.2 APIs 9. Known Issues for 2.2 APIs 10. Supported Ciphers 11. Part Numbers DESCRIPTION Thank you for selecting Motorola as your mobility solution tool provider. User friendly mobile applications are key to leveraging the power, value and return on investment of your mobile solutions and with Motorola RhoMobile Suite you can significantly reduce the time and cost associated with mobile application development. RhoMobile Suite allows you to create flexible, OS­independent, hardware­agnostic applications that look, feel and act the same on every supported device. You can rapidly create robust mobile applications that can include a wide range of advanced data capture capabilities. Whether you want to streamline your warehouse, delivery or service operations or enable more robust asset tracking & visibility, Motorola RhoMobile Suite will help you get your enterprise mobility solution up and running. RELEASE NOTES Version 5.0 Service Pack 3 (5.0.38) Roll­up of previous 5.0 service packs Issues Resolved MobileIron will now work with Rho iOS applications. In order to work with the per­application VPN functionality of MobileIron it is necessary to configure both the settings ios_net_use_curl=0 and ios_direct_local_requests=1 as explained in the Runtime configuration guide Version 5.0 Service Pack 2 (5.0.30) Roll­up of previous 5.0 service pack New Features Added iOS apps can now be built with 64­bit support.
    [Show full text]
  • Understanding What Makes Rhomobile Tick
    A Saviance Technologies Whitepaper Understanding what makes RhoMobile tick Why Businesses are keen to use RhoMobile Mobility platforms are becoming a vital aspect for businesses. The market for mobile application development platform is in a period of rapid growth. Developers are investing a lot of time and money in creating powerful sets of development tools and managing different versions of each mobile application that help businesses. The RhoMobile suite which is a robust set of development tools enables businesses to build feature-rich, native enterprise applications. It gives developers more time and better tools to write smarter apps for the enterprise, quickly and reliably for all mobile operating systems. It also helps organizations to optimize their IT resources so that they can create cost-effective and innovative solutions that help businesses efficiently. RhoMobile Suite is comprised of five Rho elements, namely: RhoStudio RhoMobile RhoConnect RhoHub RhoGallery This whitepaper focuses mainly on RhoMobile, the next evolution in Mobile Application development and its future in Mobile Computing. What is RhoMobile? RhoMobile is a mobile application framework which is used to develop Mobile applications from scratch. Selected as Best Startup at Interop 2009, it enables developers to use HTML and Ruby to create native iPhone, BlackBerry, Windows, © Saviance 2014 All rights reserved www.saviance.com Symbian, and Android applications. The framework in it is called Rhodes. Rhodes is a free and open source MVC-based framework which is written in Ruby under the MIT license for building native cross-platform mobile applications. Rhodes enables developers to create a native app, and porting the app in cross operating systems such as Android, iOS, BlackBerry, Windows Mobile, Symbian etc.
    [Show full text]
  • Cross-Platform Mobile App Development Using Rhomobile Cross-Platform Approaches
    Cross-Platform Mobile App Development Using RhoMobile Cross-Platform Approaches ● Hybrid approach is most promising ● Web technologies are widely used everywhere ● Web developers (front-end HTML/JS) are much more numerous and cheap than iOS or Android devs ● There are some OS like WebOS and FireFox OS where you can write application only using web technologies ● By Gartner report currently in the enterprise environment 90% of applications are web or hybrid Cut Expenses ● Hybrid cross-platform solutions like Phonegap or RhoMobile allow to reduce development cost in three and more times ● It’s possible to involve existing web developers ● Existing web applications code reuse ● App code portability between development platforms What exactly is “RhoMobile” ● The set of development tools for creating data-centric, cross-platform, native mobile consumer and enterprise applications ● It allows developers to build native mobile apps using web technologies, such as CSS3, HTML5, JavaScript and Ruby ? ● With RhoMobile you can track offline changes on mobile clients and synchronize with a corporate backend ● It dynamically updates application UI when backend data changes RhoMobile Suite ● RhoStudio allows development, debugging and testing of cross-platform enterprise apps with single tool simplicity ● The foundation of RhoMobile Suite, Rhodes is an open-source cross-platform development framework for rapidly building native apps ● For access to built-in APIs for barcode scanning and RHOMOBILE SUITE RFID, support for the widest range of operating
    [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]
  • Developing Mobile Educational Apps: Development Strategies, Tools and Business Models
    ACSIJ Advances in Computer Science: an International Journal, Vol. 3, Issue 1, No.7 , January 2014 ISSN : 2322-5157 www.ACSIJ.org Developing mobile educational apps: development strategies, tools and business models Serena Pastore 1 Astronomical Observatory of Padova, INAF Padova, 35122, ITALY [email protected] with the several market analysis companies [2]. Mobile Abstract actors involved in the mobile ecosystem (Fig. 1) includes The mobile world is a growing and evolving market in all its devices manufacturers (e.g., Nokia, Samsung, RIM aspects from hardware, networks, operating systems and Blackberry), software platforms providers (e.g. Apple; applications. Mobile applications or apps are becoming the new Google, Microsoft), applications developers and mobile frontier of software development, since actual digital users use operators that in each country (e.g., in Italy Vodafone, mobile devices as an everyday object. Therefore also in an TIM, 3G) provide Internet connectivity. A single mobile educational environment, apps could be adopted in order to take advantage of mobile devices diffusions. Developing an app device is composed by specific hardware and software should not be a decision linked to the trends, but must follow platform that deals with the peculiarities of these systems. specific strategies in choosing target devices, mobile platforms, Mobile devices should follow the user's mobility and distribution channels that in these contexts usually go (therefore mobile devices are generally of reduced size through e-commerce sites called stores (e.g., Apple Store, and weight, such that they can be transported easily). Google Play, Windows Phone store). Furthermore the design of Their hardware components manifest limited processing an educational mobile app requires a careful analysis on the power and memory, little screen dimension, but a variable methodologies to be adopted and the available tools especially if numbers of other hardware such as cameras, network the aim is to build a successful and useful app.
    [Show full text]
  • Rhomobile Suite V5.1 Contents Description Release Notes
    11/2/2016 RhoMobile Suite RHOMOBILE SUITE V5.1 CONTENTS 1. Description 2. Release Notes 3. Device Compatibility 4. Components 5. Installation 6. Usage Notes 7. Known Issues 8. Usage Notes for 2.2 APIs 9. Known Issues for 2.2 APIs 10. Supported Ciphers 11. Part Numbers DESCRIPTION Thank you for selecting Zebra as your mobility solution tool provider. User friendly mobile applications are key to leveraging the power, value and return on investment of your mobile solutions and with RhoMobile Suite you can significantly reduce the time and cost associated with mobile application development. RhoMobile Suite allows you to create flexible, OS­independent, hardware­agnostic applications that look, feel and act the same on every supported device. You can rapidly create robust mobile applications that can include a wide range of advanced data capture capabilities. Whether you want to streamline your warehouse, delivery or service operations or enable more robust asset tracking & visibility, RhoMobile Suite will help you get your enterprise mobility solution up and running. RELEASE NOTES Version 5.1 Bar code capability for WP8. Timer Capability for WP8,IOS,and Android Extending printing support for USB in Android Extended Support of Config for WP8,Android,IOS New Features Added Support for TC70 GA1 (Non rebranded Device) Android KitKat. Support of Windows embedded MC18 hand held device Support for WAP4 CE6.0 device. Common API Support for Camera for both Ruby and JavaScript Device API Supported on Symbol device,which gives the capability to the
    [Show full text]
  • Cross-Plattform Development Einer Mobile Business Application Am Beispiel Einer Tourismus Anwendung
    ulm university Universität Universität Ulm | 89069 Ulm | Germany Fakultät für Ingenieurwissenschaften und Informatik Institut für Datenbanken und Informationssysteme Cross-Plattform Development einer Mobile Business Application am Beispiel einer Tourismus Anwendung Masterarbeit an der Universität Ulm Vorgelegt von: Daniel Glunz Matrikelnummer: 702033 Wirtschaftswissenschaften [email protected] Gutachter: 1. Prof. Dr. Manfred Reichert 2. Prof. Dr. Franz Schweiggert Betreuer: M. Sc. Johannes Schobel Dipl.-Inf. Marc Schickler 2014 “Cross-Plattform Development einer Mobile Business Application am Beispiel einer Tourismus Anwendung” Fassung vom 13.10.2014 © 2014 Daniel Glunz This work is licensed under the Creative Commons. Attribution-NonCommercial-ShareAlike 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/de/ or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA. Satz: PDF-LATEX 2ε Zusammenfassung Möchte man eine mobile Applikation für ein mobiles Betriebssystem entwickeln, so programmiert und kompiliert man diese mit dem jeweiligen SDK der Plattform und hinterlegt sie dann in dem jeweiligen App Store. Um sich den Aufwand der mehrfachen Entwicklung für die unterschiedlichen Plattformen zu sparen, entwickelt man eine Cross- Plattform-Anwendung, also eine Anwendung, die unabhängig vom Betriebssystem des mobilen Endgerätes ist. Dafür gibt es inzwischen verschiedene Frameworks, die diese Entwicklungsmöglichkeit unterstützen. Einige davon werden in dieser Arbeit vorgestellt. Diese Arbeit behandelt die Entwicklung einer plattformunabhängigen Applikation für mobile Endgeräte anhand eines solchen Frameworks. Als Anwendungszenario wurde eine Tourismus-Applikation gewählt, welche als Client Informationen wie Nachrichten, Veranstaltungen, Bürgermeldungen und Sehenswürdigkeiten abruft und auf dem mo- bilen Endgerät des Nutzers darstellt.
    [Show full text]
  • Motorola Rhomobile Suite V4.0.0 Contents Description
    11/2/2016 Motorola RhoMobile Suite MOTOROLA RHOMOBILE SUITE V4.0.0 CONTENTS 1. Description 2. Device Compatibility 3. Release Notes 4. Components 5. Installation 6. Usage Notes 7. Known Issues 8. Usage Notes for 2.2 APIs 9. Known Issues for 2.2 APIs 10. Supported Ciphers DESCRIPTION Thank you for selecting Motorola as your mobility solution tool provider. User friendly mobile applications are key to leveraging the power, value and return on investment of your mobile solutions and with Motorola RhoMobile Suite you can significantly reduce the time and cost associated with mobile application development. RhoMobile Suite allows you to create flexible, OS­independent, hardware­agnostic applications that look, feel and act the same on every supported device. You can rapidly create robust mobile applications that can include a wide range of advanced data capture capabilities. Whether you want to streamline your warehouse, delivery or service operations or enable more robust asset tracking & visibility, Motorola RhoMobile Suite will help you get your enterprise mobility solution up and running. DEVICE COMPATIBILITY RhoMobile Suite supports iOS, Android, Windows Embedded Handheld, and Desktop Windows XP / XPe / 7 development. On MSI devices the Rhomobile Suite supports Android, Windows Embedded Handheld 6.1, 6.5 and Windows CE 5, 6 & 7. Not all APIs will be available on every supported platform, please refer to The online API compatibility document (http://edgedocs.rhomobile.com/guide/apisummary) for a comprehensive list. Consumer Devices This
    [Show full text]
  • Cross-Platform Solutions and Rhomobile Platform
    Cross-platform solutions and Rhomobile platform ● Mobile cross-platform solutions overview ● Introducing of Rhomobile platform ● How to start with Rhomobile Enterprise mobile development specific Enterprise devices Consumer devices Special devices ● BYOD ● Win CE/WM still used ● Useful for many cases ● Migrate to Android ● iOS and Android dominate. ● A lot of software developed for WinCE/WM Enterprise mobile software specific By the device set : 1. iOS, Android, WinCE/WM - not one OS. Different H/W level of devices. 2. Special H/W 3. Special peripheral By software: 1. Sometimes just web portal is enough. 2. Access to special H/W 3. Databases synchronisation between mobile device and backend 4. Mobile application is just part of complex solution. OLD GOOD LEGACY DEVICES What is mobile application place in enterprise solution Mobile application is just part of complex solution ! mobile devices personal computers Backend servers Browser PC data Server WEB Browser MD data DB Application DB sync Application Other important things Cross-platform development is always a tradeoff! + + = + + + + Web technologies are dominate ! Mobile cross-platform solutions architectures Mobile cross-platform development architectures SImple not cross-platform Web Native Hybrid Mixed Hybrid Native Application cross-platform Application cross-platform Application cross-platform Application cross-platform Application Platform Browser UI Framework WebView Framework WebView platform dependent or UI HTML/CSS/JS code cross-platform UI + Logic code HTML/CSS/JS UI +
    [Show full text]
  • Survey on Native and Hybrid Mobile Application Development Tools
    International Journal of Advanced Research in Computer Engineering & Technology (IJARCET) Volume 6, Issue 9, September 2017, ISSN: 2278 – 1323 Survey on Native and Hybrid Mobile Application Development Tools Shruthi Sasidaran Different operating systems run on different smart Abstract— Mobile phones have drastically phones – Android, iOS and Windows being the transformed from being simple devices to being most widely used. These platforms use different fully – functional pocket – sized computers, programming environments, each with its own equivalent to any desktop or laptop. This language and APIs, to develop unique and high – typically led to the requirement of mobile end user experience apps. The increased demand of application development and mobile – friendly such apps gives rise to the necessity of cross – user interface design development. Hence it is platform mobile app development frameworks, to important to understand, learn and analyze the ensure that apps gain access to the largest user – different types of mobile applications that are base they possibly can, irrespective of the platform present in the market. This paper conducts a they use, resulting a low cost – in terms of money, survey on the types of various mobile time and effort [1][5]. applications, a brief comparison between them, and the various application development tools Organizations have understood the necessity to available in the market – for both native effectively use smartphones and mobile apps to applications as well as hybrid applications. reach and attract customers. Many organizations have started encouraging users to utilize their Index Terms—Native Applications, Hybrid mobile apps and websites for using new and existing Applications, Xamarin, HTML5, Android, operations.
    [Show full text]