Capawesome Launches Capacitor AdMob on Google Next-Gen SDK
Capawesome has released the first Capacitor AdMob plugin built on Google's Next-Gen Mobile Ads SDK for Android, featuring Kotlin-first architecture and targeting the 2028 legacy SDK sunset.
Stock photo for illustration only, not from the actual event
- Capawesome releases the first Capacitor AdMob plugin built on Google GMA Next-Gen SDK.
- Legacy Android GMA SDK reaches deprecation on June 30, 2027, and sunset on June 30, 2028.
- Supports all 5 ad formats with a new Resize Mode to prevent banners from blocking UI buttons.
- Integrates User Messaging Platform (UMP) consent flow for EEA, UK, and regulated US states.
Google currently operates two Android ad SDKs in parallel, and one of them carries an explicit expiration date—a single fact that should dictate your choice when picking an AdMob library for a Capacitor app this year. Capawesome has announced the release of the Capacitor AdMob plugin, the very first of its kind built on Google's Next-Gen Mobile Ads SDK, shipping as part of the paid Capawesome Insiders subscription.
The legacy Google Mobile Ads SDK on Android currently sits at major versions 24 and 25, with Google establishing a strict deprecation schedule. They reach their deprecation date on June 30, 2027, and their sunset date on June 30, 2028, after which ad requests face the severe risk of returning no fill and failing to serve ads entirely.
The successor is the GMA Next-Gen SDK, delivered as a new Kotlin-first artifact under com.google.android.libraries.ads.mobile.sdk. Because it utilizes a completely different API surface instead of a standard major version bump of the old library, plugin authors are forced to perform a complete port. Capawesome's plugin runs on this Next-Gen SDK on Android from day one, defaulting to ads-mobile-sdk 1.2.1, while utilizing the latest Google Mobile Ads SDK on iOS where a Next-Gen variant is not yet available.
Migrating to the GMA Next-Gen SDK represents a pivotal shift for mobile developers. The Kotlin-first architecture streamlines memory management and native performance, but it also requires a complete rewrite of ad integration layers. Adopting this library early prevents last-minute technical debt when Google's legacy sunset deadlines take effect.
The plugin comprehensively covers all five AdMob mobile formats: banner, interstitial, rewarded, rewarded interstitial, and app open. All full-screen formats adhere to a clean two-step structure utilizing a load method that returns an identifier followed by a show method. Furthermore, rewarded formats accept a serverSideVerification option with userId and customData parameters forwarded directly to server callbacks.
Stock photo for illustration only, not from the actual event
Banner integrations—historically cumbersome in Capacitor due to native views overlaying web views—are streamlined via three distinct placement modes. Resize mode offers the fastest route to ensuring banners never obstruct UI buttons, supporting seven specific dimensions including AdaptiveBanner, InlineAdaptiveBanner, and fixed sizes such as 320x50, 320x100, 300x250, alongside 468x60 and 728x90 for tablets.
Compliance is equally robust, incorporating mandatory User Messaging Platform (UMP) consent flows for users in the European Economic Area, the UK, or regulated US states via the requestConsent method. Ten dedicated lifecycle events track ad performance, anchored critically by adRevenuePaid to power LTV modeling, ROAS dashboards, and granular cohort analyses.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment