The app works with some abstract items. Those can be shown in list or on map
Bordered button in list leads to map view and vice versa, bordered button on map leads to list view.
Everything would be fine if we hadn't to deal with hardware "Back" button. Lets imagine 3 states of navigation backstack
- Main -> List
- Main -> List -> Map
- Main -> List -> Map -> List -> Map -> List -> Map -> ......
Im quite unsure what "Back" button should do in cases 2 & 3. Should it lead user thru full backstack to main page ? Or should it probably only show last map and last list and then skip all other pages ?
When user changes view from list to map the current filter is preserved but can be changed via application bar button.