IMO Apple is long overdue admitting that putting navigation buttons on the top bar was a mistake. Fine in the era of the original iPhone, but as phones get progressively bigger and taller, less so. The swipe back gesture works in most situations, but I was a fan of Allen Pike's mockup of bottom navigation on the iPhone X (or, "Pro", at the time):
Having navigation at the bottom is one of the few things Android got absolutely right at launch when compared to Apple. But back to notifications, Android isn't great either: if a new notification arrives while I'm swiping old ones away there's no consideration that I might not want to swipe away something I haven't even read yet, so it disappears immediately and with no way to get it back. Frustrating.
That looks too much like how Android navigation works. Apple will never go for something like this.
- Go back one document (like internet)
- Go back one screen
- Leave the app
A lot of Android users just hammer the back button and then the application icon again if they want to go to the Home screen of an application.
Also it's always there even if you don't have a document to go back to. Nor it provides extra information about the previous document like the title.
Personally I would like a back button down there (next to the home button) that also holds a miniature of the previous document that animates in and out of place.
I've never been able to understand why the operating system does not manage this case and ignore input that occurs within say 0.25 seconds of the dialogue's appearance, on the grounds that humans generally can't react so quickly to something they just saw, so they must not have really meant it.
I like your idea of a .25 second delay. I can normally send a movement request to my hand in about .13 seconds (fastest time I can click twice on a stopwatch is .13 seconds), so .25 is good for me.
I feel like Facebook does this in their app when you post something to a page and it pisses me off to no end. I know as soon as I post something it's going to pop up a full-screen confirmation so I'm hovering over the X to close it and as soon as it pops up I tap it... and tap. And tap. And tap tap tap tap tap tap come on I have other stuff to do and tap tap tap tap and now finally it closes.
Except that's not what happened. My friend James logged in, a moment before I clicked and his name replaced hers where my mouse was. I absentmindedly typed "Hello sexpot!"
Well, we laughed it off eventually... but yea.
That's why Firefox save file dialog is inactive for the first few seconds.
My generalized solution that would work in any interface layout is to add new interface elements as disabled, and leave them disabled for maybe 1 full second. This would eliminate 90% of false clicks on fast moving popups.
Personally I think the issue is slightly overstated (or I'm just not popular enough and get fewer notifications) but my use pattern usually would naturally lead me to ignore such notifications by turning them off completely. Only messages get a pop-up for me on Android (or banner in iOS) and for large group chats they only get buzzes or noises.
Maybe iOS and Android can have a priority group you can set for instant delivery and then hold non priority notifications until a period of inaction from the user, adding an small delay.
But really, the occurrence rate seems pretty low to me from my workflow. And I live on my phone at work.
Kind of ironic to make this sort of calculation only to post it on medium, where it can't be read until a pop-up nag is closed. I wonder how much agony I accumulate in a year of accidentally clicking medium links.
It seems to me that if that’s genuinely the case, the problem is with the number and type of notifications received, which iOS gives tools to manage on an app by app basis.
1. Are currently logged in to Medium on your preferrred browser on every computer you typically use.
2. Are not in an incognito window.
3. Are using the correct browser (e.g. don't be signed in via chrome then hit a default browser link in ios).
This same approach could be used to pause movement on a web page during mid-render, for example if an ad or other content is late to load but the user is already clicking on a link. How many times do we end up clicking on something unintended because the page re-renders mid-tap/click?
Starting with the Samsung Galaxy S4 or S5 the phone had the ability to use finger proximity as a highlighter of sorts. I loved it, but never saw the functionality really used for more than visual candy effects.
I’d rather build in a hidden timer, so taps on a notification only trigger an app change after a certain amount of time. E.g. 0.5 seconds after it popped up.
They didn't think of that. I guess in the same way that Apple didn't think of the problem presented in that post.
Still, a solution is needed.
I wish they’d also force apps to differentiate between functional notifications to actually use the app (eg “Your Uber has arrived!”) vs advertising notifications (“Discounted Ubers today!!”) I want the former but not the latter. Currently I don’t have that choice though, it’s all or none.
4.5.3 Do not use Apple Services to spam, phish, or send unsolicited messages to customers, including Game Center, Push Notifications, etc. Do not attempt to reverse lookup, trace, relate, associate, mine, harvest, or otherwise exploit Player IDs, aliases, or other information obtained through Game Center, or you will be removed from the Developer Program.
4.5.4 Push Notifications must not be required for the app to function, and should not be used for advertising, promotions, or direct marketing purposes or to send sensitive personal or confidential information.
Not everyone has the Plus model.
Currently(0), we use the same virtual grid for visual layout as for mouse/touch interactions. If there's a box displayed visually, then there's a corresponding box that's available to receive clicks. If that box moves 100px down the screen, then the click-receiving box also moves 100px down the screen immediately. If you clicked the original box's location just as it moves, the computer replies with something like, "hey idiot, why did you just click empty space?" Why can't the computer be a little less of a bully and recognize the intent of the user by looking into the past a little to see what the user tried to click?
Instead of keeping these grids in lock step with one another, the click/touch-receiving grid should be delayed by 10-200+ milliseconds (and tunable -- esports players on one end and elderly/disabled folks on the other). This grid from the past is actually what you intended to click.
Back to the example above, if you click the box just as it moves, the click is now checked against this slightly-old grid instead of the current (suddenly changed) visual location of the box, and the computer correctly detects that the click was aimed at the box.
0: in any system I've worked on; I imagine some system has tried to make this better, though?
This echoes the Saving Lives anecdote:
> "Well, let's say you can shave 10 seconds off of the boot time. Multiply that by five million users and thats 50 million seconds, every single day. Over a year, that's probably dozens of lifetimes. So if you make it boot ten seconds faster, you've saved a dozen lives. That's really worth it, don't you think?"
While my home machine came out of hibernation yesterday evening I stroked the cat. I would have probably done that anyway while the authentication screen waited for me, had it started up faster.
While my work machine started up this morning I discussed the outcome of one of yesterday's problems with a colleague. This took several minutes so the PC starting in 20 seconds instead of 30 would have made no difference at all.
There are far more important reasons to not interrupt someone's workflow than "closing the notification takes precious seconds from my life". It's not the 2 seconds it takes to switch back to the other app, it's the 1 minute 45 seconds it takes to get my mind back to my original task or the 23 minutes that I'm distracted by whatever the attention-thief was.
Or worse yet, it's the lifetime and several hundred dollars when I become so frustrated that I switch to another phone. It's the $3 and hours of use that I've wasted when I switch to an app that doesn't demand push notifications.
Complaining about seconds wasted is ridiculous. If a second is "wasted", you're losing a lot more than just that one second. Don't make your argument based on the least impactful point.
Let's not forget that on iOS you can disable every notification, which is the much better option.
It could also detect when there is a tappable element under the tap-sensitive middle of the notification, and introduce a short delay only in those cases.
If there was to be a delay, 0.5 seconds sounds way too long. More like 0.2 - 0.3 would be good, and in the meantime (during the delay) the banner could pass the taps through to whatever element was visible before the notification came along.
Have it change colour, and say "1 new Mail notification" etc, and if you tap that, you get the proper context notification show up.
With the exception of the iPhone X, all iPhone devices have almost identical UX. In this way I do not think the author considered all of Apple's customers. Furthermore the SE, 6s and 7 are entry level phones, and Apple has an invested interest in attracting more entry level phone buyers, and in making current entry level phone users have as smooth as possible upgrade experience.
When holding my phone one handed, and a notification appears I want to open, I often tap the very side of a notification. Reprogramming my motion to reach farther would require effort. This is a cost. The author makes no mention of the costs of the UX change. Apple collects data on where a person taps on a push notification and if it appears to be a mistake. Apple is in a place to make data based design decisions. Fairpixel is not in a place to make data based design decisions on Apple's operating systems.
The purpose of the article is not to inspire change in Apple's iOS, but to push Fairpixel's brand as experts in UX/Design. I think it shows impulsiveness. Suggesting changes on hundreds of millions of devices based on evidence of one person's experience is irresponsible. Pretending like a change in UX is 100% positive and will not have costs is dishonest. Marketing your boutique firm as smarter then Apple at UX is arrogant. This article would dissuade me from working with Fairpixel in the future if I were considering it.
Edit: All edits are grammatical in nature.
I find notifications great for a phone, but terrible on implementation on desktop. But maybe my workflow is more unique than most? Or maybe its just not evolved. It drives me bananas, in general because its so abused.
The other portion of this is Cloud buy in. If you purchase a Cloud product from Apple, the specific portion of Photos (the app) that unifies the experience across platforms - iPhone, iPad, Mac desktop/laptops - does not have one feature to back out photos and archive. You have to individually select and the previous feature to "select all" or cntrl-click from start to last on an image group has disappeared. They effectively make it impossible to export a catalog.
argh!!!! JACKIE CHAN MEME!!!!
I really don't like how notifications are used in general. They are a ui tool that we would ideally use to interrupt ourselves when it's truly necessary, but that's almost never the case.
When your screen is on, it's usually because you're doing something with your phone. If a notification comes in during this time, it shouldn't be able to disrupt your workflow unless you opt into that disruption. I love the idea of using the status bar to give a heads up that there's a new notification in the app. It's already used to provide a "back" button when you've opted to open an app from a notification (which, granted, was a controversial UI decision), so there is some precedent for it.
Generally though, most apps send you notifications when you don't need them. I'd argue that users wouldn't hate being taken away from what they were doing as much if it took them to something both time-sensitive and actionable. Notifications should be originate from a user's interactions (whether the active user, like when setting reminders, or other users, like when sending messages), and even then they should be used carefully. In the article, the screenshot shows the user getting a notification about a promotional email. There's almost never a scenario in which a user couldn't have waited until later to read that promotion. I love that the Gmail app gives you the option to only get notified for new emails in your inbox; that's a great first step. Things like group chats are still pretty broken (you want to know when there's unread messages in a chat, not every time someone in the group sends a message).
Another possibility is snoozing notification by learning how often a user will read notification immediately, so that notifications will not display for sometime.
Just put them all in a queue similar to a twitter feed, that can be reviewed later. This would be the best way imho to handle the need for focus.
Then people can decide to review these once a day, or multiple times a day, but when it actually makes sense for them.
This would also require the ability to specify an exclusion for some apps (ie. "notifiy always" vs "queue notification").
ps: the notification area is a sort of queue, but I don't want to see it on the homescreen as it still is begging for attention. Put it away in a separate app or area that can be reviewed intentionally.
I would always put information on the top and buttons in the bottom half. Unless it's stuff that's totally out of the normal flow of usage like a help button or a feedback form.
That's the real fix of that problem.
I guess its still an issue if you just want to ignore the notification for a moment and not get rid of it yet however.
I'd prefer a setting where you would be notified after you returned to the home screen. I'd like to finish the thing I'm doing before getting a notification. Maybe you can accomplish the same thing by turning notifications off, and just swiping down every once in a while?
Or another option to solve it??? Just don't show notifications when the user is "obviously" using their phone. e.g. if there's been any tap in the last 5s, make the noise but don't show the pop-up until the screen has gone untouched for 5s (the user can still swipe down from the top to see it).
And FWIW I (and I presume others) like getting notifications when I'm in other apps.
I miss shit all the time but idc
I'd be willing to guess users who have vibrate turned off as well are a very small percentage.
Edit: BTW the described idea probably wouldn't work with my Apple watch setup, because it seems there can be some latency between the iPhone and the watch with respect to notifications. I wouldn't want to get a vibration on the watch then be wondering for a few seconds "when is something going to pop up on my phone?" I realize technically the notification comes to the phone first under the hood... but where it is displayed first is a matter of programming.
Having seen how often the bluetooth/wifi calling and messaging fails b/w my iPhone and Mac, I decided against trying an Apple Watch. Is it any better?
Sometimes I have to turn on sound on the phone for things like Waze or for playing videos or music. But the ringer stays off (due to settings).
The connection with the iPhone and Mac seems fine. However, with my watch (1st generation) a couple of updates ago the lost phone ping feature got a new unwelcome degree of latency. It can now take up to 30 seconds for the phone to ping, where it used to be immediate. I don't know if this is the case for newer models. Nor could I say whether the problem is on the watch side, or the phone side (doesn't matter, I guess). But at least it still works.
Not all - I'd say that probably 80% of them are only allowed to show the banner with no sound or vibrate. Perfect example just arrived - Patreon. Handy to see the banner/lock screen because it's normally a new video to watch but it's nowhere near important enough to distract me.
- you can't click on them
- if you hover them with the mouse, they go transparent
- if you do try to click, the click will pass-through to the GUI element underneath.
They never ever get in the way. And you can find them again if you miss one. I like 'em.
Anyone know how to quickly dismiss these without taking an action?
I don't recall if the click was sent to the now-obscured target or if it was just cancelled. either way, Apple could apply this to all notifications very easily.
Is this a parody? Don’t people have real problems? This level of petty self–indulgence is almost worrying.
I‘m not disputing that this may be a minor annoyance. But to invoke „agony“ is an insult to anyone who has ever experienced real suffering or existential dread.
And to slap on the old „Dear Apple“ cliché just to get your 15 minutes of (limited) attention is somewhat sad.
What about "No" and "Not right now"?
No solution is perfect for everybody. There are tradeoffs. If you read between the lines you can see that in this tradeoff, they are optimizing for getting more people to stay up to date. Which has many benefits which arguably outweigh the annoyance you experience.
Also, why the implied snark?