Windows Store pricing detailed

first_imgThe October 26 launch of Windows 8 is rapidly approaching, and that means it’s time for Microsoft to rally developers to make sure that the Windows Store is well-stocked with apps and games for the impending rush of shoppers. The doors are already open to users of the Windows 8 Preview builds, and it’s been smooth sailing so far. Now, Microsoft has put up a blog post designed to answer that all-important question: how will developers monetize their apps?The methods are the same tried-and-tested ones you’ve encountered on Windows Phone, iOS , or Android. The Windows Store allows developers to offer ad-supported apps, in-app purchases, trial installs, and even support for developer-hosted billing systems.One interesting twist with the Windows Store is Microsoft’s “commission.” While the initial cut is the same 30% that’s become standard in pretty much every app market, things change once an app’s total sales pass the $25,000 mark (and that includes in-app purchases). After that point, Microsoft reduces its cut to 20%, allowing developers of successful apps to pocket a little additional cash. 10% might not seem like much, but for developers of successful titles it’s another strong incentive to get their apps Metro-ready and submitted to the Windows Store.Microsoft is also raising the bar slightly when it comes to purchase prices. You won’t find any 99-cent apps or games in the Windows Store. They’ll start at $1.49 — a modest bump to be sure, but just one more way Microsoft is trying to differentiate the Windows Store and remind developers that getting paid is an important part of building an app.Users will appreciate the fact that Microsoft is pushing hard for trial apps. In their blog post, it’s mentioned that trial apps can lead to five times the sales of paid apps that don’t offer a test drive. Microsoft is keen to point out that developers benefit in other ways, too — such as harvesting useful telemetry data from customers that may otherwise never have used their apps.More at MSDNlast_img read more