Ultra Mobile PC's (UMPC's)

Well everyone knows all about the over hyped evil Origami PR and marketing campaign. And no I am not going to talk about that. All I will say is next time don't over hype things, it just leads to disappointment and extremely high expectations from users which have no foundation! What I am going to talk about here are a few potential issues that we should be considering with battery, CPU and screen limited devices such as the UMPC.

The issues that will arise with Ultra Mobile PC's (UMPC's) that will need to be addressed are very similar in many senses to the Windows Mobile and Windows CE devices. But it works on XP I hear you say! Well actually that is a benefit! However there are still issues that XP doesn't think about in it's underlying platform. Firstly it was never really designed for low powered systems and as such doesn't mange it's power as efficiently as Windows CE. So why did Microsoft choose it... Well I can only speculate that it makes the platform more accessible to the standard applications developer and cut down the time to market for getting the basic features needed for a quick uptake on the device. Maybe someone from Microsoft could confirm this or update us on these details.

The issues with screen size, orientation and real-estate have always been some of the key HCI issues with PPC and Windows Mobile devices and I for one know that there are resources out there to guide the standard developer to design usable interfaces for such devices. One thing I want to remind the devs is that dockable controls are very clever and if you use them then you should hopefully not have to re-design interfaces for the smaller screen. Keep things simple for the user. The input methods are important to the user... they don't like to spend a long time inputting data so make it easy for your users... give them the options of keyboard or the on screen input but minimise actual input where you can!

With the UMPC think about memory, power and CPU utilisation. it is good development practice at the end of the day. If developers at the moment start thinking about power utilisation with this device and maybe even with laptops when doing their development work then they may actually find that they can use the device for longer. I for one know that my laptop only has a set amount of power on battery and really it is not usable for prolonged time periods. Bear this in mind, you don't want to lose data at the end of the day!!!

Something I have to say at this point is that the above are only my personal guidelines (ie I have put these up here for me so that I remember that when I do get to design for this sort of device I remember these key facts!) and that I don't yet have one of these funky new devices to play with and find out the full limitations of them. If I did have one who knows what other useful things i could find out and advise on. :)

posted @ Thursday, March 09, 2006 11:18 PM

Print

Comments on this entry:

# re: Ultra Mobile PC's (UMPC's)

Left by Anonymous Programmer at 3/10/2006 12:15 AM
Gravatar
* Battery life: too short to be useful (3 hours)
* Weight: too heavy to be truly portable (2lbs)
* Size: too big to fit in your pocket (7")
* Price: too expensive for Joe Public

# re: Ultra Mobile PC's (UMPC's)

Left by Mike Dimmick at 3/10/2006 6:53 AM
Gravatar
I have two words for any programmer: DON'T POLL. Never ever poll for changes if you can possibly wait for a notification. Polling - sitting in a loop checking for changes to some resource - prevents the processor going into power-saving modes, keeps pages of program code and presumably data too in physical memory, and can often keep the disks spinning when not necessary.

Yesterday a colleague killed off Pamela, the Skype answerphone tool, on our boss's laptop because the fan was constantly running and the Pamela process was using all the CPU resources. We're not sure if this was an error condition or just how the software works.

For file system changes under .NET you can use the FileSystemWatcher class. In unmanaged code you can use FindFirstChangeNotification or ReadDirectoryChangesW (on desktop Windows, not available on CE). For registry changes, see RegNotifyChangeKeyValue (not on CE).

The more CPU resources you use, the lower your battery life will be. On mobile devices, fast-running code is often better battery life; try to be efficient.

# re: Ultra Mobile PC's (UMPC's)

Left by Lorin at 6/14/2006 8:42 AM
Gravatar
I just picked up the machine that Origami should have been a week and a half ago. It's got a 4.5" screen with insane resolution - 1024x600. It actually fits in the pocket of some of my pairs of jeans. Pretty snugly, but it does. But it was twice the price of the current Origami systems, so out of the reach of some folks. It's the Sony UX50. The perfect go-anywhere machine. I wish it had more than just a half gig of RAM, and better than just 2 hours battery life, but still all things considered for me it's the perfect portable. Right now only available in Japan, but it will hit the states next month. More info:

http://geekswithblogs.net/lorint/archive/2006/06/10/81423.aspx

If you're at TechEd this week then go see it in person at the community booth. Scott Cate has it for the week over there.

Your comment:



 (will not be displayed)


 
 
 
Please add 1 and 8 and type the answer here:
 

Live Comment Preview:

 
«November»
SunMonTueWedThuFriSat
2627282930311
2345678
9101112131415
16171819202122
23242526272829
30123456