Windows Phone App Studio isn’t a bad product, it does an admirable job of creating boilerplate apps, but its UI seems to be squarely aimed at that subset of the population that doesn’t know how to code but is clearly at home with things like camel casing and pascal casing. If the non-programming crowd wasn’t already dazed and confused, surely the Pascal cased “DataSource” button should do the trick and set them firmly adrift in the Sea of Needless Compelxity.Īt this point, why hold back at all Microsoft, why not go full bore and inject some Hungarian notation into this bad boy?įor a tool that is meant for non-programmers, Windows Phone App Studio can’t seem to stop speaking the language of programmers. Seriously Microsoft, “servicedsCollection” and “teamdsCollection”?! Why use words and spaces when you can add a heaping full of complexity by introducing people to the concept of camel casing!īut wait, there’s more. If Windows Phone App Studio is meant to be a tool to empower legions of business savy, non-programmer types to create their own apps, then why in the name of all things Sans Serif would you present them with a screen that looks like this?!
While you don’t need to know how to write code to build an app with Windows Phone App Studio, Microsoft certainly does do its best to make you wish you did.īe it Outlook or Windows, Microsoft software can never just work, it always has to have that extra dialog box, that extra bit of verbosity to needlessly complicate the user experience with technical jargon and programmer talk.
My experience was well, a decidedly Microsoft like experience. It sounded very cool on paper, but then I tried to build an app with Windows Phone App Studio. Last week, I wrote about Microsoft Windows Phone App Studio, a DIY tool introduced created by Microsoft that’s meant to allow non-programmers to create native Windows Phone apps with a ‘simple’ drag and drop user interface.
0 kommentar(er)
