They encountered issues when the app's submissions didn't wrap in quotation marks and when JSON removed lists. Further, they identified an issue with compatibility between Xano and Flutterflow when querying all records. This action returns a list with a bracket rather than a curly bracket, which left the first element incompatible with Flutterflow. Therefore, they had to name the first element to bring forth a curly bracket that facilitated .notation through the rest of the code. The meeting involved a lot of debugging and backend issue resolution.
They discussed using App State in Flutterflow, where the app variable was updated with every action to aid in sending backend data. They also touched on possible improvements for the user authentication process, hinting at turning the authentication parameter into a persistent variable.
Finally, they explored issues with parsing submissions on Flutterflow and updating the list of JSON in the app state. They discovered that the response body should be recognized as user selection instead of being set as the app state body.
Despite the technical difficulties encountered and not explicitly mentioned through particular platforms or programming languages, the meeting offered useful insights into problem-solving methods for building apps, especially regarding the handling of data serialization formats, backend calls, and app state management. This discussion would be beneficial to software developers or folks interested in optimizing use between FlutterFlow and Xano.
(Source: Office Hours 5/15 )