The State Changers meeting focused mostly on deciding which platform or technology is the best fit for building a reports dashboard application. The conversation centered around the comparison of no-code solutions, such as Webflow, and traditional coding methods like React. Some participants expressed the flexibility and potential growth in skill that come with using traditional coding languages in comparison to no-code solutions stating that initially one tool might seem fitting, but as understanding grows and requirements evolve, a different tool might be deemed better.
The discussion emphasized having a 'shopper's mindset'. They stressed the importance of paying attention to one's understanding of both requirements of the product and their technical capacity. In the conversation, the pros and cons of the rapid React.js development of a Tailwind UI and understanding varying technical capabilities using individual solutions such as WeWeb were discussed. The challenges of integrating advanced visualization libraries, such as d3.js with React were noted, emphasizing the need for a deep understanding of one's toolset before making a selection. The group concluded that there is no universal "right answer". Factors to consider when choosing the right framework or toolset include the kind of experience desired for the users, the usage understanding based on technical skills, and the added value to the customers. With pro code, there are more concerns compared to no code, and one must weigh if the additional controls gained are worth the increased responsibility that comes with it. Overall, the meeting offered insights into the advantages and disadvantages of no-code tools and traditional coding languages for creating applications. The participants agreed that the goal should be minimizing friction between the creator and the toolset, leading to a smoother transition towards serving the customers.
(Source: Office Hours 5/23 Extra: ReactJS )
