Hello friends,
I was trying to give my applications a more professional touch and was thinking about the "About Us" welcome screen.
It turns out that starting with this screen is a good idea since it serves as a nice "transition" between the content of our applications and the user's arrival. Perhaps someone might not agree with my perspective (which is completely valid), but essentially, if I configure it to start with "About Us," the truth is that it doesnโt always start with this screen. Instead, once the session is initiated, it goes straight into the appโs main flow.
Iโd like this screen to be unavoidable, followed by a view Iโve configured called "Inicio" (start), which serves as the login page. Only after the session is validated would it proceed to another screen (also transitional).
Iโve considered creating an "Onboarding" type view because I aesthetically like it the most for these cases. However, it includes a "Done" button that allows navigation from the onboarding view to the main views of the app.
The issue is that I can't achieve the desired behavior because onboarding views seem to lack the possibility of using a linktoview()
.
Does anyone have any ideas about this?
Solved! Go to Solution.
There is no way to force the display of any particular view when the app is opened except the very first time the app is opened after install. That one exception is what the Starting view setting is for.
Whenever i need to do something like this, I'll typically use a combination of Onboarding views + special views for the initial flow.
The trick with the onboarding view to get around the lack of an action event (which is a much needed thing), is to make use of it's "Finish View" setting.
For instance, the following is a flow that I've implemented for an app:
The onboarding views allow you to specify a view they should go to when ending... so I've made special forms to continue the flow, which have their own form-save events (isolated from any of the other forms for that same table) that make this force flow smooth. The forms then continue the flow to the next stage, and one could continue this if one wanted for additional layers until everything is established and ready to go.
Hope it helps!
There is no way to force the display of any particular view when the app is opened except the very first time the app is opened after install. That one exception is what the Starting view setting is for.
Thanks steve! I will see other ways
Whenever i need to do something like this, I'll typically use a combination of Onboarding views + special views for the initial flow.
The trick with the onboarding view to get around the lack of an action event (which is a much needed thing), is to make use of it's "Finish View" setting.
For instance, the following is a flow that I've implemented for an app:
The onboarding views allow you to specify a view they should go to when ending... so I've made special forms to continue the flow, which have their own form-save events (isolated from any of the other forms for that same table) that make this force flow smooth. The forms then continue the flow to the next stage, and one could continue this if one wanted for additional layers until everything is established and ready to go.
Hope it helps!
Of course, my friend. Thank you for such great tips. Iโd say it would be useful if you could create a post in Tips and Tricks whenever you have time.
Thank you so much for your contribution!
User | Count |
---|---|
17 | |
12 | |
9 | |
4 | |
4 |