Continuing the discussion from An amazing future for OpenMRS:
There are some very interesting possibilities to consider for micro frontends, where a web application is comprised of relatively independent sub-applications.
- The article on Micro Frontends that @dkayiwa shared
- Another article looking at pros & cons
- An example of a micro frontend framework: single-spa
The biggest wins for OpenMRS would be:
- The ability to weave together web application functionality into a shared front end framework
- A potential solution for modular functionality (ability to mount & unmount parts of the application)
The biggest challenges for OpenMRS with a micro frontend solution would be:
- Creating an application with a consistent look & feel and user experience
- Avoiding a niche solution (i.e., an approach only OpenMRS and a handful of others are still using a year or two from now, where we suddenly “own” the framework including maintaining cross-browser support and the learning curve for new devs steepens)
- Handling context (e.g., which patient is selected) and communication between sub-applications without creating significant requirements on sub-application development or dependencies between sub-applications
Exciting to see how micro frontends are coming. It would be great to ride this wave… but choosing the right wave and not having it come crashing down on us.
Are there other examples of micro frontend frameworks like single-spa? Is there one that is leading the pack? What do folks think about the pros & cons of adopting a micro frontend for OpenMRS?