A Question of Which Mobile Device for your Mobile Application?

Ok, so your thinking about a mobile device, but not sure where to start in relation to what configuration of mobile device is required.

Well, (in my view) at the very least, 'Handhelds' or 'Smartphones' selection requires some very basic but important questions to be addressed before digging into all the small print of those long lists of specifications, features and functions. In other words, know your application before getting down and dirty with someone else’s application deployment platform.


The Question of Keypads:

Keypads (for manual data entry i.e. Asset Descriptions etc...) can be full 'Qwerty', 'Alpha Only', 'Numeric Only' (mobile phone style) and this can redefine the cost, deciding which keypad for the application is a key factor (if required ... may not be required where the application is solely scanning barcodes and / or using a touch screen with onscreen keypad). I would normally suggest, that you look to the data you wish to capture and based on that data, choose the best keypad configuration.

Which keypad is required for your application? (if pre-defined)


The Question of Data Exchange:

The data from a back office application and / or data from the mobile device, can be exchanged in either 'Real Time' or 'Batch'. 'Real Time' technologies requires a direct connection to a back office shared resource (Application, Drive or Printer etc...), this would normally be for example a 'Wireless Network' (WLAN) connection. Where as 'Batch' technologies requires only a scheduled / un-scheduled periodic connection to a back office resource, this would normally be for example a 'Cradle / Docking Station' connection. I would normally suggest, that even in a wireless network, keep in mind that connections can still be lost or you may move in and out of range, so 'Batch' would normally always form a key part of data exchange.

Which Data Exchange technologies is required for your application? (if pre-defined)


The Question of Screen Size, Dimensions and Resolution via Data Capture Requirements:

While software developers may suggest what should be the best screen layout for an application and should always seek to maximize the ease of use and to minimize the data capture inputs required by the user, there are always a refined minimum amount of data that must be captured. This minimum amount of data to be captured, can be matched to the most practical screen size, dimensions and resolution available or can be presented using a pre-defined visual minimal requirement. When selected a handheld or smartphone, keep in mind, that in general, a Smartphone will on average have the smallest visual viewable area, with PDA and EDA often having double the capability to display data inputs. The bonus of EDA's is that often they are the best choice (including their touch screen) where you require a more robust unit then PDA and EDA may also include a Barcode scanner, GSM etc...

What Size, Dimensions or Resolution do you require? (if pre-defined)

What Data is to be Captured as a requirement of your application? (if Size is not pre-defined)


The Question of Touch Screen:

Some enterprises may have a set of predefined equipment already in operation which they would like to deploy their new application too, this equipment may include windows mobile smart phones. These smart phones are normally tided via contract to a Telco service provider and utilise a pre-defined spec to match pre-existing mobile office requirements. Some times these devices do not include (or require) touch screens and / or stylus pens.

However, the added simplicity or flexibility of touch screen may be a requirement of a new software application and may force the new device into play and add additional requirements for pre-existing applications which must sit along side your new application (with or without touch screen). Touch screen may also allow the users to scroll quickly and simply through long lists, or make multiple selections and move between on screen items without requiring a large number of keypad depressions, where as, the pre-existing application may only be operated using key depressions, so an onscreen touch keypad or slide out hardware keypad will also be required.

Is touch screen, as requirement of your application? (if pre-defined)

Armed with the above answers, you should now your ready to dig a little deeper and hopefully refine the large number of mobile devices down to a few application ready devices.