4 ms·
It isn't of course, Nokia smartphones from that period had colour screens and ran Symbian. They had 3G, Video calling, MP3/Video playback, fairly okay web brows
by ollie87 7y ago
It isn't of course, Nokia smartphones from that period had colour screens and ran Symbian. They had 3G, Video calling, MP3/Video playback, fairly okay web browsers (I used to use Opera), and okay-ish photo/video capabilities. You could even edit documents on them if you hated yourself that much.
They just lacked CPU power and RAM capacity compared to what came when the iPhone launched.
Models would be:
6600
6630
6680
N70
N73
I actually had another Symbian powered Smartphone when the iPhone launched, the Motorola Rizr Z8 which made the Nokia powered Symbian's at the time look really slow. I sort of miss that phone and it's form-factor, it even came with a pair of Stereo Bluetooth Headphones. Massively ahead of it's time, of course not as slick as the iPhone and AirPod combo I have now, but great in it's own way.
- vardump 7y ago> It isn't of course, Nokia smartphones from that period had colour screens and ran Symbian. They had 3G, Video calling, MP3/Video playback, fairly okay web browsers (I used to use Opera), and okay-ish photo/video capabilities. You could even edit documents on them if you hated yourself that much. Those Symbian S60 Nokia phones you listed could install and run apps written in "C++". Emphasis on those quotes! But regardless, your very own native code, doing your bidding. Been there, done that. It worked, but writing those apps was very tedious and hard. Everything was async to save power. No standard libraries, etc. I'm very happy there's no need for "leave stack" and "cleanup stack" etc. in the modern world. But damn, that architecture was really helping the battery to last for a long time. Your code simply would not be running until some async thing did a callback.
- Scoundreller 7y agoDon't forget native SIP!