Uniting Two Mobile Apps: A Customer-Centric Triumph with React Native
In the ever-evolving realm of mobile application development, seemingly insurmountable challenges often emerge. In this blog post, we embark on a captivating journey to successfully merge two mobile applications into one, while overcoming initial scepticism. Our mission was no small feat: the fusion of an existing native mobile app with a new one built in React Native. Adding to the complexity, we needed to seamlessly accommodate an 18-month-long backend migration, rendering a complete replacement impractical.
Our journey commenced with two established mobile applications already in app stores: one for iOS, developed in Swift, and the other for Android, built with Kotlin. Both apps boasted favourable reviews and had a long history in the stores. They were also tightly integrated with the SAP backend. Our vision was to form a dedicated team tasked with crafting a unified application in React Native. Initially, the plan was to introduce this as a new standalone app while retaining the existing ones. Thus, the Channels team came into existence.
The Channels team represented a fusion of talents from EDF and Accenture, harnessing their collective expertise to tackle this intricate challenge. Our EDF engineers embarked on a journey to master React Native, fostering ample opportunities for collaborative mobbing and pairing exercises. In addition, bi-weekly engineering discussions became a staple, providing a platform to dissect new features, emerging technologies, and innovative problem-solving approaches.
0 Comments