Back Button Inconsistent ???

If I go to the Home page, select an entry, and then press the Back button, it takes me back to the previous resource instead of back to the Home page. Same for Library, Search, Documents.

Open the app to ESV.
Open Nav Drawer and select Home.
Select any entry on the Home page to open that resource.
Press the back button.

Ends up back at the ESV.

This seems inconsistent with the Guides section where you open a guide, choose a resource, press back and it returns to the Guide.

Also, If I open Home and, instead of opening a resource, I go back to the Nav Drawer and select Documents, then pressing back goes to the Home page.

Shouldn't the first example (in the bullet list above) also return to the Home page when pressing the back button? Ditto for other entries in the Bible section.

Find more posts tagged with

Comments

Graham Criddle

Open the app to ESV.

Open Nav Drawer and select Home.

Select any entry on the Home page to open that resource.

Press the back button.

Ends up back at the ESV.

When I do this - and get the same results you do - and press the back button again I then get to the Home Page.

Do you see that as well?

Drew Hannay

I believe what you're seeing is the expected behavior. There are two kinds of back button history to keep in mind here: "global" back history between app features, and "local" back history within a single feature. An example of local history would be in the read view, if you have the ESV open and navigate to a new position with the location seek bar, pressing back should return you to your original location. Another example of local history would be in the Favorites section...if you've drilled into a favorites folder, pressing back brings you back up a level. An example of global history would be opening the home page, then switching to the search page, then pressing back to return to the home page.

Global history is only used if the feature that is currently being viewed has no local history. For example:

Open the home page
Open the favorites page
Drill into a favorites folder
Open the search page
Press back to return to the favorites page (global history)
Press back to close the favorites folder (local history)
Press back to return to the home page (global history, since there's no more local history on the favorites page)

The apparent inconsistency you're seeing with Guide panels is because guide panels are part of the "Read" feature's local history (as are document panels and resource panels).

One last thing to note: the global history list is a "Most Recently Used" stack, which means app features won't get added to the global history more than once. Example:

Start the app, which opens to the home page
Open the search page
Open the home page
Open the favorites page
Press back to return to the home page (removes "Favorites" from the global history stack)
Press back to return to the search page (removes "Home" from the global history stack)
Press back again to exit the app ("Home" has already been removed from the global history stack, so there's nothing to go back to)

This is so if you've been using the app for an hour or two and have switched between a lot of features, you'll still be able to back out of the app without pressing the back button hundreds of times.

Let me know if there's still any confusion about any of this!

Randy W. Sims

https://community.logos.com/discussion/comment/536105#Comment_536105

Sorry, I haven't had much chance to respond yet.

Thanks for the explanation. The implementation you describe makes sense. It still just seems a bit wonky in practice, from a user perspective. Basically, it appears that it exhaust the local history stack before pop-ing out to the global stack?

App opens to home

Nav -> Library -> Open ESV
Nav -> Library -> Open BKC
Nav -> Home -> Morning & Evening
Nav -> Search(Bible, Faith) -> Gen 15:6 NET
Back = Morning & Evening
Back = BKC
Back = ESV
Back = Search
Back = Home
Back = Library
Back = Close

It makes sense from the implementation you describe, but is a little less useful in practice. A flattened history stack would be more ideal. The workaround is to always use the Nav Drawer instead of the Back button (at least for those few features... since everything else works as expected).

Thanks.

PS: Notice on the Home screen it takes >40 secs. to populate (unconnected) Reading Plans form Faithlife. I don't think I've ever stayed on that screen long enough to see those before now.

Drew Hannay

https://community.logos.com/discussion/comment/537492#Comment_537492

PS: Notice on the Home screen it takes >40 secs. to populate (unconnected) Reading Plans form Faithlife. I don't think I've ever stayed on that screen long enough to see those before now.

Do you have a lot of group reading plan invitations? Those are loaded from the web (since you haven't connected to them yet), but I've never seen them take more than 2-4 seconds. Not sure it's relevant, but one change in 4.0.4 is that those plans now appear after existing reading plans instead of before them.

Randy W. Sims

https://community.logos.com/discussion/comment/537497#Comment_537497

Do you have a lot of group reading plan invitations? Those are loaded from the web (since you haven't connected to them yet), but I've never seen them take more than 2-4 seconds. Not sure it's relevant, but one change in 4.0.4 is that those plans now appear after existing reading plans instead of before them.

Yes, there are 29 of them. I did first notice this in 4.0.3 and that the position has changed, but not the load time. The load time is fairly consistent (and on a fast wi-fi connection). I also meant to mention that they don't appear to be cached in any way. If I switch away from the Home screen and immediately back it has to load them again.

David Schwegler (Faithlife)

https://community.logos.com/discussion/comment/537492#Comment_537492

Sorry, I haven't had much chance to respond yet.

Thanks for the explanation. The implementation you describe makes sense. It still just seems a bit wonky in practice, from a user perspective. Basically, it appears that it exhaust the local history stack before pop-ing out to the global stack?

Right, yes that is correct.

We definitely discussed our options here during development, and we're not sure there's one 'right' solution that handles all user scenarios. For example, a frequent case is switching to a different resource in the library -- let's say you're reading in the ESV and want to quickly look up a verse in a different version, so you switch to your library and pick the LEB. Now that you've seen it, you wish to return to the ESV -- currently, pressing back takes you directly back to the previous location in the reading view (the ESV). In a 'flat' structure, back would take you back to your library, and then you'd need to press back again to get back to where you were reading before. In that scenario, the Library itself isn't an interesting destination.

On the other hand, he best argument for the 'flat' structure is Search, where you're likely to want to be flipping back and forth with several search results, and thus want back to take you to Search after viewing one.

We're still considering options here, and we still may decide to change it. Thanks for your input.

Drew Hannay

https://community.logos.com/discussion/comment/537500#Comment_537500

I also meant to mention that they don't appear to be cached in any way. If I switch away from the Home screen and immediately back it has to load them again.

I'm not sure I can do anything about the initial load time, but it definitely shouldn't be reloading every time you open the home page. I've fixed this and it'll be in the next beta.

Randy W. Sims

https://community.logos.com/discussion/comment/537515#Comment_537515

We're still considering options here, and we still may decide to change it. Thanks for your input.

it definitely shouldn't be reloading every time you open the home page. I've fixed this and it'll be in the next beta.

Thanks David and Drew.