Reanimating a legacy mobile app for food delivery

When we started working on this app, the state of affairs was far from effective and stable functioning. Through numerous users’ feedback, it became clear that there are two main areas of improvement that led to severe underperformance:

1. The app used to crash a lot, showing a high rate of instability and poor user experience.
2. Inadequate order processing made it almost impossible to get the orders delivered correctly, hence people gave up using the service due to unsatisfying app execution.

Needless to say, these troubles impaired the business overall and became a massive blocker on the way to success.

We started working on the app by making sense of what data we can access to track back the numerous errors that the app produced. And that was when we spotted the first challenge. We discovered that the final information we got about the app use (which pages are visited, which one was opened last before the crash, etc.) wasn’t clear enough. The answer was to introduce an updated crash report system. Consequently, we started receiving adequate data for thoughtful app examination and shaping further improvement strategies. Had we not done this, the whole development process would have been compromised in its very essence. It is immensely important to make sure you base your decisions on the fullest and most accurate information available.

Another interesting challenge we had to solve was integration with Huawei devices. You cannot have a Huawei version of the app without making any changes in your code. For example, simple Google maps were not available for use. In response to this problem, we have found a way to replace used components during the build process with some scripts.