Conversation
✅ Deploy Preview for prebid-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| | Policy | Behavior | Customization | | ||
| |--------|-----------|---------------| | ||
| |`Reward`|**Prebid SDK** can signal the publisher about the type and quantity of reward coins.<br><br> If the `rwdd` or `reward` object is absent in the response, by **default,** SDK will send an empty object into the respective delegate method. |**Publisher** can set the type and number of coins in the `rwdd.reward` object.| | ||
| |`Completion`|**Prebid SDK** will inform the application once the reward time has come.<br><br> If the `rwdd` or `reward` object is absent in the response, by **default,** <br><br>- **banner:** SDK triggers the completion of the banner rewarded ad after **120 seconds** on the screen.<br><br>- **video:** SDK triggers the completion of the rewarded ad once the video playback is completed. But only if the ad doesn’t have an end card. | **Publisher** can set the rule when the SDK should inform the app about the reward time. Depending on the ad format, the publisher can set different rules using `rwdd.completion.banner` and `rwdd.completion.banner` objects respectively.| |
There was a problem hiding this comment.
set different rules using
rwdd.completion.bannerandrwdd.completion.banner
probably you meant rwdd.completion.banner and reward.completion.banner ?
| | `Rotation` | **Prebid SDK** allows the rotation of the screen for the interstitial ads. The ad content is rotated according to the screen position. SDK changes the layout of the ad control elements according to the screen orientation. <br><br> **Publisher** has nothing to do in this operation, SDK doesn't provide any events to subscribe. | Currently, there is no way to customize the rotation behavior of the interstitial ads. Open an issue or PR for the alternative approach.| | ||
| | `Close Button` | **Prebid SDK** adds a close button to the interstitial ad, providing a way for users to dismiss the fullscreen ad. Depending on the ad format, the button can appear from the very beginning of the ad or with some delay. <br><br> **Publisher** is responsible for subscribing to the ad flow events and managing the app flow, accordingly. | **Publisher** can customize the default SDK behavior using the [Ad Experience Controls](https://docs.prebid.org/prebid-mobile/modules/rendering/combined-ad-experience-controls.html) feature.| | ||
| | `Learn More Button` | **Prebid SDK** adds a close button to the interstitial ad, providing a way for users to dismiss the fullscreen ad. Depending on the ad format, the button can appear from the very beginning of the ad or with some delay. <br><br> **Publisher** is responsible for subscribing to the ad flow events and managing the app flow, accordingly. |**Publisher** can customize the default SDK behavior using [Ad Experience Controls](https://docs.prebid.org/prebid-mobile/modules/rendering/combined-ad-experience-controls.html)| | ||
| | `Tap` | **Prebid SDK** processes the clicks, actually taps, in different ways, respectively, depending on the type of the ad. <br> **The publisher** is responsible for handling `adwillopen` delegate. |Currently, there is no way to customize the way of processing the taps on the ad. Open an issue or PR for the alternative approach.| |
There was a problem hiding this comment.
handling
adwillopendelegate.
should we add link to the doc as you did for banner autorefresh property ?
muuki88
left a comment
muuki88
left a comment
There was a problem hiding this comment.
Please use relative links whenever possible, so that links also properly work in stage deployments 😊
I know we have a lot of <br> tags floating around in the docs. Usually I recommend to avoid those.
Co-authored-by: Muki Seiler <muuki88@users.noreply.github.com>
|
Hi @muuki88
Could you suggest an alternative method for adding an empty line within a table cell? I tried "" but without success. |
|
I haven't found one 🥲 Ideally we would find an alternative, but at this point it's okay to have them, if the docs are unreadable otherwise. |
|
I would commit all the suggestions, using relative links and then merge this. Fine for you? 😊 |
Hi @muuki88 ! Yes, I'm ok to use relative links, but just want to make sure that you read this and this comment and are aware that in fact they are external links. So everyone is on the same page |
3 participants
Description
This doc will serve as a public spec of Mobile SDK UI/UX policy.
It describes how UI/UX is currently implemented. What is the default behaviour and how publishers can customize it if needed.
Eventually this doc will be changed if new UI/UX features are added to the SDK.
Publishers can use this doc in two ways:
🏷 Type of documentation
📋 Checklist
Closes prebid/prebid-mobile-ios#693