Subsurface-mobile on iOS UI design questions

[Thomas Pfeiffer]

On Wednesday, 9 March 2016 05:54:41 CET Pablo Wolter wrote:
> What about scrolling to the left with the finger as you do when browsing on
> iOS devices to go back and to the right to move forward?
> 
> I don't know how this will work for abort/cancel that you mentioned though.

Actually, Pablo is exactly right!
Swiping left/right is the main method for going back/forward in Kirigami.
It should work in most cases for Subsurface, and we recommend to use it on 
Android as well (in addition to the back button), because it's easier to do 
than reaching for the back button in the corner of the screen.
The only point where it conflicts with your navigation is when you want to go 
back to the dive list because you use left swipe to go to the previous dive.

What Peruse (a comic book reader we're developing) does is this:
You use horizontal swipe to switch pages in a comic book. When you're at the 
first page and swipe back again, you go back to the list.
If you want to go back to the list from deep within a book, you use the 
context drawer.

You can put "Dive list" in the global drawer to quickly go back there if you 
don't have a context drawer everywhere.

So, long story short: The way for going back/cancelling is "Swipe from the 
left to the right".

If there are problems with this in other places, we can find fixes for them.

Cheers,
Thomas

> I'm eager to see it on iOS!
> 
> Pablo
> 
> On Tue, Mar 8, 2016 at 21:36 Dirk Hohndel <dirk at hohndel.org> wrote:
> > Hi Thomas,
> > 
> > So I really like where we ended up with the Android user interaction. It's
> > clean, it's consistent, it's easy to use.
> > 
> > I now have a working iOS build that I have been testing and there is of
> > course one massive difference between iOS devices and Android devices: iOS
> > devices have no back button.
> > 
> > How should we deal with this. Most iOS applications rather consistently
> > have a little back arrow in the top left corner. I'm pretty sure that
> > you'll tell me that you don't like that. So before I spend the time to
> > implement this only to then be impressed by a better idea from you, let's
> > shortcut the process... I'll ask you first :-)
> > 
> > What do you suggest we should do for the back / abort / cancel action on
> > iOS?

> > Something in the context menu? I hope not. We only have a context menu on
> > one single screen (the dive details edit) and that would be tap - drawer
> > open - tap - drawer close - whatever action back should be doing. NOT
> > smooth, IMNSHO.
> > 
> > Follow the iOS standard with a back button in the top left corner?
> > 
> > Something else?
> > 
> > Thanks for your help!