Along with all the other details and demos that were announced earlier tonight in San Francisco for the upcoming Windows Store that will be an integral part of Windows 8 a new blog was kicked off that will detail the development process of the Windows Store.
According to the introduction by Antoine Leblond for the first post, which is titled Previewing the Windows Store, this blog will focus on informing developers on the store’s progress as a service and platform for developers.
In September, we announced the Windows Store as part of Windows 8 and the distribution point for Metro style apps. And today, at our Store Preview event in San Francisco, we described the app policies and business terms for the Store, both of which are now published to our Dev Center.We also announced our First Apps contest for developers, and confirmed that we’re also inviting a select set of developers to submit Metro style apps for inclusion in the Beta version of the Store.
We’re also proud to publish the Store’s developer-first economics—with up to 80% revenue share for apps sold through our platform. Combining the broad reach of Windows, a new developer platform, best-in-class developer tools, a reimagined user experience, support for new chipsets, and a built-in Store with industry-leading business terms—Windows 8 is the largest developer opportunity, ever.
According to Antoine this blog is intended as a dialog just like the Building Windows 8 blog is.
This first post is written by Ted Dworkin who is the partner program manager for the Windows Store.
When we set out to build the Windows Store, we wanted to do the best job of connecting people to as many great apps as possible. We realize the challenge of having apps stand out, particularly as app catalogs grow. We thought a lot about ensuring quality, maintaining trust, reducing friction, and enabling choices. We designed for these guideposts. We further established a set of four guiding principles that would inform both the overall design of the Store as well as the partnership that we want to have with developers:
- Designed for discovery
- Flexible business models
- Transparent terms
- Best economics
He uses the remainder of the post addressing those areas. Based on the length of this post and the detail there is an opportunity to learn a lot of stuff as this process moves forward.