Exploring Webflow and WeWeb for Accounting Software Development and API Optimization
The State Changers in this meeting discussed developing an accounting system with software other than Bubble. They mentioned Webflow as a potential choice because of its ease of use, but voiced concerns about building this more intricate system with their current knowledge of that software. Furthermore, they predicted they needed added functionality, such as adding columns or rows to their work.
WeWeb was mentioned as an alternative with apparent similarities to Bubble, but there was debate on whether its dynamic design, which is more suitable to static pages that use data input, would be able to handle such a task.
Other possible solutions recommended were Glide and Airtable. Glide operates on spreadsheets which might suit their needs and Airtable's grid view was thought to be beneficial. However, it was highlighted that developing an accounting software was a big undertaking and one should consider if they could achieve the same result in an easier, more simple way.
The conversation switched to the structure of API calls. The idea was to simplify nested API calls into a singular call. The discussion revolved around looping to resolve the data structure issue, and using URL inputs to extract both the label and the number for the accounting system. It was stressed that this may not be the most efficient method, but it served as a starting point.
The meeting ended with plans to repeat these discussions in future sessions.
Keywords mentioned: Webflow, Bubble, WeWeb, Airtable, Glide, API, data structure.