Anyone managed to make AdMob work on W8?

CoronaCards (Corona in native apps) CoronaCards for WP8
#21

Not sure what to tell you about that, but you could always port one game to W8 without ads and see what it does, and then when admob 8.1 is up you can simply just update your game.

If anything it just gives you the knowledge of what you will need to do to port your other games if and when you decide to.

I am not sure how much has changed since I was building apps for windows phones over the years but it use to take anywhere from 7-21 days to get reviewed but imagine that has come down a little bit but plan on releasing something here shortly just to see what the process is all the way through these days.

#22

Just build for Windows Phone 8, not Windows Phone 8.1. Then you can have admob advertising with your corona game. I have done this for my game and it works great. If you like I can help you out.

#23

And is there any penalty (e.g. in performance or less devices targeted) if you build for 8.0.

What is the advantage to build for 8.1 over 8.0?

#24

I’m not sure. There was a thread on here somewhere where someone reported a slight fps boost for building for windows phone 8.1. Unless you need any windows phone 8.1 specific native features, I would just stick with 8.0 since that is more widely supported right now by third parties such as admob.

#25

An app built for Windows Phone 8.0 will run on 8.1.  That is, Windows Phone 8.1 is backward compatible and will support installing/running 8.0 apps.

So, yes, Google’s AdMob SDK will work in an 8.0 “Silverlight” app, meaning it will also work on Windows Phone 8.1.  The keyword being a “Silverlight” based app.  Google’s current AdMob SDK is based on Microsoft’s Silverlight UI framework, which is also supported on 8.1.  What Google does not currently support is the Universal XAML UI framework, which is a new UI framework that Windows Phone 8.1 supports, but 8.0 does not.  Does this make sense?

Bottom line, yes, the current AdMob SDK will work.  Go ahead and use it.  Your WP8 built app will work on Windows Phone 8.0 and 8.1.

#26

Good news!

Any drawback for using 8.0 instead of 8.1 (e.g. performance)?

#27

>> Any drawback for using 8.0 instead of 8.1 (e.g. performance)?

There are no performance issues, but there are advantages and disadvantages between 8.0 Silverlight based apps versus 8.1 XAML based apps.

Regarding 8.0 Silverlight based apps:

  • Advantage:  They’re supported on both Windows Phone 8.0 and 8.1.

  • Advantage:  Has more 3rd party library/sdk support, like AdMob.

  • Advantage:  Microsoft incentive programs usually require this.  (Although this will likely change in the future.)

  • Disadvantage:  Does not support universal apps.  (ie:  No Windows 8 Metro or Windows RT tablet support.)

Regarding 8.1 XAML based apps:

  • Advantage:  Has universal app support.  (ie: Windows Phone 8.1, Windows 8 Metro, and Windows RT tablets)

  • Disadvantage:  No Windows Phone 8.0 support.  Only 8.1.  (8.0 takes nearly half the WP8 market right now.)

  • Disadvantage:  Not a lot  3rd party library/sdk support for it yet on Windows Phone, such as AdMob.

Now, the biggest reason you want to use an 8.0 built app is because it makes your app available to most of the Windows Phone market (ie: 8.0 and 8.1 devices).  According to the last statistics I’ve seen (see link below, page 6), you’ll see that 8.0 devices take about 45% of the market.  If your app was built for 8.1, then you would lose 45% of potential customers.  That’s huge!

   http://blog.adduplex.com/2014/09/adduplex-windows-phone-statistics.html

So, Microsoft and the WP8 native development community is currently going through a painful transitional period.  At the moment, most native WP8 developers are sticking to 8.0 Silverlight and will later work on 8.1 XAML support in the future.  This is Corona Labs’ plan too.  Just note that native developers don’t “add support” for 8.1 XAML.  Native developers (such as Corona Labs) have to rewrite their entire UI code base to support the new universal XAML framework.  It’s a large undertaking… which is also why you don’t see Google currently supporting 8.1 XAML yet for AdMob, because it basically means that they have to rewrite it.

Anyways, I hope the above helps explain it.

#28

Thnx Joshua, that is very informative and helpful!

#29

wrong thread oops

#30

Just FYI I posted an admob tutorial in this thread: http://forums.coronalabs.com/topic/52372-tutorial-add-admob-interstitial-ads-to-your-coronacards-windows-phone-8-app/

#31

Josh - thanks for posting all of those details re: 8 vs 8.1, very helpful.

#32

AdView bannerAd = new AdView

{

Format = AdFormats.SmartBanner,

AdUnitID = “xxx-xxx-xxx”,

VerticalAlignment = VerticalAlignment.Bottom

};

AdRequest adRequest = new AdRequest();

adRequest.ForceTesting = false;

fCoronaPanel.Children.Add(bannerAd);

bannerAd.LoadAd(adRequest);

Add this in the constructor in MainPage.xaml.cs file to get banner adds working.

ISO

#33

AdView bannerAd = new AdView

{

Format = AdFormats.SmartBanner,

AdUnitID = “xxx-xxx-xxx”,

VerticalAlignment = VerticalAlignment.Bottom

};

AdRequest adRequest = new AdRequest();

adRequest.ForceTesting = false;

fCoronaPanel.Children.Add(bannerAd);

bannerAd.LoadAd(adRequest);

Add this in the constructor in MainPage.xaml.cs file to get banner adds working.

ISO

#34

@ISO

Thank you for posting this, banner are working!

#35

@ISO

Thank you for posting this, banner are working!