Category: Smartphone

The Microsoft Windows Mobile platform turns 10 years old next week (more on this topic next week). Mike Calligaro’s most recent blog item which bravely (Mike blogs about a lot of hot button topics on behalf of Microsoft) tries to explain Microsoft’s rationale for removing the ability to use ActiveSync over Ethernet (wired or wireless) reminded me of an interesting fact about Windows Mobile: It may be one of the few products that actually lost functions across a series of upgrades. Let’s take a look at just the features I can remember losing in no particular order (I don’t claim this is a comprehensive list. So, feel free to let me know about lost features I neglect to mention).

• ActiveSync over Ethernet
• Microsoft Access Database Importation
• Printing (with add-on driver)
• Microsoft Reader
• Creating a Media Player Playlist on the Device Itself
• Ability to Manually Disconnect from ActiveSync while connected over USB
• AvantGo Reader in firmware
• Menus at the bottom of the screen (replaced by two giant soft-buttons)
• Ability to add to Tasks on the device (Smartphone)
• Ability to encrypt Word or Excel documents/spreadsheets
• Backup entire device to PC using ActiveSync
• Pocket Money (add-on Microsoft application)
• Pocket Streets (add-on Microsoft application)

The Windows Mobile Pocket PC (perhaps soon to disappear in non-phone configurations based on sales declines) and Smartphone are still my mobile devices of choice. But, even with explanations from people like Microsoft’s Mike Calligaro about various design choices, it is difficult for an ordinary end-user like me to understand why I’m losing features and options (even software add-ons) which each new Windows Mobile generation of devices.

Google released a Java Midlet Gmail client for mobile devices today. So, of course, right off the bat it doesn’t work with my Dell Axim X50v (Windows Mobile 2003 2nd Edition) or T-Mobile SDA (Windows Mobile 5 Smartphone). My i-Mate K-JAM (Windows Mobile 5 Pocket PC Phone Edition) has a Java runtime, however. So, I was able to install and test it there. Couple of thoughts.

• The fonts look horrible on he 240×320 LCD. The fonts are small and jaggy (aliased).
• The scrollbar on the right is razor thin. I guess this is ok on a phone/smartphone device. But, it is difficult to grab with a stylus on a PDA type device. Of course, the navigation buttons work on a Pocket PC. So, I could use it instead of a stylus. But, when I am using a stylus, I don’t want to have to put it down just to scroll a page.
• Navigation through a threaded message list is fast. But the navigation is not as intuitive as it could be. Clicking on a thread item’s tab expands or collapses it. But, it is not immediately obvious.
• The menus look ok when my K-JAM is used in portrait mode but are truncated at the bottom when I’m using it in landscape mode (keyboard pulled out).

Google should go back to the drawing board for this one. They should also take a good look at the Yahoo! Mobile web interface. Yahoo’s mobile web interface is a relatively simple HTML one that seems to work with everything, is easy to understand, and look fine on pretty much any screen.

Microsoft’s Jason Langridge (AKA Mr. Mobile!) wrote an overview of the Windows Mobile Device Center (WMDC) that replaces ActiveSync in Windows Vista. He also provides a bunch of screenshots. So, head over to his blog to get the details.

Windows Mobile Device Center Overview

I use Microsoft’s Live.com as my default Internet Explorer 7 home page. Its tabbed page interface and hover over text expansion work great on my desktop and notebook PCs. The Mobile Live Beta is interesting but loses everything but the main page. Clicking More… just takes me to the current Windows Live mobile page which is a rehash of the MSN Mobile page. The Mobile Windows Live portal can be a great resource once they get more of the info from the desktop version and navigation that isn’t totally tied to a phone-centric interface (i.e., don’t forget the larger Pocket PC form factor).

The Official Google Blog noted that the Google Mobile relaunched last week with a new layout and simple access to Google’s mobile products. You can find it at…

http://mobile.google.com/

For some reason, though, Google Mobile thinks my T-Mobile SDA is a MiTAC Mio 8390. The Mio is an older (Windows Mobile 2003) flip-style smartphone while my SDA is a Windows Mobile 5 based non-flip phone. And, it still says that the Java-based Google Maps for Mobile doesn’t work on the SDA.