TLDR: New public APIs, Ad opportunities metrics, new ad format: inFeed Native, a new engine under the hood and some fixes.
- For this new SDK, we built a new JS Engine from scratch. This new engine will allow us to ship fixes and updates remotely, reducing the need for an update of the SDK on your side. The new engine implementation does not rely on WKWebview anymore but directly on JavaScriptCore, we are still using WKWebview to display JS creative.
- The public API has been rethought. It will better match the needs of a majority of developers. We created a new single entry point for you: the ad placement. This entity will be taking care of all the processes to display ads in your app. It will request the ads, telling you when it was received or if some problems happen. Also, we split our delegate methods into two instances, TeadsAdDelegate and TeadsInReadAdPlacementDelegate.
- As part of our SDK v5 release, we introduced a new way to measure the ad opportunity. This measurement reflects the performance of your inventory. It will help build the visibility score of your placement in the publisher dashboard more precisely. This is beneficial for your business, take a moment and implement it.
- We are thrilled to announce a new way to display ads inside your app. Our latest placement type: inFeed Native, which allows publishers to display true native ads in their app feed, according to their own template for an optimal UX.
- Our background scroller format now supports animated images. Your users will be able to interact with rich animations in this ad format.
- The sound button now appears in the right place for VPAID creatives.
- VPAIDs that had resizing problems are now resized correctly.
- VPAID creatives are now displayed in the correct resolution.