The State Changers met to discuss the most efficient and user-friendly way of setting up Web forms. The main concern was whether to split a form requiring lots of input into different pages with multiple elements, or to include everything on a single page. There's always a risk of overwhelming users with too much information at once, or discouraging them by making the form appear too long to complete.
Also, they discussed the inclusion of business-related, free form fields and the option to upload business related images for personalizing the client’s experience. It was suggested that the most unique information should be asked first to push users to complete the form, as completion rates drop when people don't finish forms on their first attempt. So, the aim was to allow users to complete the basic mechanical parts first, while creatively engaging with the form in the initial phase, making for a fun experience. They considered breaking the operation down into four elements: boilerplate details, pictures, text information about the business, and a required donation to a nonprofit organization. Formulation of these into steps across the top was also suggested. Mention was made of form generating software like Reform, Typeform, Paperform, and Jotform as potential solutions, as they are cost-effective and reduce the burden on the website - they could be embedded into the site. Using these tools also offers the chance to adopt good User Experience designs from their well-thought models. No specific mention was made of 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 12/26 )
