zlacker

>>skille+(OP)
I feel like the elephant in the room is that there's no phone battery that's going to stay useful in anywhere close to that time frame, and replacing phone batteries is usually a losing proposition. I've tried, several times. Fake, low-quality batteries are rampant (usually degrading within weeks), and genuine ones are prohibitively expensive -- usually a significant fraction of the cost of a new phone.

>>wheels+B7
Even if properly replacing the battery costs 2/3rds of a new phone, I'd be happy to pay that a couple times over its lifetime to squeeze extra years out of it and reduce how often I have to go through the gruelling process of successfully migrating everything over to a new phone (it's a real pain for those who prefer to avoid forking your data over to Google, which I gather is required by the built-in options like cloud backups and D2D transfer).

>>rkager+3y
> gruelling process of successfully migrating

I hate this. Why do I have to relogin to every app on a new phone? Why are some apps missing after every migration? Why do some apps just randomly lose all config and settings and force you to set them up again?

I want Google/Apple to force app devs to make backup and restore seamless. Like, if I am halfway through typing this comment on HN and then lightning fries my phone, when I restore to a new phone I want the exact same chrome tabs open with the same half-written comment. I don't want to have to battle to re-pair my printer or watch. I don't want stupid cookie warnings on every website again. I don't want to have to retrain every single fingerprint. I don't want to yet again opt out of data collection. I don't want to re-accept the same T&C's for photo backup I already agreed to last year, and the year before, and 10 years before that.

Please... just make migration work the way it should have always worked.

>>london+vB
On the other hand, I'd preferentially have the cloud backend have exactly zero of that information. I'd be worried about privacy getting deprioritized in favor of the above.

>>sho_hn+XF
Easy enough to encrypt with your password so the backend has the info but can't 'see' it.

Google already does this optionally for Chrome synced data.