Basic (?) on-boarding question

Hi, I’m just starting an app to help restaurants of a small town in the covid-context. It is to be “public” (free) to facilitate at maximum its acces; but, once the user uploads information & selects options, the app needs its coordinates to send her/him a summary.

The flow should then be:
Screen 1. Access without account/email -> Upload document [user specific column] -> Copy [button action]
Screen 2. Choose options [user specific column]

Screen 3. Enter user’s email & adress [create user profile]
Screen 4. Send email [button send] to the user with the previously collected information (when the user was not signed-up)

It’s for sure a basic question, but it’s my first “public” app, and I wonder how/if Glide could keep user specific information until the user is not signed-up?

Thanks in advance for your knowledge!

[edit: should it be a big ‘form’ that appears as home screen, with successive conditional visibility, and 1 single tab?]

In a public app, user-specific information is only kept for that session, which means if the user closes the app, that info is gone. You have to record the uploads and choices back to the sheet and tie them to the user’s email to combine info later on, I suppose.

1 Like

Thanks @ThinhDinh, this seems as a good news for me: if I understand well, while the user is not signed-up yet, the information that he is uploading - selecting - entering are “temporarily saved”, and if he creates an account in the same session, they will be recorded? (I’ve tried it that way several times yesterday, but something went wrong, I have to do it again). Thanks

I’m not sure about that create an account part to be honest. Are you using user profiles for it?

I found that if you use publish sign-in but you have comment functionality and user try to add comment system will force user to sign-in but I don’t know if it possible to performed other functionalities as public with email sign-in or not.
Then I always use public with email sign-in from start.

1 Like

If it’s a public app, the User will have to manually sign back in after the app is closed. Their info could all be saved though, as long as they log in with the same email address each time.

There’s no filtering by signed-in user though for public apps, so I’m not sure how you’d display items per user, unless you created a filter/view for each specific user and control visibility with actual email addresses and not just “signed-in user”.

Thanks @ThinhDinh @Nocodemobileapp @shchc.
Maybe should I put all my flow* (1 to 4) in 1 single screen / tab, which would be a “User” sheet in a Form.

Screen 1. Access without account/email -> Upload document [user specific column] -> Copy [button action]
Screen 2. Choose options [user specific column]
Screen 3. Enter user’s email & adress [create user profile]
Screen 4. Send email [button send] to the user with the previously collected information (when the user was not signed-up)

[Edit: apparently forms cannot write to user specific columns… arrgh 🆕 New containing screen context for conditions]