Want to know what’s new in Windows Phone Dev Center? Take a look!
Ad mediation lets you display ads from multiple ad networks in your app. Different ad networks may have their own strengths, with some having a higher cost per thousand views (eCPM) or higher fill rate (percentage of ads served when your app makes a request) in certain markets than others. With a single ad network, you may end up with unfilled ad requests, causing you to lose potential revenue. With ad mediation, you can specify how each of your ad networks is used by updating your mediation configuration in Dev Center. You can optimize this by market, so that you're using the most effective ad networks in the appropriate regions. And you can make changes to how each ad network is used without having to republish your app. For more info, see Using ad mediation to maximize ad revenue.
Using the respond to reviews feature is one way to let customers know you’re listening to their feedback. With a review response, you can tell customers about the features you’ve added or bugs you’ve fixed based on their comments, or get more specific feedback on how to improve your app. This feature shouldn’t be used for marketing purposes. For more info, see Respond to customer reviews
Dev Center now requires only a one-time registration payment, which grants developers the ability to submit apps to both the Windows Store and Windows Phone Store, with no annual renewal fee. Register once for a low single price ($19 for individual accounts and $99 for company accounts) and you’ll be able to submit both Windows Phone apps and Windows Store apps.
If you publish a Windows Phone version and a Windows version of your app, you can share a single identity between the two versions of your app in the Windows Phone Store and the Windows Store. This means that a customer who has purchased the app in either Store can download the app from the other Store without paying for it again.
Sharing an app identity also means you can roam data between the Windows Phone and Windows versions of your app. For example, a user could buy durable in-app products on their Windows Phone and have their in-app products available in your app on their Windows device.
If you plan to associate your Windows Phone app with a Windows Store app and your app offers in-app products, the in-app products that share the same alias in the Windows Phone Store and the Windows Store must also share the same type, Consumable or Durable, for example. See In-app product properties for more info.
Beta apps in the Windows Phone Store no longer expire, so you can keep your beta running in parallel with the real app for continued feedback from the beta community. However, you can unpublish or delete your beta app at any time, ensuring that new users cannot download the app. For more info, see Beta testing your app and in-app products.