displayio_sdk 0.2.5
displayio_sdk: ^0.2.5 copied to clipboard
Flutter plugin for the DIO (Display.io) ad SDKs — banner, infeed, interstitial, interscroller, audio and native ads on Android and iOS through one Dart API.
0.2.5 #
Smooth frame rate on Android without Hybrid Composition++.
- Where HCPP is not on (Android 13 and older, no Vulkan, or an app without the
EnableHcppflag), the plugin's native views are now hosted with texture layer hybrid composition instead of hybrid composition. The view is still a real view in the hierarchy, so impressions and Open Measurement fire as before, but Flutter no longer synchronises every frame with the platform thread. With an ad on screen, a Motorola edge 50 pro (144 Hz, HCPP off) went from 72 to 143 fps on an interscroller and from 107 to 143 on a banner; a Samsung Galaxy M52 (Android 13, 120 Hz) went from 83 to 120 on a native ad. - A creative whose player holds a
SurfaceViewwhen the view is created (seen with infeed video) is moved back to hybrid composition by Flutter itself: it plays as before, without the frame-rate gain. - With HCPP on, nothing changes. No plugin API change.
0.2.4 #
Smooth frame rate on Android while an ad is on screen.
- Android 14+ (Vulkan): the plugin's native views (banner, infeed, inline,
interscroller, In-Game Audio card, companion, native ad slots) are hosted with
Hybrid Composition++ when the app opts in with
io.flutter.embedding.android.EnableHcppin itsAndroidManifest.xml(see README, "Smooth frames on Android"). Hybrid composition synchronised every Flutter frame with the platform thread while an ad was visible: on a 144 Hz phone a game fell from 145 to about 42 frames per second. With HCPP it stays at 145. The views are still real views in the hierarchy: impressions and Open Measurement events fire as before (verified on a Motorola edge 50 pro, Android 16, for every format, the interscroller's parallax included). - Without the flag, or on older Android, nothing changes: hybrid composition as in 0.2.3. The mode is asked of the engine once per run.
- No plugin API change.
0.2.3 #
Native SDKs raised to Android 5.8.2 and iOS 4.8.2.
- Every ad request now carries the device sound state (muted / audible,
volume, output) in
ext.dio, so the ad server can target audio and sound-on demand to devices where it will be heard. Nothing to configure. - Android: stability fixes for several production crashes.
- iOS: interstitial, banner and interscroller fixes; the In-Game Audio
companion keeps its own size; the SDK no longer overrides the host app's
AVAudioSessioncategory, so an app that configures its own keeps it. - No plugin API change.
0.2.2 #
Fixes ad events going missing when more than one ad is alive.
- Every ad subscribed to the shared
dio_sdk/eventschannel with a stream of its own. A platformEventChannelkeeps one listener per name, and the native side one sink, so the latest subscriber took the channel over: an ad still on screen stopped receiving its events. A playing In-Game Audio ad that outlived the load of the next one never reportedcompletedorclosed, although the native SDK played it to the end; and any ad that stopped listening closed the channel for all the others (No active stream to cancel). The channel is now listened to once, while at least one ad listens, and each ad filters that single stream by its request id. Holding a preloaded ad while another plays, or a banner and an audio ad at once, now reports every event.
0.2.1 #
Fixes the iOS build of 0.2.0.
DioAdOptionsApplier.swiftusedFlutterStandardTypedData— the type backing the newDioInGameAudioConfig(icon:)field — without importingFlutter, so every iOS build of 0.2.0 failed with "Cannot find type 'FlutterStandardTypedData' in scope". Android was unaffected.
0.2.0 #
In-Game Audio customization and a card-less mode.
- Card styling (
DioInGameAudioConfig): background gradient, progress ring track and progress colours, accent colour, badge colours, corner radius, ring width, and switches for theADbadge, the now-playing indicator and the ring. Every field is optional and an unset one keeps the SDK default. - Your own image in the card:
DioInGameAudioConfig(icon:)takes encoded PNG/JPEG bytes andiconPaddingthe gap around them. The image replaces the default audio bars, takes no touches, and yields to the campaign's companion. - Card-less mode:
DioInGameAudioConfig(showCard: false)drops the UI and keeps the audio.DioInGameAudioAd.play()/.pause()drive it — nothing is heard untilplay, and the impression is counted when playback starts rather than on viewability.DioInGameAudioAd.hasCardreports which mode the ad is in, andpreferredSizeis no longer reported when there is no card. - Companion suppression:
DioInGameAudioConfig(companionEnabled: false)keeps the card on its own artwork; the SDK does not even load the companion. - Native SDKs raised to Android 5.8.1 and iOS 4.8.1, where this API lives.
0.1.0 #
New ad format and a diagnostic API.
- In-Game Audio (
DioInGameAudioAd): an audio ad the SDK renders as its own square card — progress ring,ADbadge and a native mute control — which the app positions itself (ad.cardView, typically in aStack). Playback follows attachment and on-screen visibility, so there is noplay/pause. Size it withDioInGameAudioConfig(customWidth:);ad.preferredSizereports the card's natural size. NewAdUnitType.inGameAudio. DioSdk.instance.placements(): lists the placements the SDK loaded for the initialized app id (DioPlacement— id + type). Diagnostics: it returns an empty list before init and on any native error, and never throws, so a settings screen cannot break on it.DioPlacement.typeis null for units this plugin does not model, with the native string kept inrawType.
Both are device-verified on Android and iOS.
0.0.2 #
Native SDK bump.
- Android:
com.brandio.ads:sdk5.7.4 → 5.8.0. - iOS:
DIOSDK4.7.5 → 4.8.0. - Breaking (iOS): the minimum iOS deployment target is now 15.0 (was 13.0). DIOSDK 4.8.0 raised its own platform requirement, so an app targeting iOS 13 or 14 will no longer build against this plugin.
The Dart API is unchanged. Both platforms build, but the native release notes are not published by the vendor, so re-verify ad rendering on a device.
0.0.1 #
Initial release — the DIO (Display.io) Flutter plugin, wrapping the native DIO ad SDKs for Android and iOS behind a single Dart API.
- Core:
DioSdk.instance.initialize/loadAd/sdkVersion, a sealedDioAdresult (DioInlineAd/DioInterstitialAd/DioAudioAd/DioNativeAd), ad lifecycle events, and viewability. - Formats: banner, infeed (video / display / audio), interstitial, interscroller (Dart-driven reveal parallax), inline, InFlowAudio / InRing audio, and native ads.
- Widgets:
DioAdView,DioCompanionView, and the native-ad slot widgets (DioNativeAdView+DioNative{Media,Icon,Cta}View). - Customization via
DioAdOptions— per-load placement styling (audio, interscroller, infeed, pure-audio, native asset params) plus ORTB ad-request and targeting config (DioAdRequestConfig). - Ad metadata:
ad.metadata(DioAdMetadata) exposes the bid-response fields (eCPM, advertiser, creative/campaign ids, nurl/lurl, TTL, …). - Server-to-server / ORTB:
buildOrtbRequest,token, andloadAdFromOrtbfor rendering a bid response the publisher already holds. - Android and iOS are both device-verified across every format.