No this is not a mistake. It is not supposed to be 2022, and this is not a futuristic post about how mobile development will look a few years from now. It is about how we developed applications back then, in 2002. I found this magazine in a pile of old papers I was about to throw to the recycling bin, and suddenly it hit me – I wrote this piece on how to develop mobile apps more than 13 years ago! So it is a visit down nostalgia lane, bringing long forgotten memories from what seems to be now a tons of technological generations ago. Continue reading
This is indeed an interesting question. The article Ultimate Mobile OS Showdown: iPhone vs Android vs webOs vs Blackberry vs Windows Mobile vs Symbian tries to compare the good and bad of each of the common mobile OS at hand today.WorldMate is mentioned in this article as one of the better BlackBerry OS third-part apps for tracking travel plans.
Personally, I like the Windows Mobile OS, but I have to agree this is probably a dying mobile OS.
iPhone is very chick but if I have to gamble on a winner it will be the Android. Its openness and support from a plethora of vendors will make it the winner, eventually.
What do you think?
It is no secret that I work in one of the most experienced Windows Mobile development ISV company. Lately we were wondering about the future of Windows Mobile. Traditionally, we developed Windows Mobile applications in C++ (for the Pocket PC platform). We used MFC throughout Windows Mobile 2000, 2002, 2003, 5.0. For the Smartphone platform we plunged right into .Net Compact Framework.
While working on our latest Windows Mobile 5.0 products, we suddenly encountered some MFC changes that broke backward compatibility. We also seen the effort put in by Microsoft to promote .Net in general and for mobile development in particular.
Fears begun creeping in: will MFC future is doomed? Will we still have Win32 API’s in future Windows Mobile releases? What will the Pocket PC and Smartphone unification bring for developers?
We are now faced with decisions regarding our future Windows Mobile development technology. Basically we can:
- Stay with MFC and face its fate bravely.
- Move to Win32 APIs (or create our wrappers around it).
- Switch to .Net CF (and suffer the performance penalty and the hardships of doing non standard “things” with it).
What do you think?