07-11-2008, 07:00 PM
|
Executive Editor
Join Date: Aug 2006
Posts: 29,160
|
|
Is Windows Mobile Turning Into Palm OS From a Development Standpoint?
"A few years ago Palm was at the top of its game and had thousands of applications. But quickly developers started leaving and going to the more stable Windows Mobile. It had little to do with the operating system or zen of Palm or whatever. It had to do with the fact that the OS was becoming fragmented and becoming difficult to deal with as each device that came out broke this or that. You no longer were writing software for the Palm, but instead for the Palm Zire, or the III or whatnot. Each device had a custom PalmOS that required some custom coding for. Mostly due to HTC, Windows Mobile is slowly going that same way. In the past we could write to the Windows Mobile spec and mostly everything worked on any device. Now HTC is doing so much custom stuff and breaking so many things its ridiculous."
Alex Kac, head guru over at WebIS, raises some interesting points about the dangerous cliff that Windows Mobile is heading towards - or perhaps has already gone over if you ask Alex. Looking back to the first generation of Windows Mobile devices, you had three devices with 320 x 240 screens, no physical keyboards, and similar RAM/CPU configurations (although there was that whole MIPS/SH3/ARM thing). From a development standpoint, that's a about as easy as it gets. Remember though that Microsoft was criticized for being too strict in their requirements for the hardware, and many of us wanted to see more variation in the designs we were seeing. Boy did we get it! Fast-forward eight years, and we have a staggering array of devices with huge variations amongst screen resolutions, CPUs, RAM, and input methods. That's enough to give any developer a headache.
Has Windows Mobile gotten out of control in this regard? A platform isn't really much of a platform if, from a development perspective, you have to code for every variation of device. We don't really want to go back to the world of having only one choice of devices, do we? What should Microsoft do about this?
|
|
|
|
|
07-11-2008, 08:35 PM
|
Intellectual
Join Date: Jun 2005
Posts: 190
|
|
I'm not sure what they *can* do - heck, they can't do it for Windows! (play a PC game lately?)
But I do recall on the few Palm devices I had that as I advanced fewer and fewer things worked - different screens, etc ... and the same has been somewhat true with Pocket PC devices, though it got better when the processors converged ...
|
|
|
|
|
07-11-2008, 09:26 PM
|
Thinker
Join Date: Aug 2006
Posts: 378
|
|
Probably the root of the problem is that too much is left for device OEMs to implement with regards to Windows Mobile. Every time a new OS version comes out, we have to wait for the OEM to release their version of the OS specific for that device. That in itself is asking for big trouble due to a large part of development being pushed to manufacturers. Why is it that we cannot buy a CD containing a generic WM6 OS and flash to any WM-based device as long as it meets the system requirements (but we can buy a generic Vista DVD and install on most PCs)? It also seems there is no control for driver certification. In Windows, you have WHQL and you are supposedly guaranteed trouble-free operation as long as you stuck to the WHQL driver but I suspect none of these controls are in place for Windows Mobile.
|
|
|
|
|
07-11-2008, 10:48 PM
|
Thinker
Join Date: Aug 2006
Posts: 486
|
|
Quote:
Originally Posted by JesterMania
Probably the root of the problem is that too much is left for device OEMs to implement with regards to Windows Mobile.
|
That's actually the root that I'm talking about. The screen sizes, the different formats - I don't mind those. Its the fact that things break - Microsoft APIs break. One one device SMS APIs break. On another, MAPI APIs break. On another contact pictures are different formats.
So for me its the fact that OEMs have way too much control over drivers and quality.
|
|
|
|
|
07-11-2008, 11:20 PM
|
Executive Editor
Join Date: Aug 2006
Posts: 29,160
|
|
Quote:
Originally Posted by txa1265
I'm not sure what they *can* do - heck, they can't do it for Windows! (play a PC game lately?)
|
I don't quite follow - are you referring to certain games requiring a certain level of graphics performance? I don't know if that's the same thing: the game will install, and work, just not as smoothly as you'd hope. That's a different thing...or are you referring to something else?
|
|
|
|
|
07-11-2008, 11:30 PM
|
Intellectual
Join Date: Dec 2004
Posts: 150
|
|
Check out the folks over at Treo Central with their spanking-new Treo 800w phones...Most of the software out there isn't compatible with the 320x320 screen.
|
|
|
|
|
07-12-2008, 01:26 AM
|
Intellectual
Join Date: Aug 2006
Posts: 175
|
|
Well I think that MS should ask their OEM's to stop make lookalikes and start making WM devices.
The first devices, up untill WM2003 was 2:3 form factor screens with 4 hardware buttons and a 5 way navigation button underneath, and maybe a 5th button on the side for recordings or what ever. Then came the Blackberry wannabe era, where all new WM machines needed to have square screens and a small QWERTY keyboard underneath, and today they all have to be Iphone wannabe lookalikes.
The added hardware keyboards are not the issue for programers, but the many layouts of hardware buttons and lack of them, plus non programable ones is a big issue, as is the many form factors of the screens (QVGA, WQVGA, VGA, WVGA, Square, Rectangular........) and different graphics accelerators.
Let's figure out what a WM PDA should look like, and stick to it, you can still make lots of variations to the design, even if there is only one type of screen (please let it be VGA) and one button layout (the old one please, maybe with the Record button replaced by a scroll wheel). But that would leave the Smartphones out and require going back to two versions of WM, and we can't do that now, can we :?
On the other hand, we could ask: Is there a problem for WM, or is it Apple who are walking the Plam line now?
Palm designed both hard and software, and decided what went where, making the Palm Pilots work so flawless, which was why they had that edge over WM for a long time (4 years is a looong time in hight tech business), isn't that exactly what Apple is doing now? We decides what is good for you, and what you need, if you want to have a say about it, go somewhere else????
|
|
|
|
|
07-12-2008, 02:11 AM
|
Intellectual
Join Date: Dec 2004
Posts: 194
|
|
I think we should remember that MS and Apple are selling a different products. MS are selling a platform for OEMs to build their mobile "Smart-phone" on top of their platform as a base layer, while Apple are selling a phone to end-users - the regular consumers, without trying to offer it as a solution to OEMs.
To continue selling the Windows Mobile platform to OEM companies MS have to keep the platform flexibility and allow OEMs to implement this level of customization with their devices and probably even more. If all Windows Mobile devices will be the same and will be shipped with the exact similar content then there isn't any need for such competition model between the different OEMs as they will all be forced to ship the exact same phone.
MS business model in this case is structured on the fact that they generate a complete market relying on their platform of different OEM companies that also compete between them on different implementation of MS OS - just think about the great position that such structure puts MS in!
I doubt it if the third-party applications market actually include more than 5% or so of all of Windows Mobile users since most of WM users simply buy a device to use the built in features that arrive with the device. This means that when HTC adds a new weather solution with their device they are offering a completely new feature that other companies doesn't have on their device (with the understanding that most users aren't familiar with the existence of third-party application option for their mobile device or they simply won't know how to install it).
Since I believe the third party applications market is relatively small from the large MS eyes, I don't think that the fact that there are lots of different variations for Windows Mobile devices is effecting MS too much, nor the majority of the Windows Mobile users.
Due to the difference in the models and target market between MS and Apple I don't think that we will see any changes soon since both companies simply have a different path in their hand and the only question is simply when one of MS OEMs will be able to produce something that will run on WM that will offer a better mobile solution from what Apple are offering at this stage.
Cheers!
|
|
|
|
|
07-12-2008, 07:54 PM
|
Theorist
Join Date: Aug 2006
Posts: 300
|
|
I don't blame HTC at all for "breaking" WinMo. I just recently bought a Touch Diamond, and (after updating the ROM to 1.37.456.2), it's an amazing device. My only complaint, in fact, is that the ugly, difficult and annoying Windows Mobile 6.1 interface is not more completely hidden. Every time I drop from TouchFlo 3D into Windows (to answer an email, or change my alarm, etc), it's a reminder of the ugly beast that still lurks beneath the slick, fast, and finger-friendly interface that HTC grafted on top of it.
However, since it's not really ideal having a great interface that isn't used for any programs I install, the solution is simple:
Microsoft needs to completely re-think, re-design and re-create the GUI for Windows Mobile. Not just another point-release, not yet another evolutionary change.
Far too many functions have been added to Windows Mobile devices since my Cassiopeia E-11, and my iPaq 3650 (the original Pocket PC shell) to be easily accessible thru that interface. My Diamond has a phone, sms, MMS, email, instant-messaging client, GPS, multiple network settings (3G, EDGE, WiFI, Bluetooth, etc), mobile versions of office apps, pocket Outlook for contacts and calendar...
That requires a different kind of interface. All I can say is, Microsoft better have *something* that seriously learns, and adopts where appropriate, from the iPhone, which has a very fluid and intuitive (but not perfect) user interface.
Having so many functions is pointless if they're difficult for people to get to, to change, and to configure, and Windows Mobile - even 6.1, which my Diamond has - looks not much different than my very first iPaq did back in 2000.
Windows Mobile 7 needs to provide the kind of interface natively that HTC and other companies - Samsung, etc - are being forced to put on top of WM 6.x. If Microsoft's UI was compelling, simple, attractive, and flexible (not an easy thing I know, but ****, they have BILLIONS to invest in this ), then HTC and others would not be forced to hide the beast under a pretty custom interface.
That's my 2 cents. I really like TouchFlo 3D, since at least *somebody* is trying to improve the user experience, and it sure as heck doesn't seem to be Microsoft lately. Maybe they should buy HTC, and learn a bit about aesthetics.
__________________
Casio Z7000 >> Ipaq 3650 >> Viewsonic V36 >> Ipaq 1915
Dumb phones >> Axia A108 >> HTC StrTrk >> Touch Diamond
blog.HackingBangkok.com
|
|
|
|
|
07-13-2008, 12:46 AM
|
Intellectual
Join Date: Jul 2003
Posts: 125
|
|
Is it MS or is it the Carriers?
I agree with the basic argument that WM is just too far behind to catch up with the iPhone's GUI and that it needs to be completely made over. BUT I think we are forgetting the power the carriers wield. They have kept 3rd party apps off cell phones, pretty much stopping the development community. Apple changed the rules of the game and they drove the party not AT&T. So it seems to me that MS needs to sit down with Verizon and Sprint and T-Mobile and say "What are we doing guys? What is our answer to the iPhone? It better not follow the same history as the iPOD or we are toast. We did a fairly good job with the Zune. Why can't we do that with a phone?"
|
|
|
|
|
|
|