You Should Not Develop a Mobile Application - Just Because You Can

We often receive calls from software developers asking about our mobile software development environment. The developers often ask the question, "Why should I use your development platform when I can develop my own mobile software application for handheld PDAs?" That is a good and fair question. I will usually follow their questions with my own:

1. How many mobile software applications have you already designed, developed, deployed and supported successfully for handheld PDAs? Is your employer comfortable with having you learn on the job or are they risk adverse? Are they willing to be patient with your learning curve? If it takes you 4 months longer to develop your own, does the business suffer?
2. Have you created a full synchronization engine successfully in the past? This is very complicated and software companies like MobileDataforce have spent years optimizing these. What are the chances you will get it right and optimized on the very first project?
3. Do you have experience developing and configuring a variety of connectivity options such as cradle sync, wireless sync, satellite sync, bluetooth, etc.? Does the business manager know which one is needed in every case? Should you develop one, or develop multiple methods? Are the business requirements likely to change in the next 3 years?
4. Have you developed a full database integration manager for mobile solutions? Do you need an API or will your DBA allow you to directly populate the database? If you can directly populate the database, then the data better be validated in the mobile software application on the handheld pc. Did you set aside time for that?
5. Do you have experience designing scalable and reliable mobile applications? This is simply an experience thing. You don't know what you don't know.
6. Do you have support for a Pocket PC 2003, Win CE, Microsoft Mobile 5 & 6? How are you going to upgrade and support next year's mobile OS from Microsoft? Is this built into your project plan and budget?
7. Have you developed mobile applications that run on a large variety of different mobile handheld devices? This takes a lot of work and thought. Every week new mobile handheld devices are being delivered with new technologies and add-on components. The device selected today, will likely not be available next year at this time. How do you keep current?
8. Do you have experience developing interfaces for third party hardware? Mobile applications often need additional third party technology integration like bar code scanners, RFID, GPS, Digital Cameras, etc.
9. Have you thought through and developed dashboards for managing mobile application security, users, applications publishing, etc?
10. Do you have a development environment set up exclusively for mobile applications development that may include short-cuts, libraries, screen designs and scripts?
11. Do you have experience creating a helpdesk dashboard for sync logs, users, applications, device management, etc.?

Most often the developer was only interested in creating the screens for the mobile application, not a complete mobile application platform and support system. They had not considered the full end-to-end solution requirements when volunteering to develop a mobile handheld application.