palmos

Smartphone OSes at the time were PalmOS and a version of PocketPC with phone capabilities retrofitted on.

Android, Windows Mobile and PalmOS users have been doing fine with having the option of installing their own software.

The most successful one before was for the PalmOS and it wasn't over the air.

I think it's a lot closer to the PalmOS cards functionality, which a lot of people really enjoyed.

The recent disabling of TLS1.0 on so many sites means I'm finally going to have to upgrade my cell-phone, as there aren't any TLS1.1+ supported browsers for PalmOS.

PalmOS made it a point to separate the executable and it's data, in the form of a database file that could be easily backed up.

If it hasn't been necessary for PalmOS previous and it's damn clear that desktop operating systems don't work this why, why do phones have to?

I do wonder why they decided to close their app distribution, I enjoyed the little bit of PalmOS development I've done.

Is it just me, or wasn't this sort of quick point and shoot data transfer extremely common back in the days of PalmOS, thanks to IrDA?

The way this worked on PalmOS was completely sane.

I was particularly fond of the onboard programming environments for PalmOS.

Isn't that the same case as Windows, BeOS, Android, iOS, PalmOS, etc?...

I got it two years ago - I had various PalmOS products ("instant on") before that.

In my drawers, I still have all of my Handspring/Palm "smartphones", I used almost all their PalmOS lineup during the naughties: * Handspring Visor+Visorphone (2002): huge!

I agree that this whole process seems completely broken from jwz's perspective, but it's hard to say that Palm had people "who did it right in the PalmOS years" when they never got it right in the category that matters: number of app sales.