| Thread Previous • Date Previous • Date Next • Thread Next |
My concern with the difficulty is in the size of the target. There will be
a large vertical travel to reach the accept button, and only a small
vertical region that can be hit. It is also adjacent to a reject button, so
that might be problematic. I think Android's solution to this is the best,
with a slider that once grabbed can be moved in the desired direction.
Haptic feedback also lets you know when you've grabbed it successfully. As
far as doing something more important, maps is perhaps the only thing that
I can think of that would supercede this. It's at most a 30 second
interruption to whatever you're doing if you let it ring through, but the
interruption can be much shorter if responded to appropriately. For an
activity which has such a small response window, it seems like it would be
important enough to interrupt the screen.
Maybe make both styles an option? Or perhaps my concerns are completely
unfounded. I'm not the expert here by any means, so do whatever is
necessary. I'm just voicing an opinion.
On Fri, Jun 7, 2013 at 10:19 AM, Matthew Fischer <
matthew.fischer@xxxxxxxxxxxxx> wrote:
> I'm actually okay with this design. I personally find it annoying when a
> call takes over my screen, especially when I'm doing something more
> important, using maps, for example. And over the past few years it has
> become more clear to me that the primary purpose of my "phone" is no longer
> for making phone calls. I spend far more time using email, web, maps, and
> SMS.
>
> I do of course hope that your concern about "difficult to quickly accept"
> is unfounded, there are occasionally some calls that I really don't want to
> miss, but I think that the notification is there long enough to catch it.
>
>
> On Thu, Jun 6, 2013 at 7:24 PM, Josh Leverette <coder543@xxxxxxxxx> wrote:
>
>> I recently watched this demo[0] of the new notification OSD, and I have
>> some concerns about how not-prioritized a phone call is in the current
>> design. This was the comment I left on the Google+ thread about this video.
>>
>> "I don't know... I feel like the incoming phone call needs to take over
>> the screen fully and completely, in much the same way as happens with iOS
>> and Android. A phone call is too important for a small notification, and
>> placing notifications at the top of the screen places them in the least
>> optimal position for quick response. I can easily reach all around my 4.65"
>> Galaxy Nexus's screen, but the top is the least convenient place to reach
>> right before trying to put it up to my head to answer a call, I believe.
>> Especially with such small buttons.
>>
>> The aesthetics are coming along nicely though, so congratulations on
>> that, and for normal notifications that should be fine."
>>
>> Essentially, since the driving purpose behind a phone is to make and
>> receive calls, I feel like we should give ultimate priority to incoming
>> phone calls. If a user misses a phone call because of an easy-to-miss or
>> difficult-to-quickly-accept phone notification, then the device has,
>> effectively, failed at its intended purpose. Smartphones have expanded the
>> vision of what the device is able to do, but real time communication is
>> still not something to be diminished, is it?
>>
>> These are just my thoughts of course, and I'd love to hear opinions from
>> people who are more involved in the project than I am.
>>
>> [0] http://www.youtube.com/watch?v=zQMIf1cOyHc
>>
>> --
>> Sincerely,
>> Josh
>>
>> --
>> Mailing list: https://launchpad.net/~ubuntu-phone
>> Post to : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>> More help : https://help.launchpad.net/ListHelp
>>
>>
>
--
Sincerely,
Josh
| Thread Previous • Date Previous • Date Next • Thread Next |
