Sorry, my name is Patricio, I’m from Chile. I’m reaching the community because I need help with a project I would like to build using Glide.
I’m not sure if this can be done with Glide, and how to do it. Maybe you can guide me.
Well, I’m trying to learn how to use Glide to build an app that allows users to create requirements. So in this context, the app needs to ask users different alternative questions and depending on the alternative they choose, show them another question. So putting it in simple words, the app has a “decision tree” behavior".
So that’s the first thing. The second thing I need to do, is in some of the questions that the app is asking to the user over the journey, might need him to insert text (for example, his name, email address, etc) and/or upload some files (could be an image a pdf or doc files).
So until now, it is a combination of alternative/answers questions, text answers, and file uploadings, around a “decision tree” behavior dynamic.
Ok, here comes the challenge. I need to feed a pdf file with the information I’m getting from the answers that the user is giving and the information that he is completing in the questions that require filling a text field. So when the user starts the journey, while he is advancing with the process, in parallel a pdf file (“requirement request”) will begin to be completed in those parameterized fields that require the information that the user is providing.
Ok, final step. In the last step of the journey, when we have all the information required by the user, two things need to happen before the journey ends.
Once the last question is answered, the user will be introduced with a registration/login view that needs to complete to formally send and register the requirement in the platform.
Once step number 1 is completed, the pdf will be already filled and has to be automatically sent to the user’s email and to me (LOL). With this, a folder with the name of the user should be created automatically on my Google Drive, containing this pdf with a description that begins with the date and time to identify it. Additionally, if the same user were to make the journey again, the new pdf document that originates must not replace the previous one, so this is why the date and time over the name of the document are very important.
Then the process is concluded.
Ok, one last thing here, that might be a little bit tough, some of the files that are asked to the user to be uploaded need be attached in the same pdf “requirement request” as Annexes.
I was talking with David from the Glide team and because the flow is longer than two interactions, and also apart of radio buttons single/multiple choices, dropdowns, information that the user has to enter over text fields, comments text areas, date picker, upload files and even e-sign (using a third-party), the best way go to get a better result and an awesome UI/UX design is using multiple screens (instead of conditional visibility feature that use for example the “party invite” template), so each answer sent the user to an independent screen, so there as a developer we can have more autonomy over the UX and UI.