How to Develop a Slow and Unreliable Mobile Software Solution for Mobile Handheld PDAs and Smartphones
Some companies have figured out how to develop slow and unreliable mobile software solutions for use on expensive and fast handheld PDAs and smartphones completely on their own, but for those new to this process please read on:
- Make sure you purchase the slowest available processors on your handheld PDAs
- Develop your mobile software applications in complete isolation from your real world working environment – chance and fate make life interesting if not entertaining
- Make sure you purchase the least amount of memory possible on your chosen PDA
- Purchase outdated and end-of-life handheld PDAs (try eBay)
- Develop new mobile solutions to run on old operating systems (try pocket pc 2002 or 2003)
- Choose a dial-up modem option for synchronizing your PDA (forget wireless broadband)
- Develop mobile solutions that assume you will always have good wireless carrier coverage
- Make sure if you lose wireless coverage, that your mobile software application is useless
- Take your existing desktop server application and force it to run on your PDA
- Don’t filter the data you want to synchronize from your Oracle or SAP databases, just download the entire corporate database to your handheld PDA
- Don’t synchronize only “changed” data, download the entire corporate database each time you synchronize
- Make sure if your connection is broken, you start the entire synchronization process over again – none of this starting where you left off sissy stuff
- Don’t consolidate your enterprise data into one simple mobile synchronization “view”, leave the data in dozens of different databases and database tables spread liberally around your IT ecosystem – this proves your courage and fortitude
- Don’t bother optimizing your application for mobile environments
- Maximize the amount of encryption and security you use on every aspect of your mobile solution – with enough security and encryption you can slow the data synchronization down to a mere trickle
- Make sure you have all your mobile workers synchronize their handheld PDAs at the same time in batch mode
- Hard code your mobile software solution to work only on one specific handheld PDA that can only synchronize with your backend database in one specific manner
- Ensure that the software programmer that develops your mobile software application is ambitious and feels he/she is under paid and under appreciated, and/or their green card is about to expire
- Develop your own synchronization middleware…so what if other software companies have spent the last 15 years perfecting it…no time like the present to begin your own 15 year odyssey.
- Make sure this is your first time developing a mobile software solution – it brings out the pioneering spirit
- Give yourself some unrealistic development time frames – make sure you commit to these time frames publicly and in the presences of senior management. Make sure that senior management then develops their business strategy around the dates you provided
- Don’t include testing and debugging time in your project plan…you need to cut corners somewhere
- Documentation is only for forgetful minds, don’t waste your time here
- Purchase all your handheld PDAs before you develop your mobile application. Purchase enough to last the next 8 years. Who knows how long they will be available on the market and you don’t want to re-develop your mobile software application for new operating systems and features
- Allow your mobile workers to download all the games, music and videos they want onto their handheld PDAs
- Don’t standardize on a particular operating system or handheld PDA specification – it will stifle creativity
Discover more from The Future - With Kevin Benedict
Subscribe to get the latest posts sent to your email.
Leave a Comment
