This question is referring to AppStudio FORM elements, not HTML Forms. But first some additional background. Also, this discussion is based on information in topic https://discuss.appstudio.dev/t/new-app-design-considerations-part-1-screen-size/1923
The UI layout of the app is the next step. I was referred to JustInMind recently and found it to be very helpful in designing the UI. The first step was to determine all of the screens/pop up questions/UI elements for the app - not the look and feel, but what questions to be asked and what are the possible actions and results. If you have a team, using the pro service makes a lot of sense, but the free lifetime version is extremely useful.
I separate the Look and Feel, as what JustInMind has for UI elements verses AppStuido do not exactly match up. And there doesn’t appear to be a way to “transfer” your work between them. So no real sense in spending any time with Look and Feel in JustInMind.
Once I had the UI concept going, I automatically start thinking about how it’s going to be implemented. I have one additional assumption. The App will all have the same basic screen layout - header, menu, footer, and an area to present questions (including the login).
So this question comes down to:
- Is it best to make one form object and modify the contents of the presentation area in the form object with each new question formatted as needed based on question type.
- Should there be a form for each type of question format, and then only the contents of the question itself would change and the program would change forms as needed based on the question format.
Another way to think of this question is: When would you use multiple forms in an app?