Modularisation and Abstracted Approach for building flexible UI/UX Apps
With technology disruption taking over our everyday lives and with the advent of smart phone revolution, multiple mobile apps are released each day to simplify the lives of the customers. However, the success rate of all the apps released may not be foolproof.
Comviva builds and deploys secure, robust & user friendly apps as per client needs.
To stay ahead in this digital transformation journey, Comviva uses a Re-usable, Scalable, Abstracted & Optimised approach for Mobile App Development MicroApp Approach.
Problems with Monolithic Architecture
Developing separate apps to deploy same functionalities but with different UI & UX using Monolithic Approach was getting tedious for us
- Code Maintainability: Multiple duplicate codes are used across different apps/modules which have the same set of features
- Change Management: Adding / removing / changing feature in one of the existing deployments maintaining backward compatibility and extensibility was getting into a challenging task
- UI/UX Flexibility: Extremely difficult to manage different UI / UX across different deployments using same set of features
- Turn Around Time: On-boarding new deployment/change management was taking a lot of time to get into hands of end users
App Development Strategy Micro Apps
Comvivas App Development Strategy is to use the MicroApp Approach to:
- Deliver mobile app functionality fast enough with limited development resources
- Deliver apps with the high quality user experience (UX) needed to spark adoption
- Features are developed using MicroAppsconcept
- Product apps are developed by adding MicroApps as dependencies and stitching them using Routers
- Product apps can have their own user journey and them
 100vw, 624px” data-src=”https://www.comviva.com/wp-content/uploads/2020/10/1.jpg” data-srcset=”https://admin.comviva.com/wp-content/uploads/2020/03/1.jpg 624w, https://admin.comviva.com/wp-content/uploads/2020/03/1.jpg 300w” /></h3>
<h3>MicroApps An independently developable, deployable and testable module</h3>
<h4>Root MicroApp (#RMA)</h4>
<p>Setup in a separate git repo which is </p>
<ul>
<li>Developed independently as per <strong>MXVM architecture</strong></li>
<li>Deployed independently, as dependency, which can be used in any <strong>#FMA</strong>or <strong>ProductApp</strong>as per any UX / UI</li>
<li>Tested independently for Unit Tests using mock</li>
</ul>
<h4>Feature MicroApp (#FMA)</h4>
<p>Setup in a separate git repo which is </p>
<ul>
<li>Combination of #RMA along with <strong>Router</strong></li>
<li>Feature specific UI is designed and passed to <strong>#RMA</strong>as per <strong>MXVM architecture</strong></li>
<li>Feature specific <strong>User Journey</strong>is defined using Router</li>
<li>Tested independently for unit and UI tests using mock</li>
</ul>
<h3>MXVM Architecture</h3>
<p><img decoding=)
https://medium.com/@mfs.techblog/modularisation-and-abstracted-approach-for-building-flexible-ui-ux-apps-3fae0bc5a7dd?sk=325adbea9aed9181a1c14de80e970be9