Mobile Carriers Cry "Less Operating Systems"
A NYTimes story says "Multiple systems have hampered the growth of new services, mobile phone executives say. " The story does a good job of capturing some of the changing dynamics in the mobile OS market — but rightly raises the point that given the sheer size of the mobile market, it's unlikely we're going to see the homogenization we have in the desktop market.
"FEWER" systems! "FEWER"!
I know they have trouble adding-up, but jeez...
Smokey, this is not 'Nam, this is bowling. There are rules.
- Symbian UIQ
- Symbian Series 60
- Symbian Series 60 v2.0
- Symbian Series 60 v2.2
- Symbian Series 60 v3.0
- Symbian Series 80
- Symbian Series 80 v2
- BREW 2.10
- BREW 3.12
- BREW 3.14
- Palm 5.4
- Palm 6
- WinCE 4 SP 2003
- WinCE 5 SP
- WinCE 5 PPC
- J2ME CLDC
- J2ME CDC
- J2ME JSR-184
- J2ME M3G
And that's just the ones that I can remember off the top of my head. Some of these are legacy builds, but there are still customers who want them. A large part of our product family is platform abstraction code; if you want to support multiple mobile platforms, you either bloat your code with abstractions, or drown it in #ifdefs. In either case, you have to write to the lowest common denominator, and avoid anything that's even remotely platform dependent, which does engender decent coding discipline but at the result of reducing productivity. That's mostly a C issue, but even J2ME isn't immune, particularly when you have to deal with extensions like OpenGL ES or M3G.If I never had to work in anything but (e.g.) J2MD CDC OpenGL ES or (gasps of outrage!) WinCE SP2005 again, I'd be a very happy bunny indeed.
If you were blocking sigs, you wouldn't have to read this.