The first version of our SDK was released as part of the initial experiment that turned into what AdDuplex is today. While we released numerous updates to that package, it didn’t change the fact that it was based on the minimum viable product.
We have released v.2 of our Windows Phone SDK more than a year ago. Among other features it added support for image ads. But v.1.x was purely text based and, in order to support the legacy version, we are still forced to require both text and image ads from Windows Phone developers and advertisers who would prefer to use just an image ad. This results in unnecessary confusion and complexity of the UI and we feel that it’s time to address it. Especially since there’s no downside in upgrading to v.2.
So, what’s the plan?
- on February 17th, 2014 we will stop accepting new apps using SDK v.1.x
- on July 1st, 2014 we will stop serving ads to apps running SDK v.1.x
This should give you plenty of time to do the upgrade without disturbing your normal workflow.
What are the benefits of upgrading to v.2?
- improved user and developer experience, ad serving speed and stability
- we will show image ads for your app only if you are running SDK v.2.x in it
- upgrade to v.2 by the end of February 2014 and you will be automatically entered into a draw to win one of 10 gift coupons for 1,000,000 free ad impressions (list price – $990)
OK, how do I proceed?
Version 2 of the AdDuplex Windows Phone SDK is available for XAML apps targeting both Windows Phone 7 and Windows Phone 8. Upgrading is as simple as swapping the SDKs. Download and implementation instructions are available in our knowledge base.
What about XNA?
XNA games are a small, but important part of the AdDuplex community. While it’s possible to use v.2 of our SDK with hybrid XAML/XNA and MonoGame apps and games, there’s no v.2 SDK for “pure” XNA Windows Phone games at the moment. We are trying to understand if there’s a demand for a new SDK for XNA before committing to work on it. So, if you are developing a new “pure” XNA game or actively update one you’ve made before, please let us know in the comments below or via email. We would also love to hear from “former” XNA developers who have moved to using other frameworks, so we can decide if we should allocate time to work on the XNA SDK or rather spend it improving support for other frameworks.