Many organizations struggle to realize the promise of enterprise mobility despite big investments, in large part due to the long release cycle for apps and the difficulty of getting users to update. What if you could deliver a constant stream of incremental updates to your users automatically instead? In this session you’ll learn how microapps, which are single-purpose and cross-platform apps designed to support a single step in a user’s workflow, can ensure employees and business partners have a unified and secure way to access data and complete workflows.
Microapps help enterprises easily develop native mobile apps and modernize their legacy systems by easily developing Mobile apps for their existing systems.
Microapps is the fastest way to enterprise mobility and can dramatically reduce time to market and increase their employee productivity
Visit for more details: https://eloha.io
Blog: https://medium.com/eloha
Mobility is becoming not only the new digital hub, but also the bridge to the physical world. That’s why mobility will affect more than just your digital operations — it will transform your entire business.
SmartPhones are ubiquitous, I bet everyone of us has a mobile phone over here, right? Why don’t we do a simple exercise now, I will ask you 3 questions if your answer is yes raise your hands,, if its no then well don’t raise them.
it is estimated that there are around 5 billion Mobile Phone subscribers on the planet, almost 2/3rds of the world population already has a mobile device
Mobility has helped to
- Create new industries and business models that never existed before
- Revolutionized our communication
- And transformed our live for good.
And with the advent of Smartphones we have all the services at our finger tips, there is an app for everything right from booking a taxi to ordering food, groceries etc, Back in india you can even book a tuk tuk with your phone
But can we say the same about Enterprises
In an Enterprise setup, we as an employee or business users still depend
- On paper processes,
- Web applications that offer shrink to fit mobile experiences and
- Siloed apps that are seldom used and eventually abandoned.
So how did we end up here, to answer that question lets see how enterprise app evolved over time
Initially it was mostly one huge monolithic application that would handle most of the business functions.
Then software vendors started building solutions that solved a specific business problem, like CRM, ERP etc, and organizations deployed these solutions alongside the legacy applications.
Then people started using SaaS applications these SaaS applications lived along side the purpose built solutions and legacy applications.
It is estimated that an organization has anywhere around 20-60 different systems, Which is huge.
Each system has its own interface, some of these systems offered mobile apps, while few only offered web interface that can be accessed through mobile phones
And few legacy systems only have dated Windows GUI, and few systems had dated Character GUI.
So now we have different apps to access different systems and these apps provide different user experience which makes it hard to use them, and more over off the shelf applications are not custom tailored to each organization.
Each organization is different, they have different processes and workflows, so what organizations need is more Custom mobile app development that Streamlines & Simplifies the processes and workflows
Now lets look at this from a different perspective, lets look at Enterprise mobility maturity model to find out where we are
The First Phase is Aware Phase:
- Here organizations don’t have any mobility strategy
- But they are aware about the benefits of mobile applications bring in
- They mostly have shrink to fit web applications that are accessed through mobile phones and few applications that are approved by IT
The next phase is Reactive phase:
- Few custom applications deployed
- Few mobile apps that come free with saas solutions
- Few web applications accessed through mobile browser
Here orgs are aware about the benefits and they also have a strategy to include mobile apps through custom app development and through SaaS mobile apps
The last Phase is Proactive phase and this is where the magic happens:
- Here they have Articulated Strategy about how they will go about developing and deploying mobile apps inside their org
- They have required tools and technology to develop custom applications that are containerized and truly transform the processes and workflows
In aware phase they initially see increase in the productivity and then it decreases as they quickly hit the limitations
And as they transition to reactive phase they see significant decrease in the productivity as they face lot of challenges in developing custom applications
and from user endpoint they see drop in the productivity because of sheer number of apps that offer inconsistent user experience
And this is where organizations find it hard to convince their employees to adopt mobile apps
The Proactive phase is where the magic happens
they start to see increase in the productivity tremendously, here orgs streamline and simplify process and workflows by developing containerized custom applications and delivering them through an omni channel
And most of the orgs are still in reactive phase
The key to climbing the maturity model is:
- to develop custom applications that are tailored to business needs
- Delivering them through a containerized omni channel experience
So first step in developing custom applications is to choose an application architecture
These are different architecture choices we have, each choices have their own pros and cons,
so how do we decide which one to choose, to do that lets look at the tradeoffs of each architecture
In the top quadrant we have Native and Jit compiled technologies that provide great user experience and don’t rank so well on the productivity front
Because applications needs to be developed for different platforms, and investments needs to be to hire right talent with right skills
Where as at the bottom end of the spectrum be have web and hybrid that offer great productivity because of all the good that web technologies bring in
But the user experience takes a big hit as they cant match the native application experience
Moreover application architecture is just one part of the puzzle
To develop a mobile application we also need different services/solutions like
Manage application management
Mobile content management
Identity and access
Preferably Some kind of mBaaS solution that simplifies backend development
The list of prerequisites is so huge that it prohibits lot of organizations from making any investments
How can we climb up the maturity model
The key to climbing up the maturity model is to breaking down the problem into Microapps
Microapps are Single purpose Cross-platform applications that helps you to accomplish single step in a workflow,
to understand microapps better lets take a step back and see what are different parts that makes up a mobile app
All these parts put together makes up the whole mobile application, but there are certain features that are repeatable and are needed for all apps
So when you extract the repeatable parts, what you will be left with is just your application UI and the business logic of that app
What if we can create a generic container application … <Continued>
That handles all the repeatable parts, then all that you will be left with is the UI and business logic.
Also what if we split the application into atomic units that are self sufficient and dynamically deployed into the container app.
This will help speed up the application development and also offer focused set of atomic features that will help users accomplish task in a single step.
These atomic units are Microapps
Any number of microapps can be deployed onto the container application
Now lets look at the microapps architecture,
There will be a container application that will be installed on the host OS
And any number of microapps can be deployed onto the container app dynamically without Appstore approval
Here we choose Nativescript as the technology as it offers great native user experience while helps create applications from a single codebase, this is an excellent fit for microapps architecture
Now if you look at the tradeoffs it has best of both the worlds
You get an exceptional User experience with native apps, and great productivity improvement, since all platform specific nuances is handled by the container and nativescript gives us the flexibility to develop cross platform apps from single codebase,
But application architecture is just one part of the puzzle
What about all the other services that are needed for application development, this is where we come in
Say Hi to Eloha microapp platform ( https://eloha.io )
Eloha is a high productivity Mobile application development platform or in short it’s a Microapp platform
that provides you will development and management tools which helps you to build and publish microapps easily
It is powered by an industry standard MBaaS platform (Kinvey) that provides you with all the services that are required for your application backend
It provides you turn key connectors to your enterprise systems and content management systems which helps you accelerate enterprise application integration
Lets look at the Eloha platform architecture
The Microapp architecture has three main pieces:
The Microapp containers - We have one container per platform: Android, IOS and Web
The platform itself built on top of Kinvey (Kinvey.com) and we internally use Datadirect(https://www.progress.com/datadirect-connectors) to connect to enterprise content and enterprise applications
We also provide Management and development console that helps in building and publishing microapps
Now lets look at each of this piece individually
First the microapp container
Container is like a clean slate on top of which you can publish any number of microapps, which is built using NativeScript for mobile containers and KendoUI for webcontainer
Next part is the platform itself
- The platform is built on top of kinvey, it provides you powerful sdks that helps you deliver mobile experiences without having to reinvent the wheel
It gives you a serverless nops backend, so that you can forget about infrastructure and writing backend services and focus on delivering value to your business
And it provide you with Connectors that help you connect to your enterprise system and identity providers
And we have development tools that helps you in building Microapps faster
The development tools are a combination of Cloud and Local, which have flexibility that lets you use both code-first and low code development paradigms.
The low code tooling takes your developer productivity a step further by providing templates that lets you easily scaffold a complete microapp in seconds without any coding.
We also provide you with management tools that lets you put access restrictions and provides you insights about the usage.
Now lets look at what microapps are in detail and lets explore few use cases that microapps can solve and streamline
So we already established that microapps are Single purpose, cross platform apps that help accomplish a single step in a workflow,
But what makes up a microapp
How do you interact with them
What are different parts of Microapps
Lets try to understand this better by digging deep into different parts that make up a microapp
At its core we have a Microapp container that can host any number of microapps.
The container has:
A Widget feed, which manifest events in a easily actionable cards
There is a screen with App shortcuts which help discover and launch Microapp UI
And the last thing is the Microapp UI itself
Apart from this the container also manages the Lifecycle of Microapp and Isolates it from the nuances of the underlying OS
So container is a clean slate which can host any number of microapps and Microapps are like lego blocks that can be added into the container dynamically
Now lets try to dissect microapps and see what few examples where it can be applied to:
The Microapp in itself is made up of just two parts
Microapp Widget and Microapp UI
- Microapp Widget:
The microapp widget is the place where all the action happens, any events that occur in the underlying system will be manifested as easily actionable cards
Each widget can show one or more cards, Widgets can also provide dynamic information that refereshes after certain time interval for eg: there could be a widget that provides site analytics from a hubspot backend which will be updated every hour.
Microaap UI:
You can think Microapp UI as a place where you can create new records in the system or a place where you can get records out of system
Eg: Expense Forms, Contacts lookup, Ticket creation etc
The Microapp Cards have unified UX regardless of the backend system that is generating that event, users will get a feel as if they are interacting with one single system. Furthermore each card provides useful insights that can be easily consumed and users can also act upon the events right from the cards, this will drastically reduce the number of steps which would otherwise have taken.
Few examples of cards include:
BI Charting
Approvals: Timeoff, PTO etc
Information widgets
Analytics: Sales, usage etc
Statuses
etc
Micro app UI is the interface through which new records can be created in the system and it can also be used to retrieve information from the system.
The Microapp UI can be invoked from the widget or from Microapp shortcut screen.
The Microapp UI also provides a unified user experience and lets user easily accomplish a task in one single step, compared to fiddling with multiple logins and applications he would have otherwise had to deal with.
Few example of Microapp UI include:
Ticket Creation
Corp directory lookup
Submit forms
Submit reports
etc
Lets see a demo (Added a gif in the next slide)
Microapp Cards:
Makes it easy to take actions on events
Full screen to see gif play
Microapp UI:
Perform task in a single step
Microapp helps enterprises Transform their business services and apps into Engaging Mobile Experiences.
Microapps can help your organization to:
Streamline business workflows
Improve internal communication by reaching out to their employees through one single portal app
Empower fields service agents by providing all the service in one single mobile app and simplifying the tasks
It also helps you to consolidate business apps and service into one single mobile app, you can go from having 10 different interfaces to one single mobile app with unified user experience
Will drastically simplify approvals by providing easily actionable insights though Microapp cards
Reduces app fatigue by minimizing number of apps to be installed to one
Increases your Business and employee productivity
So Microapps can help you go from this:
To this!!
Reach out to me at srireddy@progress.com to know more or visit https://eloha.io
You can also follow our blog on medium: https://medium.com/eloha