The participants, State Changers, during the meeting discussed the implementation of a system that allows end-users to create and input their own values in a pre-existing table of habits and activities values. The goal is to have this user-generated input function in the same way as the pre-set table values. The State Changers also debated best practices for this process and used tagging as an example.
They suggested a method where the system stores the user-inputted tags as strings while having a stored database of known tags. The system would then attempt to match user tags to this stored database and supplement the user input with a comprehensive version of the tag. It was noted that managing the intersecting logic between the known and unknown can be complicated but would facilitate better functionality and user incentives to use known tags. Specifically, the State Changers mentioned models like Xano, Flutterflow, and React.js as examples of tags and how these can be optimised. Improvements on end-user experience and incentivization, as well as scalable feedback loops for system improvement, were discussed in the meeting. It was also mentioned that an add-on can be used for the look-up process to handle unknown tags. The State Changers agreed on the importance of preparing for future discussions by looking at prior video resources, posting questions in the help forum, and ideally supplementing this with a loom to help understand the context of the question.
(Source: Office Hours 3/8 )
