You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a number of entry-points to Explore, each with different contexts and expectations about what view is presented and what the filters are. Furthermore, most of these buttons push Explore onto an existing stack navigator, e.g. MyObs -> ObsDetails -> TaxonDetails -> Explore, or even more confusingly, Explore -> TaxonDetails -> Explore, and in these stacked contexts, Explore needs a back button to pop it off the stack and return to the previous screen (plus the previous Explores need to keep their state).
MyObs toolbar Explore button should
Show the Observations view
Show a back button that takes you back to MyObs
Have an accessibility label that makes it clear you are going to see all of your observations in Explore
Filter observations by the current user with no other filters, i.e. user_id=1&verifiable=any and no default geographic filters like nearby
TaxonDetails Explore button should
Show the Observations view
Have an accessibility label that makes it clear you are going to see observations of this taxon in Explore
Show a back button that takes you back to TaxonDetails
Filter observations by the taxon that are verifiable with no other filters, i.e. taxon_id=1&verifiable=any and no default geographic filters like nearby
UserProfile observations button
Show the Observations view
Show a back button that takes you back to UserProfile
Have an accessibility label that makes it clear you are going to see observations by that user in Explore
Filter observations by the profile user that are verifiable with no other filters, i.e. user_id=1&verifiable=true and no default geographic filters
UserProfile species button
Show the Species view
Show a back button that takes you back to UserProfile
Have an accessibility label that makes it clear you are going to see species observed by that user in Explore
Filter observations by the profile user that are verifiable with no other filters, i.e. user_id=1&verifiable=true and no default geographic filters
Default to Nearby with location permission otherwise Worldwide geographic filter
Not lose its state when you navigate away, i.e. when you are in Explore and set some filters then tap Notifications in the bottom tabs and then tap Explore in bottom tabs, those filters and those observations should still be there (Explore should not lose state when you nav to MyObs and back #1215)
Not have a back button
I would try to experiment with at least two different screens, one for the root Explore accessed from the bottom tabs that should never have a back button, and another for the Explore that can be stacked (with a back button). Ideally every stacked screen is a separate instance and doesn't navigate you back when you do something like Explore -> TaxonDetails -> Explore -> TaxonDetails -> Explore. Alternatively, maybe it would work if the bottom tabs button just resets the nav state.
The text was updated successfully, but these errors were encountered:
@kueda there's one other entry point I see for explore, from the logged out MyObservations screen. should that one operate similar to the bottom tabs entry point -- species view, default to nearby if location permissions are given, and no filters except verifiable? and should it have a back button to return to MyObservationsEmpty?
There are a number of entry-points to Explore, each with different contexts and expectations about what view is presented and what the filters are. Furthermore, most of these buttons push Explore onto an existing stack navigator, e.g. MyObs -> ObsDetails -> TaxonDetails -> Explore, or even more confusingly, Explore -> TaxonDetails -> Explore, and in these stacked contexts, Explore needs a back button to pop it off the stack and return to the previous screen (plus the previous Explores need to keep their state).
I would try to experiment with at least two different screens, one for the root Explore accessed from the bottom tabs that should never have a back button, and another for the Explore that can be stacked (with a back button). Ideally every stacked screen is a separate instance and doesn't navigate you back when you do something like Explore -> TaxonDetails -> Explore -> TaxonDetails -> Explore. Alternatively, maybe it would work if the bottom tabs button just resets the nav state.
The text was updated successfully, but these errors were encountered: