RhoMobile Open Source FAQ
Why go open source?
To enable the platform to grow as a whole and not be limited by what just Zebra can provide.
RhoMobile is only one part of a set of tools and utilities that developers can use to build enterprise grade devices. We provide multiple options so developers/customers can choose what best fits their skill set and solution requirements:
- RhoMobile for cross-platform using web skills
- EB for web-based applications
- EMDK for Android, for native apps
- EMDK for Xamarin, for cross platform apps for developers who have .NET skill set
RhoMobile supports both Zebra enterprise devices and consumer devices. We recognize that there is wider interest in RhoMobile beyond Zebra devices, as many customers use the platform for consumer OS devices.
Please visit the RMS Open Source Forum.
What are the benefits of going open source?
By taking RhoMobile open source, we believe our customers and partners can better recognize the benefits open
source brings:
- Innovation Acceleration: Companies and individuals can move faster, build more quickly; customers & partners can gain control of their IT investment; and all parties can benefit from each other’s enhancements, new ideas and challenges to the status quo.
- Better Software: When work is visible to the world, culturally developers tend to build better code – architecting their open-source code to be extensible, have minimal dependencies, and stable APIs.
- Community Learning: Encourages adoption for both Zebra & non-Zebra devices – advancing the platform as an industry platform, not just a Zebra platform.
- Share Challenges: During an era of scale, complexity, and ever-evolving operating systems, open source allows for collaborative creation of scalable solutions to new problems – making projects evolve faster.
- Control: Provides control to customers and partners using the platform – opening up the option to add new features, new OS support and more, specific to their solutions.
What are the migration options?
There are three migration options:
- Stay on Zebra releases. For customers who are satisfied with their current version/solution, Zebra will continue to sell and support existing versions of RhoMobile Suite (2.x through 5.4). There is no need to move to open source.
- Migrate to Enterprise Browser. If you are using older versions of RhoElements for a web-based application, you may continue to do so, or you have the option to migrate to Enterprise Browser if new features or new device support is required and is covered by Enterprise Browser.
- Migrate to RhoMobile Open Source. If your solution(s) require new platform enhancements, new OS support (such as iOS 10, or Android M) or new device support you will be able to migrate to the open-source platform – based on your own timing/need. Customers desiring assistance on the open-source platform can work with the open-source community as well as our partners, Tau Technologies and Kutir, who are committed to offering support options.
Which components of the current RhoMobile Suite will not be open-sourced?
- Hosted cloud builds will remain available to customers with subscriptions up to version 5.4. Customers using open source will be responsible for their own build environments or will be able to take advantage of environments if offered by other partners.
- Support for the Windows M/CE platform webkit is a third-party proprietary component that cannot be open sourced. Customers with solutions that use/need Zebra WinM/CE devices can remain on their current version of RhoMobile up to version 5.4.
- The WM/CE framework APIs will be open sourced without the webkit – allowing the community to provide their own webkit replacement or work with a partner such as Tau Technologies who is working on a webkit option.
- The RhoElements RFID plug-in for Windows Mobile/CE will not be available as open source.
- Open Source components of the current RhoMobile Suite include:
- Rhodes
- RhoStudio
- RhoElements
- RhoConnect (client & server)
Enterprise Browser and AppGallery use RhoMobile – will they be open sourced?
No. Although built on the RhoMobile framework, both are considered separate products and will not be transitioned to open source. They will remain separate offerings as they are today.
Where can I find the source code?
The open sourced version of RhoMobile can be found on GitHub: https://github.com/rhomobile/rhodes
What resources will still exist on Launchpad?
The resources on the RhoMobile space in Launchpad will refer to the RhoMobile 2.x - 5.4 versions of RhoMobile Suite. If you are using these versions, then these resources apply to you. If you are using the open source version, you should consult the readme documentation in the open source repo.
Will the pricing structure change?
Prices for existing closed-source versions will not change. Versions 2.x, 4.x and 5.x will continue to be sold and supported. The open-source release will be free to the public to use and provide contributions. Customers desiring support on the open source line will be able to purchase support from our partners, Tau Technologies and Kutir.
Will my existing Silver or Gold subscription change?
Silver and Gold subscriptions used with version 5.x will continue to receive support. If you want to move to the open-source line, you may work with the community for free, or purchase support from support partners.
What happens if I am using RhoMobile v4.x or v2.x?
There are no changes to RhoMobile v4.x and v2.x – they will not be open-sourced. You may continue to purchase support and licenses for your solution on these versions.
How will I get bugs fixed?
If you remain on your current version (v2.x, v4.x or v5.x) and have a current support contract, you will follow standard procedures and submit bugs to the ZenDesk Support Portal. If you move to the open-source code line, you will have the ability to hire support from other vendors also using/supporting the open-source software, or, address the bug and submit the fix back to the community.
Isn’t RhoMobile already open source?
Only Rhodes and RhoStudio are currently open source. With this move, we will be open-sourcing all enterprise grade capabilities including RhoElements enterprise API’s and our enterprise grade data synchronization engine RhoConnect and RhoConnect Client.
Will RhoMobile be included in the Gartner MADP Quadrant in 2016?
No. Once RhoMobile is open source, we will no longer have a commercial offering on the open source release and will not qualify for the quadrant.
How do I engage with partners if there is a customer requirement for RhoMobile?
RhoMobile partners, Tau Technologies and Kutir, have committed to offering support options for the open-source platform.
Edward Correia
19 Replies
Hello, I have a question.
Will Zebra keep updating the RhoMobile suite (even if it would be just itegration of the open source contributions)? What I am asking is, will current paying customers get updates to say RMS 5.5 and so on?
Or is the support provided by Zebra strictly limited to the current version 5.4 with no plans to support later version?
Thank you
Will the Rho software play nice with Apache Cordova?
Hi Adam- Zebra will honor existing support contracts and perform bug fixes up to version 5.4. Zebra will not be releasing new versions beyond 5.4. For support on the open source line our partners Tau (Tau-Technologies.com) and Kutir (<a href="http://www.KutirTech.com">www.KutirTech.com</a>) will be providing support options and have committed to being active contributors to new features/functionality on the open source.
Regards,
Eddie Correia
Where would the "launchpad" for the open sourced version be for discussions and such.
In the FAQs above, in the "How will I get bugs fixed?" section, it states that users will be able to "address the bug and submit the fix back to the community". How can I submit a bug fix for the open source version? (I would like to submit a fix for this bug: <a href></a> )
Thanks,
Rob Roberts
Hi, please check out <a href="https://github.com/rhomobile/rhodes">GitHub - rhomobile/rhodes: The Rhodes framework is a platform for building locally executing, device-optimized mobile ap…</a>
I dont get new post/responses notifications via email anymore.
What gives?
Hi Rob, please just create a pull request. Thanks.
Thanks Darryn. I created this pull request with fixes for two issues: <a href="https://github.com/rhomobile/rhodes/pull/813">https://github.com/rhomob…;
I also get a nasty error from Oracle Access Manager when trying to login thru SSO.
Not sure how the Zebra "closed source" forum upto RMS 5.4 is separated from the open source discussion forum.
Not sure why there cannot be an open source discussion forum outside of Zebra Launchpad, or am I missing something?
Hi, do you mean in terms of license? Being MIT Rho can be integrated into any Apache licensed project (including Cordova).
Technically, I'm not sure there would be too much benefit. Whilst it is possible to include a Cordova plugin in a Rho project and vice versa the amount of heavy lifting is more than just writing the thing from scratch.
Hi Dwayne:
All RhoElements 2.x plug-ins have been open-sourced and are available in the rhodes repository. So if you're referring to the RhoElements 2.x API, then it's all available under Rhodes repository referenced by Darryn in the prior reply.
If you need help getting it, visit this link --> <a href="https://github.com/rhomobile/rhodes/blob/master/doc/oss/getting_source_… to get rhodes</a>.
Regards, Eddie Correia
Is RhoElements currently available as open source? I have not been able to find the source-code.
Would also like a response to this. There is no information about Rho moving to a new ticketing system that I can find. We are now paying for support which we can't access.
Thanks for the quick response. I am not the main person on our account so I did not receive that email.
Now Rhomobile Suite developed and support by Tau Technologies(<a href="http://tau-technologies.com/">http://tau-technologies.com/</a>).
You can download current RMS versions from this: <a href="http://rhomobile.tau-technologies.com/index.html">http://rhomobile.tau-…;
Latest release is 5.5 (September 2016). 6.0 is coming June 2017 and will contain some major changes/new features (like new 2.3 Ruby VM, Node.js environment on mobile device etc.).
5.5.X - current version with new features - for developers
5.5.0.X - stable versions based on 5.5 release and contain only important bugfixes
Bugtracker: <a href="https://tautechnologies.zendesk.com/">https://tautechnologies.zendesk.c…;
Forum: <a href="http://forums.tau-technologies.com/">http://forums.tau-technologies.com…;
Hi Mark-
Check out the new <a href="/community/rhomobile-suite">RMS open source forum</a>.
Dwayne- I've received some additional information from Zebra's engineering department that might be helpful.
The command "app_type: rhoelements" when added to the build.yml of your Rho project will bundle all Zebra-specific APIs with the executables. This source code has never been exposed to the world before. Now all such common APIs are present under either "<strong>rhodes\lib\commonAPI"</strong> or "<strong>rhodes\extensions"</strong>
Locations of the individual open-source RhoElements 2.x APIs are:
For Android:
<a href="https://outlook.office.com/owa/redir.aspx?REF=ayLJ3P-i2ovWynLt1hPyVh1A6…;
For WM/CE:
<a href="https://outlook.office.com/owa/redir.aspx?REF=OYvfHzDrxvcyDVdtOvW1tVbW0…;
RhoElements framework:
<a href="https://outlook.office.com/owa/redir.aspx?REF=TUgpy0uc4CmR6wAd8YoAl2qGq…;
Hope this helps.
-Eddie Correia
Hi Mark, when we open sourced Rho we had 3 options to promote, either:
<ul>
<li>Build up the old Google group that was used prior to the original acquisition of RhoMobile: <a href="https://groups.google.com/forum/#!forum/rhomobile">Google Groups</a></li>
<li>Create a new group</li>
<li>Keep going with launchpad</li>
</ul>
We discounted using the original google group because there have been few posts in the past few years (understandably since people have moved to launchpad). In the end we decided to keep going using launchpad because Rho is still part of Zebra's solution suite and it is the most active community.
Conversations are currently going on to make it easier to distinguish open source from closed source documentation.