Mobile Application Development - Focus on the Browser

I came across this article today by Carl Weinschenk on the challenges of selecting the right mobile OS and hardware platform for application development. The problem is many companies have users in all camps. This is a common issue, that all mobile application developers must ponder.

***********************************************
http://mobileenterprisestrategies.blogspot.com
***********************************************

54 Questions to Help You Select the Right Mobile Handheld Computer

Mobile computing requires mobile computers. Which brands and models you select can be a hard decision. The following list of questions are designed to help you think through some of the big issues that will enable you to narrow down the selection list.

The first big question you should answer is what is the primary purpose of the handheld or mobile device. Is it barcode scanning, GPS, RFID, surveying, map reading, voice calls, email, digital signatures or field data collection?

The second big question is what is the environment that the device will be used in. Is it used in the office, clinic, warehouse, cold storage or out in the rain on a construction site.

There are a large number of very good handheld computers, PDAs, Tablet PCs, laptops and Smart Phones to select from, however, the key to getting the right mobile device is to research the business purposes and the environment in which the solution will be used before making a selection. The following questions should help you narrow down your list of mobile handheld computers:

1. What environment will you be working in - is it hot, cold, wet or dusty?
2. How rugged do you need your device? There is a ruggedness scale.
3. Are there explosive vapors or explosive powders?
4. Is it a clean office environment, or a muddy and rugged outdoors environment?
5. Is the user in and out of vehicles all day?
6. Is your software application focused exclusively on bar code scanning, RFID reading, GPS, or do you need a multi-purpose data collection device?
7. Will the hardware configuration ever need to be changed? Some handhelds can be configured at will; others are locked and can only be used with the original configuration.
8. Will the device be used as a primary phone, or is it focused on data collection?
9. What hardware requirements does your mobile application require?
10. Will the battery last long enough to complete your daily work between charges? Do you need back-up batteries? Can you use batteries purchased at the local market, or are they vendor specific?
11. What is your budget? What does the value of using a handheld computer justify spending?
12. Do you have enough budget to purchase or develop the mobile software and hardware you need? Does your budget only allow for low cost consumer devices?
13. How many replacements(of a consumer device) does it take to equal the cost of a ruggedized handheld?
14. How do you replace broken devices? Can you get a replacement service in 24 hours, or must you wait a week?
15. What kind of support contracts and warranties are available?
16. How long will your new handheld computer be supported, serviced and manufactured by the vendor? Is it near end of life and being discounted for a reason?
17. Can you upgrade the operating system when Microsoft releases a new version of their mobile operating system?
18. Can you use standard laptop data cards in the handheld, or do you need to pay for high priced vendor specific cards?
19. Can you view the screen effectively in the sunlight?
20. Can you add more memory if your requirements increase?
21. A few industrial handheld computers have flashlights built into the device to provide better light for taking digital photos. Is this useful?
22. Do you require GPS? If so, how accurate?
23. Will your users be wearing gloves? If so, small keyboard buttons won't work. How big of keys do you need?
24. Do you need a water proof, or just water resistant case for your handheld?
25. Does the bar code scanner work effectively in real-world environment? Some scanners cannot scan effectively through glass or plastic.
26. Is the size and weight of the handheld appropriate for the user and environment?
27. Can your handheld computer support all the add-ons you require at the same time? Some devices can only support a specific number of add-on components so you are forced to choose. Some cannot support both a GPS and a data card at the same time. Some devices cannot support both a bar code scanner and a GPS add-on. This is an important consideration.
28. Do you need only a touch screen and navigation pad, a number pad or a full QWERTY keyboard? This is very important for user acceptance.
29. Is the handheld device also going to be used as a phone? Is a 2 pound industrial grade handheld really a usable phone?
30. Does your low cost consumer grade PDA need a rugged case like the ones Otterbox sells?
    If you only have a budget for a low cost device, does it support the battery life and add-on components you require?
31. How will the device be transported around a job site? Will it strap to a belt, swing from a shoulder strap, sit in a holster or be mounted to the dashboard of your truck? Does your device support your chosen method?
32. Where is the closest inventory of extra handheld computers? Where is the closest repair depot?
33. Will your vendor loan you a device on trial?
34. Can you rent the handheld if you only need it for a short-term project?
35. Does your vendor take trade-ins on your old handheld computers?
36. Can you get the same exact handheld, under a different brand name for less?
37. How will your handheld computer send data back to the office? Cradle sync, WiFi, bluetooth, wireless data card, GPRS/GSM, CDMA?
38. What size screen do you need? Some devices like the Jett-Eye have a "landscape view" others a "portrait view" many have different sized screens. What do you require?
39. Do you need an integrated digital camera? Do you need a low or high resolution camera and does your device support it?
40. Does a refurbished device from Ryzex make better sense that a new device?
41. Where is your vendor's office? Are they in the neighborhood or on the other side of the planet? Does their location offer you the support and attention you deserve?
42. Does your handheld computer run on the same operating system that your mobile software solutions requires? I have had customers order Windows CE devices for their Windows Mobile application. It did not work.
43. Is your device likely to be stolen? If so, you may want to use cheap devices that can be easily secured and replaced. We have implemented projects in Africa where this was an issue for the buyer.
44. Does your handheld computer come with a pistol grip or other straps that help you avoid dropping it?
45. Can you comfortably hold the device in your handheld and complete your work? Some devices have scanners on the side, on the end or underneath.
46. Can you effectively view the data you need? Some jobs simply require a full keyboard and a full screen for viewing large CAD files or Maps. Does your screen size match your requirements?
47. Where will you store the device when you use the washroom? One of my customers used Tablet PCs and they kept breaking when they slipped off of the sinks in the bathrooms.
48. Does the mobile device you select support the RFID reader you need for distance and accuracy?
49. Does the battery in the mobile handheld last long enough after you have added on all the additional hardware accessories? Each added radio uses more energy.
50. If you have dozens of handheld computers, how will you charge them all at the same time? Do you have a docking station that allows for all of your devices to both charge and synchronize at the same time?
51. Do you need wireless data plans, or does batch synchronziation after each shift work?
52. What wireless carrier and data plan provides the best service and cost for you? Does that wireless carrier support your mobile device?
53. Does the wireless carrier have sufficient coverage for your workers?
54. What is your budget for each handheld computer? This may limit your selection and make the choice simpler.

I don't sell or represent any mobile hardware. I have just managed many mobile application development projects around the world so have learned some lessons. If you would like to discuss this topic in more detail please contact me.

***********************************************
http://mobileenterprisestrategies.blogspot.com/
***********************************************

Mobile Inspection Application ROIs

A few years ago I worked with a state agency on a very interesting mobile application development project. The agency was responsible for inspecting pharmacies and other locations that handled drugs and narcotics. In order to perform their tasks, they were required to drive into the main office, rummage through paper files, remove these paper files and load them into a box to take with them to the inspection sites. They would use a carriage with wheels to transport this box to their automobiles. Let's pause a moment to think of the costs and inefficiencies of these task. They would do the following:

• Drive to the main office where previous inspection documents are stored
• Sort through file cabinets for earlier inspection results
• Read through these files to determine any previous non-compliance or failed inspection issues
• Record these issues and highlight them for review at the site
• Load these files into a box and carry out to their vehicles
• Re-inspect the site and record more information on new forms
• Drive back to the office
• Carry boxes of paper files back upstairs
• Refile all old files
• Re-type the collected data into the database application in the office
• Add new paper forms to the files
• Carry back to the main office

Once the mobile application was designed, developed and deployed -a simple database synchronization with a handheld computer, laptop or Tablet PC from the field completed most of these tasks in seconds.

I was also involved in a mobile project in the UK. This project was similar in that hundreds of service technicians would drive to the central office each morning to pick-up their list of work orders or service tickets. Once the orders were completed, or it was near the end of their work day, they would all drive back to the office to turn their work order forms back into the central office.

The time, fuel and opportunity costs of this hugely expensive routine was enormous. The ROI from dispatching work orders to mobile handheld computers would have been recognized in a matter of weeks.

Think about it, 300 service technicians wasting 1 hour per day driving back and forth to the office, plus fuel, vehicle maintenance and lost billable service time.

1. 300 service technicians wasting 1 hour travelling back and forth multiplied by $25/hour is replaced by dispatching and synchronizing data to a handheld computer. This enables each service technician to save a travel hour and replace it by completing an additional work order for an additional amount of $22,500 USD/day
2. Save 300 gallons of wasted fuel per day multiplied by $2.69 USD/gallon = $807/day
3. Save some unknown amount of vehicle maintenance costs
4. More efficient work enables the company to reduce labor costs by 10% or $6,000 per day.

If you could be dispatching work orders directly to the service technicians' mobile handhelds, saving fuel, saving travel time, and getting an additional work order completed each day, you would be able to complete the same amount of work with less service technicians. Let's say you could reduce your staff by 10% and still bill the same amount of work (save $6,000 USD per day on labor costs).

The savings and profits on this project alone were close to $30,000/day. If the mobile application development project was $150,000, and the mobile devices each cost $1,000 each, plus a monthly data plan of $75 each you would invest around $450,000. However, the ROI would be recognized in less than 1 month. The bigger the number of mobile service technicians and vehicles, the faster you generally receive a positive ROI.

The important note here is we were just considering 4 or 5 benefits. The typical mobile application can improve customer service, inventory management, onsite sales of additional services, annual contracts and upgrades plus provide shipping status and cash collection. There are many things that can add value beyond the few we just discussed. Follow this link to read more on this subject.

If you would like to discuss this topic in more detail please contact me.

***********************************************
http://mobileenterprisestrategies.blogspot.com/
***********************************************

Mobile Application Development Strategies for Handhelds, Smart Phones and PDAs

The mobile application framework on the mobile handheld computer, Smart Phone or PDA can be thought of as a mini-EAI application (enterprise application integration platform). In the world of SAP they have NetWeaver for integrating all of the various applications together. NetWeaver is described as an integrated technology platform. Many different mobile software applications are found on a typical mobile device and they all need to be integrated together as well including:

• Radios - Bluetooth, wifi, RFID, GPS, Phone
• Data collectors - RFID, barcode scanners, digital images, voice memos, GPS, credit card swipers, mobile applications and forms
• Databases, synchronization technologies
• OS with downloadable applications

All of these various applications need to be integrated together using some kind of mobile integration technology platform. The OS can take care of many of the simple features and functionality, but a database driven integration platform for the mobile device is required if you are going to create various application layers that are all integrated into one downloadable mobile software application that can combine all of the necessary application functionality into one synchronization platform that is integrated with your back-office business applications.

Mobile applications have many unique requirements. Among these requirements are:

• GUI that can be resized quickly based upon the mobile device used
• Data collection fields and forms
• Mobile application workflow engine and validation features
• Data validation features
• Framework for pulling in data from third-party data collection hardware and software applications (barcode scanners, RFID, GPS, voice memos, credit card swipers, databases, etc)
• Mobile database (small databases optimized for mobile devices)
• Synchronization technology on the mobile device and on a central server

Mobile software application developers will want to find a good development toolkit for efficiently creating mobile applications. These toolkits can assist in quickly creating:

• Application GUIs
• databases
• Synchronization scripts
• Workflows
• Integration with third party data collection applications
• Data validation features
• etc.

In addition to the basics listed above, it would also be very useful to have the following:

• Mobile application workflow engine (as described in this article)
• A mobile software kit based on your back-office ERP or database

Wouldn't it be nice to bring up a "work order ticket" on your Oracle or SAP system and immediately replicate the data requirements and valid data rules on your mobile device database? Today, this is a long and painful exercise. Each field in the SAP or Oracle database for that specific application would have to be analyzed to determine what is a valid data entry. The validation rules, would need to be individually documented and recreated on the mobile application database manually. An ERP centric mobile application toolkit would quickly transfer those data validation requirements to the mobile application that would be collecting the data and synchronizing back to the office.

If you have not developed industrial strength mobile applications before, it may be good to work with some experienced mobile application developers on the first few. There are strategies that experienced mobile application developers employ that can save you much time and pain.

If you would like to discuss this topic in more detail please email me.

***********************************************
http://mobileenterprisestrategies.blogspot.com/
***********************************************

13 Key Steps to a Successful Mobile Application Development Project

Companies now days are looking for ways to do more with less. Many recognize that their mobile workforce is being managed inefficiently and extending business process automation to mobile field workers is becoming a priority. Saving fuel, reducing paper, reducing administration work load, more efficient dispatches are all important.

The following 13 points identify how you can get started automating and mobilizing these business processes.

Step 1 – Understand the ROI/Scope of the Project and Plan Ahead

“What’s the number one reason a mobile project fails?” is a common question we get asked. The answers are that many companies don’t put enough upfront thought into defining the requirements, scheduling testing resources and planning a deployment strategy. The results of these deficiencies are project scope creep, cost overruns, missed deadlines, poor user acceptance and sometimes even complete project failure.

Step 2 – Build a Team of Stakeholders

Make sure the members of your team have the right roles and responsibilities to help the project succeed. Mobile solutions usually tie into other corporate IT assets and business processes, therefore impacted members of your IT department and business units need to be on the project team.

In addition, a representative mobile field worker(s) should be included on the project team to provide valuable “real-world” insight. Don't forget the folks running the IT helpdesk. They are likely to get called when the mobile handheld PDA runs out of battery, memory or needs repaired or replaced.

Step 3 – Select a Partner That Specializes in Mobility Solutions

Performing successful data synchronization from mobile computing devices can be a challenging and complex task. There are many variables that can affect the results of synchronization. To insure you get your solution done correctly the first time, you need experienced experts in mobile technology. You need technologists who specialize in the design, development, deployment and support of enterprise mobile solutions.

Step 4 – Know Your Target Users

During the planning and scoping phase of your mobile project, take time to experience the working environment of your mobile workers and observe the business processes in action. Pay specific attention to how information is collected and exchanged between the office and the mobile workers. These observations can significantly impact the design, development and deployment of a successful project!

Step 5 - Evaluate the user environment

How do moist, cold and dirty environments impact the mobile devices? How does low light or bright sunlight affect visibility of the screen? Can workers read the small text on the PDA screen, or does the text need to be larger?

Step 6 – Don’t Underestimate the Complexity of Synchronizing Field Data

Step 7- Understand the technical challenges and issues

One of the biggest mistakes a project planner or IT department can make is to underestimate how complex data synchronization can be. Part of designing a solid and reliable mobile solution is to select robust synchronization middleware and to spend time designing and testing the data synchronization. Without the right middleware and design your end users could encounter issues such as extra long sync times (hours, not minutes), duplicate records, incomplete data, lost data and even database corruption. Every one of these issues will trickle down to your support department, so designing it right the first time is very important.

Step 8 – Build in Phases

Most successful projects involve a series of phased implementations. Each phase can be developed, tested and implemented in an orderly manner. Once a phase is deployed and proven, additional phases can be layered on top that include more features and added complexity. Remember, the more data requirements that you add the more data you must synchronize, and the longer each synchronization session will take. Only synchronize data that your remote users require in the field. In addition, most mobile devices don’t have the same CPU power or memory as a PC/laptop, so be aware of how the performance of your solution will be affected by a smaller, lower powered device.

Step 9 – Evaluate Your Hardware and Connectivity Needs

The term “mobile devices” can have many different interpretations. Today, laptops, Tablet PC’s, UMPCs, PDAs and Smart phones are all identified with this term. When determining the best mobile device for your project you will want to consider screen size, data storage capacity, security, physical working environment, required hardware accessories such as barcode scanners, GPS, digital cameras, RFID, and the ability to upgrade the device with updated hardware and software components.How do you connect your mobile device to your enterprise database applications? You have many options including cradle, WiFi, satellite, Bluetooth, wireless, dial-up modems and satellite uplinks to name a few. The method(s) you choose will be affected by how often your mobile workers need to send/receive data. How much data will be transmitted and will they always have connectivity. Study each option, your working environment and consult your mobility partner to make the best selections.

Step 10 – Deploy to a Limited Focus Group, Evaluate and Improve

Once you have completed version 1 of your mobile solution and you are ready to deploy in the real world, roll out your solution to a small group of trusted and motivated users. Define a specific period of time to evaluate the solution, document the results and identify any required changes and improvements. The result of this evaluation should be an improved mobile solution that is ready for wide deployment.

Step 11 – Set and Enforce Hardware and Security Policies

Mobile devices are small computers with the ability to store sensitive corporate data, communicate this data over the Internet and even catch viruses. You must clearly communicate how mobile devices are to be used and for what purpose. Establish and publish guidelines for using mobile devices.

Step 12 – Provide Full Support for Mobile Users

Mobile devices are guaranteed to break. What is your plan for keeping a mobile worker productive and communicating business critical information when their mobile device ceases to function or gets misplaced? These are inevitable issues that are best planned for in advance. Have a plan and a documented back up process.

Step 13 - Select a technology partner that understands your business applications and ERP

I f you use SAP, make sure that the mobile technology partner you select is also an expert in SAP mobile.

***********************************************
http://mobileenterprisestrategies.blogspot.com
***********************************************