I see the starting view no longer applies. Is there any way to set the starting view again. I like to start the app every day on the same view as this is the one I use the most. My app has about 20 views and I would like to start each day on the same one, not in the middle of some random view I last looked at. Surely other people would like their users to start on a specific view each time??
The behavior you want is gone.
Starting view now only applies the very first time the user accesses the app. Thereafter, the app tries very hard to restore the most recent view when the user returns to the app.
It was a bad change.
Ohhh… I was thinking that setting was going away.
I was like…
So when does the About view pop up. Is it only a manual select? It was working ok before with the about view for first timers start and Starting view for every day use.
Wow. I was wondering why it seemed so erratic these days. I really think there should be the original “starting view” option, and if not enabled can default to last view?
Very uncomfortable to find that “starting view” is only “one time starting view”.
I was also under the impression that setting was to start the app on the same view every time the app is opened, that’s much more useful for the users of my app.
I don’t know.
My impression is that the old behavior was considered a long-standing bug, that it was never intended to work that way.
Yes, this change in behavior was accidentally introduced probably around the end of 2020 and reported to us.
To @Lynn 's question about the About view, the About view is not a view that app creators define in UX > Views and historically it got its own toggle to enable it. As stated in the description (Instead of a view, show the About pane when the app is started.), it should overwrite the starting view if turned on.
If there is interest for this to be a feature, I’d recommend one of you to add this to our Feature Requests.
I think the best solution would be to update the Starting View dropdown to be an option of:
-Views in your App
-An expression that generates a navigation link
-“Attempt to resume” from the last known view
Here’s my thoughts, most apps, if they are online and have not been touched long enough to require a sync, DON’T want to resume where they left off. Most of the time its also not an issue for these apps either. Production type apps and apps used offline, I can totally see to most of the time wanting to resume. But in any other type of app, it looks sloppy. If I’m going to get interrupted with a sync (that I didn’t manually trigger), then I might as well also get sent back to my starting view that I defined. HOWEVER, if the app was closed/minimized/whatever for not long enough to trigger a sync, then it 100% should always go back to last known view.