There are many instances when a client calls upon a consulting firm to come in and improve their process. The client is in a state of complete confusion and frustration. They have spent time, money, and resources to create a new process which they believe to have a positive impact on a large part of the organization. The client states that there is substantial resistance to adopting the new process. Often those who have no choice but to adopt, due to the large effect to their everyday duties, are angry about the change and have little confidence in the team that implemented the new process. The client believes that the new process brings increased efficiency and accuracy to the business, but feels that the process still needs improvement in order for the employees to eagerly adopt.

In my previous entry, I discussed the shortcomings of Android in relation to the Enterprise and how it's not ready.  Several commenters stated we could get around this issue by adding this functionality to the application; being self-aware of application updates.  My team had discussed adding this sort of functionality before my blog entry, so we decided to go ahead and pursue this.  Close to 2 weeks ago, my team began gathering requirements and implementing a solution that would provide this self-awareness of application updates into our Android application.  An installation problem still exists if your carrier blocks installing from external sources, but we'll ignore that for this exercise.   

Android's just not ready yet.  There I got it off my chest.  Just like pulling off a Band-Aid.  I'm not even talking about the myth of fragmentation (and for the most part, it is a myth) or the missing Wifi proxy settings issue.  It's what happens after you author that wonderful application your enterprise so desperately needs...how do you distribute it?