This meeting focused on addressing the user-interface feature known as "breadcrumbs" and how they function concerning two questions related to navigation. The State Changers elaborated on two uses of navigation: repeatability and directional prompts. They noted that breadcrumbs could function as 'deep links', where a specific URL leads back to the same point in navigation, enabling the restoration of a prior state. The State Changers suggested that breadcrumbs are often used to go backwards, advising instead to think of potential lateral directions the user could navigate within the application. The need to keep relevant context in the URL to ensure the smooth functioning of the breadcrumb approach was mentioned.
The conversation then shifted to JSON files and structuring data in local storage. The State Changers clarified that JSON is an encoding scheme used for storing data string representing values, keys, arrays, and other elements. The State Changers advised that everything stored would be strings and could be easily converted into more complex structures like objects or arrays. As the conversation progressed, they deduced that the data in question was indeed an array of objects nested within an object, confirmed as the desired format for storing data in this context. Overall, the meeting focused on navigation in interfaces using breadcrumbs and efficient data storage using JSON. There was no mention of the keywords: "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", "serverless", "State Change", "ScriptTag", "OpenAI", and "AI21".
(Source: Office Hours 3/27 )
