3 ms·
It's because Apple's contract with developers was always a tightly limited execution context, sometimes things get added or taken away, but the shape is the sam
by toast0 6y ago
It's because Apple's contract with developers was always a tightly limited execution context, sometimes things get added or taken away, but the shape is the same. Background execution was originally forbidden and is now tightly regulated.
Android has moved from a mostly unrestricted environment to one that's pretty restrictive. Which means things have been taken away, and things that would have worked in gingerbread can't work today. And it's big things with reasonable use cases too: background exection and network access used to be pretty reliable (minus wifi tended to turn off with the screen), now it's not --- if Google push doesn't work, no notifications until the user starts the app or Google lets you run; you used to be able to use a usb camera from an app, now you can't with latest Android, so keep an old phone for inspection cameras.
I understand unfetered background execution is problematic, but it's also useful.