This meeting focuses on the discussion and troubleshooting of a web application functionality under development by State Changers. Specifically, they are working to correctly identify and highlight user selections on the platform. A significant part of the conversation is explaining how to use various web technologies such as JavaScript and HTML to manage web page elements and save information on those elements in an easily readable format for both the user and the machine.
This includes understanding the challenges with their existing toolset, and improving logic, potentially through code augmentation and introducing machine-readable labels and unique IDs. They also explored an approach to using domain object modeling to help identify which elements on a web page need to be updated based on the received user data. Further discussions touched on assisting the tool to clarify state changes, using class addition and removal to highlight user selections and to clear non-selections, and the task of tracking the overlap between different API responses to effect state changes. One important recommendation was considering the shift towards a more advanced web app development tool like React, most notably for tracking state changes, especially as the requirements of the web application project begin to outgrow the current no code/low code tools in use. Unfortunately, the entire transcript does not mention any of the predefined keywords such as "Xano", "WeWeb", "FlutterFlow", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda" except "Javascript" and "HTML". Other key details include the use of APIs for data lookup, storing user selection information, and changing the visual appearance of the web pages dynamically based on user interaction.
(Source: Office Hours 3/24 )
