Why is it the worst way? It would make total sense to combine those ideas.
Typically the user should be primed, given reason for what the notifications will entail, how frequent they might be and so on. It makes users much more receptive to them if you tell then why they should want to have this optional feature enabled, rather than a blind notification popup in first launch.
Right - a popup at launch with useful context rather than a blind "We want $ALLTHETHINGS".
I went through the updated app (v1.0.1) and the oAuth flow clearly indicated what I was granting access to. I'd be very curious if this was a fix by Google, a Google bug where requesting "full access" is missing that step, or Niantic changed the way they do oAuth (still a Google issue, the method lacking confirmation shouldn't exist).
It was some JavaScript injected into the WebView that automatically clicked confirm and sent a message to reposition the WebView offscreen as soon as that happens.
If they did that, they don't deserve a second chance at trust. That is outright malicious, and definitely a dark pattern. Their app deserves to be deleted and not used again.
Oauth2 has some serious holes - I have no idea if the Google login page is served by Google, or is simply a copy of their landing page designed to phish for credentials. This needs to be fixed as Oauth is becoming increasingly prevalent. We need some type of web of trust like SSL EV that gives me attestation the Oauth login page is being served by the company that I think it is.
I went through the updated app (v1.0.1) and the oAuth flow clearly indicated what I was granting access to. I'd be very curious if this was a fix by Google, a Google bug where requesting "full access" is missing that step, or Niantic changed the way they do oAuth (still a Google issue, the method lacking confirmation shouldn't exist).
It was some JavaScript injected into the WebView that automatically clicked confirm and sent a message to reposition the WebView offscreen as soon as that happens.
Terrible if true. Is there a source for this claim?
Not surprising given the incredible overwhelming number of people trying to play the game. I knew it would be huge, I never imagined it would be the phenomenon it is. (Go to a park at lunch or after work if you don't know what I'm talking about. Any park in the country.)
Especially that they launched US-only (?), but the whole world is playing anyway thanks to game's APK being spread on-line. I'm writing this from Poland, coming straight from 2 hours walk from work, catching Pokemon and leveling up on the way :).
Seems like this would be very easy for them to block since they know your GPS coordinates. They could just pop up a message saying "Pokemon Go is not yet available in your region," although, the good will demonstrated by allowing customers in other countries to play would probably be better than arbitrarily blocking them.
Typically the user should be primed, given reason for what the notifications will entail, how frequent they might be and so on. It makes users much more receptive to them if you tell then why they should want to have this optional feature enabled, rather than a blind notification popup in first launch.
Right - a popup at launch with useful context rather than a blind "We want $ALLTHETHINGS".
Exactly - I just meant not the default popup as soon as you launch without any explanation or justification.
This is what developers would do in the past with location access also, but as privacy awareness takes hold people are far more likely just to deny these permissions.
In iOS it's a pain for a user to actually reenable the setting after the fact.
Especially that they launched US-only (?), but the whole world is playing anyway thanks to game's APK being spread on-line. I'm writing this from Poland, coming straight from 2 hours walk from work, catching Pokemon and leveling up on the way :).
Seems like this would be very easy for them to block since they know your GPS coordinates. They could just pop up a message saying "Pokemon Go is not yet available in your region," although, the good will demonstrated by allowing customers in other countries to play would probably be better than arbitrarily blocking them.
They could. If they did, they'd probably kill the game on the spot, or at least significantly curtail its popularity. As it is right now, the game is a global phenomenon, and it's getting immensely popular worldwide.
I agree it is helpful to involve Google so it can be changed for existing Pokemon Go users. But I don't see how Google has verified the claim, since Google themselves have yet to release a statement. By the way, Google indorsed this comment. Believe me?
Web of trust I suppose. I trust Nintendo and I also don't think Google would allow such a brazen and public endorsement if it were untrue. If google does indeed reset permissions then you know they've at least been in contact. If it were a smaller company I'd like to see proof.
> If it were a smaller company I'd like to see proof.
Amazing how much trust the mere size of a company ensues.
On Android, Pokemon Go requests permission to access your contacts. I declined this access, and the app still seems to work (modulo the crashes & bugs that others have reported). Accessing the camera and location I can understand, but I don't want to give Pokemon Go access to my contacts.
Bit of OT Played Pokémon GO yesterday (iOS 1.0 version) and it was very buggy. Many bugs looked like they were server side (requests freezing), but there were strange rendering errors (like seeing only waves on the ground where Pokémon are, and not the actual Pokémon on them) that could be fixed by restarting the app several times. The phone also got absurdly hot, I never play on it, I don't know if it's normal for i…
Yep. Lots of other people are getting this, too. And it sucks. They all seem to be server load problems, but what gets me is that some things just don't need server updates, and they do them anyway. Oh, so you need to check in with the server every time I toss a pokéball. Niantic, it's like you've never heard of caching, combining packets, and client side prediction, or anything clientside for that matter. Sure it's…
Yeah, the server loading indicator every ball toss is grueling. It would be OK if it was reliable and always loaded after a few minutes, but a large portion of the time it locks up after several failed attempts to talk to the server and you have to kill the app. Then starting the app again shows the server error page 9/10 times, then you have to try the ball toss again, which may or may not work.
Not surprising given the incredible overwhelming number of people trying to play the game. I knew it would be huge, I never imagined it would be the phenomenon it is. (Go to a park at lunch or after work if you don't know what I'm talking about. Any park in the country.)
Especially that they launched US-only (?), but the whole world is playing anyway thanks to game's APK being spread on-line. I'm writing this from Poland, coming straight from 2 hours walk from work, catching Pokemon and leveling up on the way :).
It first launched in Australia, and is available in a few countries right now (Australia/New Zealand/USA). I believe the rollout to the UK/Asia/other countries is on hold due to issues with the huge volume of traffic overwhelming Niantic's servers.