This meeting of the State Changers revolved primarily around the difficulties one of the members, Daniel, was experiencing in his project involving FlutterFlow. He had spent several hours attempting to create a customizable calendar system for his application which tracks user's journaling habits, but hadn't made much progress. He had attempted to use FlutterFlow's badge package, but found the code difficult to understand. Dan's vision involved a user interface that could provide users with a view of their progress and gamification in a calendar format.
Multiple potential solutions were discussed. One suggestion involved reassessing whether customization of the existing calendar widget was necessary. Another suggestion was to construct their own calendar-like interface that offered more control. The discussion shifted to examine the logic underlying the triggering of certain features like a check-in bottom sheet, which was initially linked to the selection of a date on the calendar. However, the team suggested a simplification of this process by making it contingent on the page load event instead of the calendar date selection event. Overall, Daniel was advised to invest one or two hours into probing a problem then seek help or reassess the approach if no progress was made. Considering the app's impending launch, and after weighing priorities, it was decided that the current problem was not crucial for the initial launch and could be revisited later. It's noticeable that several keywords such as FlutterFlow, Javascript, and error have appeared in this meeting. The main emphasis was on topics like user interface development, problem-solving strategies and priority management.
(Source: Office Hours 5/2 )
