Get the latest tech news
Using the Strangler Fig with Mobile Apps
How to incrementally replace a legacy mobile application
Responding to a lack of reuse/significant duplication of efforts, high cognitive load in app teams and slow feature delivery, the organization chose a mobile technology stack that leveraged a Modular Micro-app architecture. Their long release cycle was related to risk aversion: Any outage in the application was a serious loss of revenue to the organization and also caused their customers distress due to the essential nature of the products they sold. We also utilized the feature flagging component of the experimentation tool to allow us to ‘turn off’ the experiment (revert to native app only) without the need for a release; greatly reducing the time taken to recover should any outage occur.
Or read this on Hacker News