3 ms·
I like Marco's proposed solution, because polling is an easily abstracted or generalized operation. Pooling app polling would save a tremendous amount of setup
by Terretta 16y ago
I like Marco's proposed solution, because polling is an easily abstracted or generalized operation. Pooling app polling would save a tremendous amount of setup and teardown time.
I also like his idea of iOS only allowing polling when signal is above a threshold. Data requests while in marginal coverage chew battery at an extraordinary rate. Changing my Fetch frequency on 3 mail accounts from 15 mins to 60 mins more than doubled battery life.
ReMail approached this by setting a timer to remind the user to launch the app and download mail to index. The data load for checking mail with arbitrary attachment sizes is considerably more than what Marco's talking about. I'd bet the data transfer problem is something Apple considered.
Even for small data sets, using data continually adds up. After getting their first data bill, users might prefer to be manually in charge of their data usage.
- pkulak 16y agoThat's really only a solution for his app. No way a chat app can work by polling randomly. Lots of things just need to keep a conection open.
- martythemaniak 16y agoWell, Marco has no solution - he has to lobby Apple to include APIs he needs for his app. His lobbying isn't going to improve his users' experience. I also can't port my app to the iPhone, as it would require me to lobby Apple to include APIs I need. I'm trying to illustrate how there is no perfect ideal approach.