By giving examples and use cases of how differently backend interfaces can be built to minimize the negative impact on mobile app UX or performance, we could introduce several mobile-friendly changes. These changes saved our client performing dozens of hundreds of unnecessary duplicated work for handling some logic on Android and iOS. That is why we were trying to show the overall system “savings” value caused by the change of approach or architecture on backend.

One of the benefits for users is to have up-to-date information (asset prices, wallet balances, order statuses) available on the go. This has been achieved using WebSockets. However, the frequency and size of updates on certain screens, combined with the amount of detailed data being displayed, made us craft a fully custom solution that would manage updates without a performance hit, which could lead to a lack of responsiveness and poor user experience.