3 ms·

It's funny how he's even imagined implementing his own push server. Only because Android. On iOS people have already taken for granted that you must go through

It's funny how he's even imagined implementing his own push server. Only because Android. On iOS people have already taken for granted that you must go through APNS. Also, this is not just about push. The problem is that Apple and Google de facto own the edge user interface: phones.

swiley 6y ago
It doesn’t have to be this way. You can buy pine phones now and they actually work.
- oneplane 6y ago
  But does it work at scale and with the UX of the other platforms? If so: why hasn't it taken off yet? The technical part is not the hardest part; it's the "everything else".
  - swiley 6y ago
    Personally I don’t like the UX of other platforms at all so I don’t see why that’s a requirement. It hasn’t taken off yet because it’s only barely started shipping.
    - packetlost 6y ago
      One of my friends has one of these and says it's horribly unstable and the LTE usually doesn't work. I imagine there's still a lot of work to be done to make it usable for technical people, much less non-technical people.
- cocktailpeanuts 6y ago
  It doesn't have to be, but it is.
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.

swiley 6y ago

It doesn’t have to be this way. You can buy pine phones now and they actually work.

oneplane 6y ago
But does it work at scale and with the UX of the other platforms? If so: why hasn't it taken off yet? The technical part is not the hardest part; it's the "everything else".
- swiley 6y ago
  Personally I don’t like the UX of other platforms at all so I don’t see why that’s a requirement. It hasn’t taken off yet because it’s only barely started shipping.
  - packetlost 6y ago
    One of my friends has one of these and says it's horribly unstable and the LTE usually doesn't work. I imagine there's still a lot of work to be done to make it usable for technical people, much less non-technical people.
cocktailpeanuts 6y ago
It doesn't have to be, but it is.

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.