[SailfishDevel] No consistency across screens
Graham Cobb
g+jolla at cobb.uk.net
Mon Dec 30 15:35:39 UTC 2013
On 30/12/13 14:01, David Greaves wrote:
>> 4. No way to interact with things in the browser e.g. save a picture.
>
> A long press does that (although some pages seem to prevent it).
> We're aware that the discoverability of a long-press is poor.
And that is a big issue, unfortunately. And it isn't just a beginners
problem -- it is a problem forever with features you don't use often (or
which work differently in different apps).
How about a standardised gesture to request help on how to do tasks on a
screen (and also, for that matter, help on the fields you are filling in
on forms)? Doesn't waste screen space but helps with the really
frustrating "there must be some way to do this -- every other phone in
the world lets me do this" moment (or the "I know I can do this -- I did
it just the other day -- surely I don't need to Google for it yet
again?" moment).
>> 5. Power level and 2G/3G signal off page - only visible when moving
>> between 2 panes.
>
> By design - you rarely need this information but it's trivially accessible.
Poor decision. I need that information all the time -- a **lot** more
often than I actually interact with the phone.
But then you probably don't live and work in an area with poor coverage
and in a job where you are on calls for 80% of the day. Both pieces of
information are absolutely critical to me. (And for people who really do
use them rarely it suffers from the discoverability problem -- see above).
There is a reason every other phone has them visible at all times.
I haven't had the phone long enough to comment on the other things but
these two stand out.
Graham
More information about the Devel
mailing list