During this meeting, the State Changers addressed two main issues: handling API errors and reducing API loading times.
One of the participants experienced intermittent 502 and 503 errors when testing their Zano API and expressed concern about these resulting in "no value" returns for a user. The errors suggest issues with Zano's gating level and the participant was advised to contact Zano support with screenshots of the problems. While discussing this issue, it was hypothesized that these errors could be a result of an overload on Zano's server, especially if it was being accessed excessively within a short period. However, after examining the user's request history and total API requests within the last 24 hours, this was ruled out—indicating an issue on Zano's side. Next, they addressed concerns of lengthy loading times despite relatively short API response times. It was suggested that these delays could be the result of the network's performance or the mobile device's processing power. To improve this, two solutions were offered: 1. Precaching or Optimistic Loading: Loading data before it is needed, ideally in the background while the user is otherwise engaged, to deliver seamless experiences. 2. Implementing Skeleton States: These UX-elements, often used by world-class apps, help build trust with the user during interstitial states by indicating pending content delivery. They concluded that although Zano offers response caching to accelerate server responses, this does not help in reducing the network transmission time. Therefore, client-side caching needs to be considered, possibly by using local storage for storing data and loading it from the local part of the app to cut down on demand-based work.
(Source: Office Hours 10/27 )
