SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere Nutzervereinbarung und die Datenschutzrichtlinie.
SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere unsere Datenschutzrichtlinie und die Nutzervereinbarung.
For developers who want to write Metro/WinRT applications, the transition is going to be rough,unless you have already been working in Silverlight or WPF. Even if you have used WPF, that willgive you the XAML and application model concepts but not the UI paradigms. The UI model thatMetro/WinRT uses is straight from WP7. In the demo apps, there is no easy way to exit. I assumethat Microsoft uses a WP7-like tombstoning/multithreading model, because the only way to breakout of them is CTRL+ESC. Likewise, in WP7 apps, there is no “legal” (as in, “will get past theApp Hub testing process”) way to deliberately exit the app. Don’t like it? Neither do I, and neitherdo a lot of other developers. It makes sense for a phone and probably a tablet but not a desktopOS.I realize that it is early in the development cycle of Windows 8 — the release isn’t even matureenough to be called a beta, and there is roughly a year before it hits gold status by most estimates.Microsoft has been slammed by a ton of analysts, industry observers, and reporters about its habitof announcing things like this in public well in advance of the actual release. Those folks are onlyseeing the PR side of things; for us developers, who are the lifeblood of Microsoft’s ability tomaintain or grow Microsoft’s market share, we needed to see this now. The Metro/WinRT apps area major change, and Microsoft needs us on board now so the company can launch with a full slateof quality titles. Think “new game console” style launch, not a traditional “new OS” launch. Theproblem is that unless Microsoft makes the experience of using legacy apps a lot better, Windows8 will be a very unpleasant experience overall. And the new Metro-style apps are not mappingwell to the keyboard/mouse; for instance, things that on a touch screen require a simple fingerswipe now require the user to hunt down a scroll bar and use it. Metro works great on my WP7phone and I love it there, but just as the Windows UI was a mess when translated to Windows CEand Windows Mobile, the Metro UI is a wreck on a desktop PC.At this point (in other words, if nothing changes on these items between now and final release), Ithink this is a good time to decide if you can transition your applications to Web apps.Metro/WinRT is lousy for apps that do complex work. Meanwhile, IE10 is very invasivethroughout Windows 8. While I often dislike Web apps, I think that for sophisticated tasks, theyare better than Metro/WinRT from what I’ve seen, and the legacy app experience is so bad that notmany developers will want to use it if they can avoid it, and new apps will feel very dated.Regardless of what shakes out in the final project, it is clear that Microsoft is signaling thatsophisticated desktop applications are a relative rarity, Web apps are much more common, and forthe things that use local resources, users prefer simple apps on the phone/tablet level ofcomplexity, not applications like we see now. I think Microsoft’s strategy may backfire, asdevelopers choose to write Web apps (possibly with non-Microsoft technologies) instead of tryingto make their applications work in the very unique, non-backwards-compatible Metro/WinRTstyle, or having their applications using the clunky legacy desktop.