Palm vs Ipaq

[EagleKeeper]

Currently have a program that is running on a Windows laptop. Battery Life is lousy (old lappy).

Custom written application uses RS232 to interface with field devices (one at a time). Samll amounts of data is transfered between laptop and unit. Program is Windows based (for convience) but is equivalent to an almost text app that would be menu selectable.

Client is thinking about replacing the laptop with some handhelds. Easier on the field techs and battery life is longer. Handhelds should be cheaper than even low end lappys from Dell.


Question based on your experience is:

Which handheld should I look at.

The Unit:
1) will require a SDK that I can run from my development PC.
2) should not require me to use Java (weak in it).
3) should be able to easily communicate with the PC for downloading & testing the application.
4) does not need sound at all and graphics can be optional.

 

[DaveSimmons]

Less of a learning curve to stick with WinCE's win32 API or even C#/.Net and you can get high-capacity batteries for at least some PocketPCs (like my Axim X3i).

One problem might be RS232 since all PDAs now use USB and wifi, but I assume you can get CF cards (or SDIO?) from someone like Socket to fix that. That narrows the price gap a bit though if it's $100 per CF card.

I'd lean towards CE / PocketPC but I'm a Windows app developer so it seems like a lot less work than learning the CodeWarrior IDE and a new API.