What Were Your Worst Mobile Platform Development Mistakes?


I’m working on a story, and I’d like your help. It’s about the biggest mistakes made by developers who work on mobile platforms. The mistakes need to be specific to mobile platform development. What were your biggest screw-ups? What have you learned from them? What are the biggest mistakes you see other developers make?

Ideally, I’d be looking for anywhere from 3-5 common mistakes. If you have more or less, however, don’t hesitate to pass them along. And these are for any mobile platform, whether it’s Windows Mobile, Windows Phone 7, iOS, webOS, Android or whatever.

I’d like to use full names wherever possible. If anonymity is needed, however, just tell me, and I’ll use your first name and last initial only (or find some other way to protect you, if you need more than that).

Feel free to be as brief or detailed as possible. Share your story, if you have a good one, of something you did that you later regretted. Pass along your words of wisdom for other developers, and show them what to avoid.

I’m looking forward to hearing from you. I can be reached here. Thanks in advance for participating in this!


Keith Ward

Editor in Chief, MSDN Magazine

Comments (1)

  1. On WinMobile 6.5 and prior.  

    1. Using the ListView for data that can grow.  The ListView was not built with large datasets in mind, so loading the view could take forever!   After a few bad experiences I had to ban the use of the ListView.

    2. Underestimating sync and thinking it was solved.  Not even close.  Seems now matter what you try you end up customizing some aspect of it.

    3. Thinking data connections were consistent.  You have to cache data, dropped calls, and data connections must be accounted for.

    4. A server database schema does not make a good mobile database schema.  Be extra careful when creating indexes.  You don't get StoredProcs, views, triggers, foreign keys, etc.  Only store what you have to have.

Skip to main content