The State Changers meeting focused on the development of a user verification process for a web application. The primary function of this process is to validate the authenticity of the users by checking their age, location, and criminal record before any actions can be placed. A crucial aspect of this process is the implementation of a verification form, which also includes a terms display outlining the data collection and usage policies.
The verification page utilizes a mobile nav bar, and there was discussion over removing unnecessary elements such as the top header from the website in the web view. The agreed upon solution is to modify the URL and add an argument (such as no header) so that when the front-end recognizes this argument, the header will be hidden. This solution would require two steps – modifying the URL and testing if the web page can recognize and implement the argument. An alternative solution discussed was to create a specific page in Webflow that does not have a header. The general consensus leaned towards picking the right tool for the right job, emphasizing the use of Flutterflow for the web app and exploring other options for the desktop version. It was acknowledged that maintaining the same content across different web pages might be challenging but such content should ideally be managed more centrally. Concerns were raised over the time-consuming build process with Flutterflow. However, it was noted that this is a standard issue with this kind of process. The meeting concluded with the team looking forward to testing the changes and adjustments made to enhance the user verification process.
(Source: Office Hours 4/17 Evening )
