I had a couple of PalmOS devices back 20 years ago. I think my last one was a Sony CLIÉ. WiFi, this newfangled thing called Bluetooth that I could use to transfer files to the Nobody Else I Knew Who Had Bluetooth, digital camera (it wasn't too bad for the time), MP3 player, and a Memory Stick Pro slot for removable storage for all those MP3s and pictures. It had this beautifully tactile selector dial on the side. You could roll it with your thumb to move menu selections up and down, then press it in to click. Oh, it was so good.
I switched to PocketPC/Windows Mobile shortly after that, though. Dell Axim, IIRC. The screens were nicer. They had CF card slots for removable storage and peripheral devices. The WiFi wasn't as flaky and it even had a basic 3D graphics accelerator. I could program for it in C#, and it was very easy, no more difficult than programming on desktop. Actually, I experimented for a while with writing apps that ran on both desktop Windows and Windows Mobile and it was quite a fascinating experience.
That was a problem with PalmOS. If you wanted to develop for them, you either got stuck using J2ME (which was hot garbage), or you had to pay to get access to a C compiler. PocketPC and .NET Micro Framework were significantly much lower barrier to entry. Completely unlike trying to figure out Android development today. I think that's why I never really bothered to learn Android development. I've never really had an impetus to push me to chug through the learning curve, plus I already knew it didn't have to be that stupid. I've rathered stick to webdev and make whatever I need as mobile responsive PWAs.
I look at my smartphone today and it has never felt as good as that CLIÉ or Axim.
Actually an appropriate gcc target didn't exist at the beginning. Initially there was only Codewarrior, which was commercial. There was not even an emulator. That came from the open-source side and was embraced by Palm.
However J2ME was not really an option. By the point Java existed, gcc prc-tools already did.
The whole j2me toolchain was pretty rough too. For a while when i started i used DOS history to get through it. then my life changed when my prof told me what a batch file was for. ( There werr four commands you had to run in sequence anytime you wanted to test your code )
Programming on j2me was like 7x better after that...
I switched to PocketPC/Windows Mobile shortly after that, though. Dell Axim, IIRC. The screens were nicer. They had CF card slots for removable storage and peripheral devices. The WiFi wasn't as flaky and it even had a basic 3D graphics accelerator. I could program for it in C#, and it was very easy, no more difficult than programming on desktop. Actually, I experimented for a while with writing apps that ran on both desktop Windows and Windows Mobile and it was quite a fascinating experience.
That was a problem with PalmOS. If you wanted to develop for them, you either got stuck using J2ME (which was hot garbage), or you had to pay to get access to a C compiler. PocketPC and .NET Micro Framework were significantly much lower barrier to entry. Completely unlike trying to figure out Android development today. I think that's why I never really bothered to learn Android development. I've never really had an impetus to push me to chug through the learning curve, plus I already knew it didn't have to be that stupid. I've rathered stick to webdev and make whatever I need as mobile responsive PWAs.
I look at my smartphone today and it has never felt as good as that CLIÉ or Axim.