Wednesday, December 15, 2010
Posted by Jon Westfall in "Windows Phone Developer" @ 07:30 AM
"We have had many users ask us when the Windows Phone 7 app will be available and our response for the last month or two has been 'any day now'. Unfortunately, it is still not available today. As a team that prides itself on trying to be quick to deliver LastPass on the newest platforms and devices, we feel like we owe an explanation to all users who have been eagerly waiting. As you might already know, Windows Phone 7 is nothing like the previous Windows Mobile devices. They changed everything, including the distribution model for apps. All installs must go through Microsoft (similar to Apple's control of iPhone apps) and all apps must be first approved. This is where the major holdup has been."
Part of the reason I use LastPass is because it runs on freaking everything I could ever use, and if it's a new product, it will have LastPass on it in fairly short order. Windows Phone 7 is no exception, however the LastPass crew has hit a small snag in the form of the Marketplace validation process. This is a process I have experience with as well, so I can vouch for the frustration the LastPass crew is feeling now. Don't get me wrong - it's not that the Marketplace validation reports I receive aren't helpful, in some cases though, they just aren't helpful enough. Case and point? A recent failure report I got listed the steps to reproduce as "Constantly change the values within the appropriate areas", which while true, could have been more helpful (e.g., "Constantly change the values (specifically to X) within the appropriate areas."). Don't get me wrong, it's a much nicer system than a blanket "You fail", but come on Microsoft, if you're going to give a report, at least go all the way with the usefulness factor! I mean, after all, your testers know what value they put in to crash my app, why not tell that to me?