Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To be honest, Google takes care of all the complexity to have apps updated on Android. It's even better, because you can do a stage rollout really easily (i.e. just deploy to 10% of users, then 20%, then 50%, etc.). It's possible to do on a web app but you'll have to do it manually.

You still have to push the apk and stay alert for the feedback, but you have to be careful with web apps update too anyway.

I'm not sure about Apple because it appears the auto-update process is not that smooth and people don't upgrade their app as often as Android users.



Auto-updates are great except in the rare cases where they aren't at all. Picking up my phone in the morning to recognize that it lost half its battery in the night due an extensive auto update and being left in the cold with a 10% battery (instead of 60%) isn't that great.

Beside that I think virmundi above has his points, and I agree with him. App updates are not instantaneous.


As of iOS 8, apps will only update automatically when the phone is plugged in to charge and connected to WiFi.


i think the default setting for new android releases is only update on wifi and plugged in.


I looked, and you can tell it to only update when on wifi, but the Play Store has no setting that I could find to only update when plugged in.


> I'm not sure about Apple because it appears the auto-update process is not that smooth and people don't upgrade their app as often as Android users.

The auto-update process on iOS is basically the same as recent versions of Android: check a box for completely automatic background updates or see a notification with the available update count and an “Update everything” button. The main difference is for things like games which hit the legacy 100MB cellular transfer limit which Apple added back when AT&T had grossly underprovisioned their network.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: