Subsurface-mobile on iOS UI design questions

[Dirk Hohndel]

> On Mar 9, 2016, at 10:16 AM, Thomas Pfeiffer <thomas.pfeiffer at kde.org> wrote:
> 
> On Wednesday, 9 March 2016 17:37:11 CET Marco Martin wrote:
>> On Wed, Mar 9, 2016 at 2:13 PM, Thomas Pfeiffer <thomas.pfeiffer at kde.org> 
> wrote:
>>> 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.
>> the problem it may have in the current version is that horizontal
>> swipe is reserved for going to next/previous dive, a test may be done
>> to make vertical scrolling between dives instead (and see what
>> problems may arise from this)
> 
> I know about that, and I have addressed it in my reply. I still believe that 
> we can work around the conflict without changing either the forward/back 
> interaction or the previous/next dive interaction. 
> As can be seen in Peruse, they don't fundamentally exclude each other.

So we can't use vertical swipe because on smaller screens (or with very
long notes) we need to be able to scroll the dive details. But the nice
coincidence is that the only page on which we can't use the swipe to go
back (the dive details - as there we use it to switch between dives) is
also the one page that already has a context menu (for deleting a dive).

And of course, we already have the "Dive list" entry in the main menu,
so either way, I think we're good and I will implement what Thomas
suggested to see how this works out for us.

>> In the api refactor, also the top bar becomes some kind of breadcrumb,
>> that may help as well (if from user tests will reveal itself as being
>> a valid interaction model)
> 
> Yes, the breadcrumb would be another easy way to go back to the dive list 
> (thogh it would again be at the hard-to-reach top).

I still haven't found the time to look at the refactor branch. I really need
to do that in the next day or two so I understand the changes this implies
for us. I was too focused on getting iOS to the point where I can make
a first alpha package that people can test. Still need to learn more about
the mechanics of exactly how to do that...

And of course I need to get ready for the first official Android release.
And I finally need to take care of the 4.5.4 release.

/D