In this meeting, the State Changers discussed transitioning from AirTable to Xano, and connecting apps to QuickBooks through OAuth. AirTable was found to simplify tasks at a high level, but Xano was preferred for low-code models as it allows one to think more like a computer.
The key objective for the participants is to integrate QuickBooks tighter with their system, which requires learning OAuth2. They elaborated on the basics of OAuth integration, the flow of user redirection to QuickBooks, and the use of access codes.
The discussion then moved towards QuickBooks integration challenges, including setting up the flow, keeping track of access and refresh tokens, and using the interaction between front end, QuickBooks, and Xano.
The next part of the conversation focused on choosing between Adalo and Flutterflow as a front-end development tool for a new mobile app, with DraftBit, WeWeb, and Wizd also mentioned as potential tools to consider. It appears that the main challenge in this context is figuring out the API piece for QuickBooks to allow users to connect their accounts.
By the end of the meeting, the participants provided some next steps, split the questions into two parts (choosing a front-end build and setting up QuickBooks API), asking for help from the community regarding both components, and seeking advice for the API configuration on QuickBooks in an office hour setting.
Use of software like DraftBit, Flutterflow, Adala, Brave, WeWeb, Wizd, Glide, Airtable, make.com, Xano, QuickBooks, and OAuth was discussed throughout the meeting.
(Source: Office Hours 6/26/23 )