Improperly structured elements could lead to elements being called unnecessarily, resulting in increased RAM consumption.
The app has more than 100 high level components, meaning that a lot of them are going to consume RAM at the same time. Improperly structuring these elements could lead to elements being called unnecessarily, which could increase RAM consumption exponentially.
This needed to be improved, so, working with our UX team, we realized that we had components that we would be using across multiple screens. For example, the charging, billing, charging request screens. We would utilize a map element in the background that would remain a shared component across screens.
Our solution was to craft a hierarchical structure for iOS and Android apps. That way, we not only stopped elements from unnecessarily consuming mobile’s RAM, but also ensured that we properly defined behavior of components that are going to be used in multiple places.