Ionic and Onymos – Better Together
The Ionic Framework is wonderful and wildly popular open-source UI toolkit for building performance, high-quality apps using web technologies.
Onymos Features-as-a-Service, available for Ionic, is a suite of foundational Features for building complex enterprise apps using standard web tools.
They sound about the same, causing people to sometimes ask – “We are using/considering Ionic Framework, why do we need Onymos?”
“We are using/considering the Ionic Framework, why do we need Onymos?”
To answer this question, we need to dive under the covers to understand the full extent of the Onymos Fabric.
UI Elements + Backend Functionality
As an example, let’s think about implementing Chat functionality in a mobile app.
We’ve all used a Chat function in different apps or contexts. In general, we all know what to expect from Chat. But often there is variability in the corner cases of every implementation. Why? Because a developer is being asked to re-create the user experience out of the individual elements.
Sure – UI elements are great, but they don’t constitute a full Chat experience.
With the Ionic UI toolkit, developers have access to all the interface components (i.e. a text window, Send button, icons for Camera, Photo Library, etc.,). Then they have to spend the time and effort to implement the Chat functionality, service logic, and backend plumbing.
But with Onymos, the Chat function is fully implemented ‘out-of-the-box.’ Plug the Onymos Chat Feature into your App and start Chatting.
The last thing any development leader wants is their most valuable resources – software development engineers – spending time exploring the quirks of various Chat implementations to decide functionality.
Customize, if needed
One of the unique aspects of Onymos is that customers receive all the Features as licensed source code. Not just the UI level, but the functional logic and back-end Cloud service connectivity.
So dev teams can customize any aspect of the Chat function, from front-end look and feel settings through to the actual service flow.
Of course, the source code is also important to ensure the security of, and trust in, the Fabric.
Ionic supported on… Ionic
When an Enterprise team orders a Fabric, it’s delivered tailored to their build environment (Cordova, React Native, Swift, Java, Ionic,…). Therefore, Onymos Fabric for Ionic is built with… Ionic elements.
The Onymos team used the underlying Ionic UI elements to build out the end-to-end Chat user experience. So adapting or modifying Onymos Chat is very straightforward, particularly if the team is already working in Ionic.
From Touch to Cloud – we did all the work
Onymos Chat is everything from representative User Experience screens (where your users Touch) to integrating with Device functions like Camera and Photo Library to the actual Realtime Database and Storage where Chat messages are stored and processed in the Cloud. Hence, the “Touch to Cloud” moniker.
The grunt work of data capture, storage, and retrieval (direct to your Cloud system, no Onymos server in the middle) is built into Onymos Chat (actually, all Onymos Features). You add in your Cloud provider’s Access Key and Secret key in the configuration file of Onymos Chat and your “data path” is completely yours.
Thus saving you and your team the time and effort of building the end-to-end functionality.
Onymos is complementary to the Ionic Framework. If your team is developing in Ionic, and you want to get your team focused on building business value rather than debating the intricacies of Chat (or any of the other nearly 20 Features we provide), then check out Onymos.