Re:FTC Issues Warning Letters to App Developers Using ‘Silve...
by baldajan on Sunday March 20, 2016 @12:32PM
(#11323513)
I've always been annoyed at hitting a few accept dialogue boxes with first launch apps on iOS. Kind of glad now that they exist.
[ Parent
| on HN ]
Re:FTC Issues Warning Letters to App Developers Using ‘Silve...
by ianlevesque on Sunday March 20, 2016 @12:51PM
(#11323577)
Yes, in hindsight (and I say this as a full-time app developer) Apple had exactly the right amount of trust for app developers - almost none. In the few instances where things didn't require approval (for example querying a URL scheme to allow for for crude inter-app communication), they were abused by even reputable developers like Twitter. Glad to see Google finally catching up with Android 6.
Re:FTC Issues Warning Letters to App Developers Using ‘Silve...
by icebraining on Sunday March 20, 2016 @01:11PM
(#11323663)
The J2ME/MIDP platform also had runtime permissions; for example, when I used Opera Mini on my Nokia S60, it would ask for permissions to write to the Downloads directory.
The MIDP security system probably had its flaws, but it seems weird that Android simply ignored it and went with an exclusive ask-on-install model.
Re:FTC Issues Warning Letters to App Developers Using ‘Silve...
by eropple on Sunday March 20, 2016 @04:58PM
(#11324624)
Agreed, but Android's made some pretty good strides on that front with Android 6.0. Just got it yesterday and, while a few apps were confusingly broken until I went digging (my audiobook app looking in a no-longer-extant path for the SD card, as apps get their own virtual storage path in 6.0), I'm pretty happy with the changes.
Re:FTC Issues Warning Letters to App Developers Using ‘Silve...
by ianlevesque on Sunday March 20, 2016 @01:58PM
(#11323871)
Sure does