Discussion on API error messages and how to improve API loading times and implement preloading and skeleton states for better user experience.
In this meeting, the State Changers discussed two main topics.
First, there was a discussion about API errors, specifically the occurrences of HTTP 502 and 503 errors. It was determined that these errors are gateway-level errors and indicate that there may be issues with the server's ability to serve the code. The State Changers suggested reaching out to the Xano support team to report the issue and provide screenshots of the errors. Additionally, they mentioned that these errors could potentially be caused by spamming requests or being under attack, but it was unlikely in this case.
The second topic discussed was how to decrease API loading times in a mobile app. One suggestion was to implement pre-caching, where data is loaded ahead of time before it is needed by the user. This can be done optimistically to improve the speed of the app. Another suggestion was to use skeleton states, which are placeholder screens that show visual representations of the data being loaded. This helps build user trust and provides a more intuitive and credible loading experience. It was also mentioned that response caching on the server side can improve performance, but it doesn't help with network transmission speed. The State Changers concluded that implementing pre-caching and using skeleton states would be beneficial in decreasing loading times. They also recommended researching and implementing techniques related to skeleton states and pre-caching, using resources specific to Flutter Flow.
Overall, the meeting covered troubleshooting API errors and optimizing API loading times for a mobile app.