On AppFlood we’re constantly working to provide our users with top quality products. Our latest most efficient monetization tool, the Splash Screen SDK just got updated to version 1.1 with a few useful improvements.
What we modified
Over the past few weeks we collected lots of useful feedback from our wonderful developers and we carried into effect changes that were driven by their inquiries.
More specifically, since we just introduced the AppFlood RTB platform not long ago and now receive premium DSP and SSP traffic, we decided to allocate more of the DSP ads to Splash Screen. RTB advertisers not only drive higher eCPM rates and supply Splash Screen inventory with higher quality ads, but also increase the SDK’s ad fill rates.
If you’re wondering about RTB, you can find more info: here.
Additional new advantages of the updated Splash Screen is the optimized memory that enables ads to load faster in our network’s applications. It offers swifter and more efficient app performance at the most crucial time: when an app is launched. Also, we managed to fix a bug with the initialize method that prevented ads from being displayed. In cases when a developer initialized only Splash Screen, the bug wouldn’t allow ads to load (all ads had to be initialized in order to overcome it). Moreover, since small screen devices (<480px) didn’t offer enough space for Splash Screen to fully display, the SDK will not show on smaller phones. On top of that, the integration guides are improved, making the implementation process clearer and easier for developers to use our SDK.
Developer News Feed
We put a great emphasis on communicating to our developers what we’re currently working on. If you want to catch up on the news, you can always head to your user dashboard and go to the Developer News Feed at the bottom left of the screen. You will see all the different updates as well as what we managed to fix and improve so far. The list will be updated regularly. (Developer News Feed).
Also, if you have any feedback or inquiries about the Splash Screen SDK or if there’s anything else bothering you (from a noisy neighbour to troublesome asynchronous code), don’t hesitate to contact us. We’re online for you 24/7 to help with anything you may come across.
In the next post, we will introduce a case study of one of our top Splash Screen SDK publishers, so stay tuned!
