While here on the Mobile Frontier, we're "blazing new trails", creating new mobile apps to help attract and retain customers or simply improve worker productivity. But on this path, I can't help to think, are there any lessons already learned in building and deploying software that can help us avoid "hitting a dead end" or avoid risk? The late-president of my alma mater George Low once said, "Without risk there can be no progress.” However, in that same article by the current president, he's also quoted as saying, “I know of too many people who have failed because they thought they knew everything and refused to listen to others.”
Well here's one of those times that I want you to hear [read] me! Mobile apps are different, but they STILL face SOME of the same issues as software has faced in history: apps crash, apps perform poorly, they can be disliked, uninstalled, or <insert your favorite app problem here>. So when I heard about a highly visible app performance and crash problem from a famous recording artist, delivered by one of the top two mobile phone manufacturers, (a second article here) I begin to think - did anyone really learn from history? Where was the performance/scalability test?!?!?!?!?!
Yeah, I downloaded this app. It crashed many times - even after that day, and I haven't tried it in a while. -SnookDogg (my "inner rapper" name)