|
Home > Archive > SQL Anywhere Mobile > April 2005 > which mobile device to use??
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
which mobile device to use??
|
|
| Joe Coady 2005-04-05, 8:06 pm |
| I am planning a simple prototype using ASA 9 (consolidated) and ASA 9
mobile with pocketbuilder 2. I am trying to determine what is the best
platform to use for the mobile device. I understand that iPAC or any
PocketPC with W2003 mobile would be acceptable.
The prototype app would be used by people to do remote audits / problem
recording and mobilink is going to be a big part of it. Does anyone have
any recommendation on what is the best mobile device I should go for
with respect to device, amount of memory, OS (Windows 2003 Mobile) or
anything else I should lean to. I want to use ASA9 and Pocketbuilder2.
TIA
Joe
| |
| Greg Fenton 2005-04-06, 7:02 am |
| Joe Coady wrote:
> Does anyone have
> any recommendation on what is the best mobile device I should go for
> with respect to device, amount of memory, OS (Windows 2003 Mobile) or
> anything else I should lean to. I want to use ASA9 and Pocketbuilder2.
>
As with most applications, the more horse power the device has the
better will be the *potential* for good performance. However, there are
many factors you need to take into account:
- cost
- availability
- type and speed of memory/storage card
- amount of data
- types of queries
- type of processing the application is going to be doing
- etc...
This is something that likely can't be tackled in the newsgroups. One
thing I will point out is that often handheld developers choose a
particular device to develop on only to find that a much better device
is available as they approach deployment or even that the device they
developed on have been discontinued (again, with newer devices replacing
them).
Hope this helps somewhat,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
| |
| Philippe Damerval 2005-04-06, 8:03 pm |
| Joe Coady wrote:
> I am planning a simple prototype using ASA 9 (consolidated) and ASA 9
> mobile with pocketbuilder 2. I am trying to determine what is the best
> platform to use for the mobile device. I understand that iPAC or any
> PocketPC with W2003 mobile would be acceptable.
>
> The prototype app would be used by people to do remote audits / problem
> recording and mobilink is going to be a big part of it. Does anyone have
> any recommendation on what is the best mobile device I should go for
> with respect to device, amount of memory, OS (Windows 2003 Mobile) or
> anything else I should lean to. I want to use ASA9 and Pocketbuilder2.
>
> TIA
> Joe
Joe,
I have done a lot of research on this very issue in the past few months.
Choosing the hardware is in my opinion the wrong approach, of course,
that was just for my case. Devices are coming out all the time. With a
smart device I found the only thing to think about was usability. THe
input made on devices needs to be kept to a minimum, as it is
inefficient to enter text in a device. The user needs to choose as many
things as possible from drop-downs, check or uncheck boxes or select
radio buttons. The conditions in which the entry is done are paramount.
For instance, you mention remote audits and problem recording. If this
is in a mechanical workshop for instance, dust and fumes are an issue.
The regular iPacs and Dell Axims are not meant to operate in the field.
They are strictly executive office tools designed to operate in a clean
environment like someone's desk or classroom. They are also not built to
be dropped from any kind of height. Couriers use devices to capture
signatures for instance, that are designed to withstand the shocks of
the road and can be dropped by careless handlers at any time.
Describe the environment in which your devices will be used and I will
be able to recommend a couple places to start.
Palm is a recommendable option in certain cases because the units are
less power-hungry and more flexible in certain ways than PocketPC's, and
for this reason I have found it a good idea to support both platforms,
which has oriented my choice of IDE to Crossfire.
--
Philippe Damerval
Alaska Dept. of Fish & Game
Commercial fisheries division
|
|
|
|
|