<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Diana Elezaj on Medium]]></title>
        <description><![CDATA[Stories by Diana Elezaj on Medium]]></description>
        <link>https://medium.com/@Diana71?source=rss-e7a06f49fdef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ArAhF-VeBx3wgaoAZ5rhmA.jpeg</url>
            <title>Stories by Diana Elezaj on Medium</title>
            <link>https://medium.com/@Diana71?source=rss-e7a06f49fdef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:04:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Diana71/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Tips and Tricks Learned from Monetizing iHeartRadio’s iOS app]]></title>
            <link>https://tech.iheart.com/tips-and-tricks-learned-from-monetizing-iheartradios-ios-app-c79a571c440b?source=rss-e7a06f49fdef------2</link>
            <guid isPermaLink="false">https://medium.com/p/c79a571c440b</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[ads]]></category>
            <category><![CDATA[app-monetization]]></category>
            <category><![CDATA[iheartradio]]></category>
            <category><![CDATA[monetization]]></category>
            <dc:creator><![CDATA[Diana Elezaj]]></dc:creator>
            <pubDate>Fri, 30 Nov 2018 22:33:42 GMT</pubDate>
            <atom:updated>2018-12-01T00:31:40.747Z</atom:updated>
            <content:encoded><![CDATA[<p>As a regular attendee of <a href="https://www.meetup.com/iOSoho/">iOSoho</a>, I was thrilled to have the opportunity to host everyone at iHeartRadio, as well as speak about our team’s experience with app monetization.</p><p>Working at iHeartRadio provides great opportunities like this to learn and share, and we are actively hiring, so check out our <a href="https://jobs.iheart.com/">Jobs Site</a> if you’re interested in learning more.</p><p>The video below has the talk and Q&amp;A in its entirety, and we’ve provided the transcript as well. Enjoy!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F302964151%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F302964151&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F742828640_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/a9710834208b105c0a97284685e15dda/href">https://medium.com/media/a9710834208b105c0a97284685e15dda/href</a></iframe><p>Transcript:</p><p><em>Hello everyone, thank you so much for coming and welcome to iHeartRadio! My name is Diana, I’m a Senior iOS Engineer here at iHeart, and as you know today we’ll be talking about monetizing your app. I’ll be sharing tips and tricks that we’ve learned from monetizing iHeartRadio.</em></p><p><em>So let’s start with the first question: Why do you need to monetize your app?</em></p><p><em>First and foremost, your app needs sustainability. Whether you have a strictly free product, or even if you offer subscription plans, you still need to think about monetizing it for your free tier.</em></p><p><em>As you can see from this graphic here, the vast majority of downloads from the App Store are free apps, so if your app falls into the light blue category of this graphic, you need to think about monetizing it.</em></p><p><em>Up until December 2016 iHeartRadio was a strictly free product: we only had free users. But that’s when we decided to add 2 subscription plans: Plus and All Access, but still a very large number of our users are Free users, so monetization through ads is a very important part of our monetization strategy.</em></p><p><em>In this talk, we’re going to explore some popular Ad SDKs; we will highlight known problems and issues that we’ve faced while using these SDKs, and also I’ll be sharing some solutions; and also we’ll discuss good user experience with regards to showing ads.</em></p><p><em>So here are some popular Ad SDKs that we’ve used in the past or continue using: AdMob, Facebook Audience Network and Adswizz.</em></p><p><em>The first two SDKs can be used for displaying video or banner ads, and Adswizz is usually used for displaying audio ads that get displayed with an image. Any developer can use any of these SDKs directly.</em></p><p><em>So let’s take a look at some ads that we’ve implemented in our iHeartRadio app using these SDKs.</em></p><p><em>The first one is, what we call, an </em><strong><em>In-stream Ad</em></strong><em>. This is basically an audio ad that gets displayed with an image between tracks while users are listening to an artist station.</em></p><p><em>Next, we have an </em><strong><em>In-Line Ad</em></strong><em>. This is a banner ad that is embedded within the content and scrolls along with it as user is scrolling.</em></p><p><em>The third one is a </em><strong><em>Transition Ad</em></strong><em>. As you can see from this short video here, this ad gets displayed while users are transitioning between different screens. One of the main criteria to display this ad is that there has to be something streaming in the mini-player. If users are simply searching for some content to listen to, we don’t want to block that searching experience, so that’s why the main condition to show this ad is that something has to be playing at the moment.</em></p><p><em>And the last one is a </em><strong><em>Pre-roll</em></strong><em> or a video ad, and this gets displayed when users start listening to a new station.</em></p><p><em>Now, if you’re looking at this screen, probably your first thought is “iHeartRadio has so many ads” — but that is not exactly true. The reason why I say it’s not true is because I only briefly mentioned the criteria for showing Transition Ads, but every ad has its own conditions to be displayed. There would never be a scenario when a user would see all these ads within a short period of time.</em></p><p><em>So, the first tip is: Know your users!</em></p><p><em>Before you decide what type of ad or SDK you want to integrate into your app, you need to be able to answer these questions:</em></p><ol><li><strong><em>Who is using your app</em></strong></li><li><strong><em>What are they using it for, and</em></strong></li><li><strong><em>How are they using it</em></strong></li></ol><p><em>Once you have that information, you will be able to make a better decision. You know that in the online world, everything has to be relevant. It’s always important that you observe your competitors: for sure you want to know what type of ads they’re showing, what frequency of ads they have, but that information should just help you. You should make the decision based on your users.</em></p><p><em>Individual developers can use any analytics SDK to know their users better. If you work for a larger organization, however, you may want to think about having an additional layer, such as AdOps team, which would help you target ads based on listening history and users’ demographics; and that’s exactly what we do in our company.</em></p><p><em>The next tip I want to talk about is using a Bootstrapping Service, or as we call it Client Configuration.</em></p><p><em>Bootstrapping Service is a service that delivers some specific values when the app is launching. So some of the reasons why we use this Bootstrapping Service is because it gives us the flexibility to enable or disable any SDK at any point in time; we can also change the grace period for new users, that’s the period of time when our users don’t see any ads at all; and we can also change the frequency of ads. All of this can happen on the fly.</em></p><p><em>One of the scenarios when this was extremely helpful for us, was a few months ago when we released a new feature on Prod, and for some reason one of the Ad SDKs had a bug on their end, so they were not respecting the frequency of ads. Users were listening to a song and a 30 seconds ad, another song, a 30 seconds ad again, so as you can imagine that was a very frustrating experience for our users. So what we ended up doing was: we disabled the SDK completely from using the Bootstrapping Service. That’s probably not the ideal solution but since this problem happened during the weekend, that was the best solution given the circumstances.</em></p><p><em>Also, you may want to think about doing a slow rollout of the new SDK. As you know, introducing a new SDK into your app is a risk itself, so you want to make sure that if something goes wrong with the SDK at least only a small number of your users will see the problem.</em></p><p><em>And if you already have an A/B test service, make sure that you use it. You may run a few tests, do some iterations, probably play around with the grace period, frequency of ads and so on; and once you have all that information you’ll be able to make a better decision of what combinations work best for your app.</em></p><p><em>So, this is how the Bootstrapping Service works. When the app is launching, we hit the server and we get all these values from the Bootstrapping Service. For example the first one is “grace period in minutes” which right now is 60 minutes. Our code is written in a way that these values will be respected. So if we simply change this value from 60 to 120, the next time users launch the app, this value will be received from the app and the app will not make any ad requests for 2 hours. And as I said this all happens in the fly, we didn’t need to release a new app version on the store, it’s very fast.</em></p><p><em>Tip number 3: Profiling the Ad SDKs</em></p><p><em>This is a screenshot from a few years ago when we upgraded to a new version of the AdMob SDK, and as you can see here from the screenshot, there’s a spike hitting right here whenever we were making an ad request. The bug was on the new version of the SDK, so as you can see it was always allocating memory but never releasing it. So to figure out this problem, we made a test project that was simply using the SDK. We wanted to make sure that the bug was in the new version of the SDK, so we added a test button on this sample app, and whenever we would hit that button, instead of requesting one ad as we would normally do, we were requesting one hundred ads now. After the AdMob SDK team fixed the problem, we were able to use this test app again to test the newer version of the SDK and make sure that now the memory usage is much more stable.</em></p><p><em>It’s not only important that you profile the Ads SDK but it’s also very important to profile your own app. You need to use visual memory debugger built into Xcode so that you see if there is any potential retain cycles or any problem with your own app. Also it can help you to establish a memory usage baseline.</em></p><p><em>Also it’s always a great idea to make a sample app. Not only does it help you figure out any potential issues with the SDK, but also if you see that something is wrong with the SDK, you can just use that sample app to work with the SDK team to fix the problem, or even post it on forums online if you need help from other engineers.</em></p><p><em>Next tip is: Keep an eye on crashes!</em></p><p><em>A few years ago, 8 out of 10 of the top crashes that we were seeing were WebCore crashes, so as you can see from this screenshot almost 100% of the crashes were happening on iPhone devices. That was actually the initial clue that made us think there must be something wrong with one the Ad SDKs, because we don’t display ads on iPad devices at all. Since all the crashes were happening on iPhone devices we thought there must be something wrong with one of the Ad SDKs.</em></p><p><em>The reason why all these crashes were happening, was because ads were loading and animating in the background. iOS does not allow OpenGL animations in the background and that’s why the app was crashing so much.</em></p><p><em>After we investigated a little deeper, we actually realized that all these crashes have been happening since 2015. Other engineers who had used the same SDK had reported this issue before, but since we only read the documentation of the SDK, we were not aware of the problem. As of today, this bug is still not fixed. However we were able to come up with a solution, which even though didn’t solve all the crashes, at least it reduced the number of crashes by about 60%.</em></p><p><em>The solution was very straight-forward. We are destroying the ad view when the app goes on background state, and we’re recreating the ad view when goes back into foreground state. This is how the solution looks like. We are simply adding an observer on UIApplicationDidBecomeActive notification, and when that notification gets sent we are recreating the ad view. Similarly, we are observing UIApplicationWillResignActive notification and when that gets sent, we destroy the ad view again.</em></p><p><em>This solution worked pretty well initially, but it didn’t take long for us to realize that some CarPlay users were still facing some crashes. The reason why that was happening was because our CarPlay users will plug in their phone in their cars, the screen goes black and then they continue using the CarPlay app. But in that specific scenario, UIApplicationWillResignActive notification does not get sent. So in that scenario for our CarPlay users, the ads were still not being destroyed.</em></p><p><em>To solve that problem, we are now adding another observer on UIScreenBrightnessDidChange notification, and now with this second solution, we’re not only destroying the ads when app goes into background state, but we’re also destroying the ad when the app is still in foreground state but the screen brightness is set to 0. So for us that means that our users are connected to their CarPlay device.</em></p><p><em>We all know that introducing a new SDK into your app is a huge risk itself. You didn’t write the code yourself, you don’t have the source code, so you’re simply relying on the proficiency of third party developers and testers. So make sure that you do your own research for the SDK that you decide to implement. Usually engineers tend to post problems online when they face issues with the SDKs, so even though it’s not going to solve the problem completely for you, at least you’ll be prepared for what potential issues you’re going to face after you add the SDK. Most likely you’ll be able to find some workarounds and solutions. Make sure you monitor the WebCore crashes. The example that I showed you before, we were able to catch it early on time, just because we were constantly monitoring those crashes. You can do so by using any common SDK like Fabric or New Relic.</em></p><p><em>Last but not least: Don’t crowd the screen with ads. We all know that more ads means more money, but also more ads means less happy users, or probably even less users.</em></p><p><em>This is a screenshot from a few years ago from our app. So as you can see here, half the screen is showing an upsell, and we have only 2 lines of content. There’s an ad displaying at the bottom, and then the mini-player. So the only area where users could interact with the app was this area here where we’re showing 2 lines of content. Of course the app looked better on bigger screens for sure, but as you can imagine it was not a good user experience.</em></p><p><em>Make sure you don’t let the ads outweigh the app’s service!</em></p><p><em>So to solve the problem that iPhone 4s users were facing before, we moved from Pinned Ads to Scrollable Ads. So now as you can see we’re still displaying ads but that ad is embedded within the content. One of the downsides of this solution is the fact that when we were showing Pinned Ads, of course the impression of the ad was 100 percent, obviously it was always visible on the screen. But when we switched to scrollable ad, since users can continue scrolling, at some point the ad will not be visible anymore so the impression of the ad is lower, but again that’s a decision that you need to make when you consider good user experience with regards to showing ads.</em></p><p><em>Another improvement that we made for scrollable ad, is that if for some reason the ad fails to load, this white space in the collectionView where the ad is supposed to load — that area will automatically collapse, so you will never have weird scenarios when your users see blank white spaces on the screen.</em></p><p><em>So to summarize again all the tips that we shared today:</em></p><ol><li><em>Make sure that you know your users because it’s extremely important to show relevant ads to your users.</em></li><li><em>Use a Bootstrapping Service because it can save you in difficult situations and it gives you some sort of control over the SDK that you’re adding.</em></li><li><em>Profiling Ad SDKs, because that prepares you for potential issues that you’re going to face</em></li><li><em>Keep an eye on crashes</em></li><li><em>Don’t crowd the screen with ads.</em></li></ol><p><em>That was it — I hope you learned something new today!</em></p><p><em>Questions?</em></p><ul><li><em>Thanks for the talk. I’ve also run into similar problems with the WebCore crashes, the ads loading into the background, and I was wondering when you say you’re destroying the ad view, are you removing from the superview or you’re just setting the ad to nil and the ad controller to nil. If so, do you have to reload a new ad when app comes back to the foreground?</em></li></ul><p><em>Yes, that’s correct, the second version is correct.We have to set the ad view to nil and then when the app goes back into foreground state, we’re checking if the ad view is nil, that indicates that the ad was destroyed before and we have to load another ad.</em></p><ul><li><em>You were talking about the Bootstrapping service and the bug you found on the weekend, so how did you find the bug on the weekend and how did you solve it?</em></li></ul><p><em>Yeah, so.. actually one of the mistakes that some companies make when they have a subscription service is that since they have the option to use the paid version of the app, most of the employees, internal employees at least, just upgrade their account to the paid version, right? But we try not to do that always, so we try to switch between the paid version and free version, so the example that I showed with the ads, that’s not something you can see. It’s not a crash or something that you can easily monitor, so one of our internal employees was using the app as a free user and that’s when we noticed that the ads were showing way to often, they were not respecting the frequency. So yeah it’s always a great idea to at least use the app just like your users are using it, so you can see potential issues, especially with ads.</em></p><ul><li><em>Okay, so you talked about mostly playing ads inside your own app. We use Facebook a lot, Facebook ads to sort of promote our app, our app is a paid app, and so that’s kind of the main way that we’ve been doing it. We looked at the promotions inside the App Store, so that when other apps that come up that are similar your app will be mentioned. Do you guys have any experience with Facebook or those app promotion things?</em></li></ul><p><em>Not with promotion things, no, but we use the Facebook Audience Network SDK, just for displaying the ads, banner ads in our app, but yeah, that’s pretty much it. We don’t have that experience.</em></p><ul><li><em>You mentioned the CarPlay crash and how you had to do a check on brightness, is that the preferred way to check for CarPlay being connected to the app or is there another way?</em></li></ul><p><em>Well, like I mentioned before, the problem is that that crash is still happening to this day, it’s been 3 years and the SDK team has not fixed it, so I can’t say it’s the best way of doing it, but it’s our workaround to fix the problem at least, for our CarPlay users.</em></p><ul><li><em>I had a follow up from the last question, I was wondering for the WebCore crashes, have you identified any specific ad network or like ad type that tend to cause that crash?</em></li></ul><p><em>Well, AdMob SDK was the one that was causing the crashes mostly, but like I said it’s iOS that kills the app because it doesn’t allow OpenGL animations in the background, so I wouldn’t say it’s specifically related to one SDK — as long as you have ads loading in the background or animating in the background, the app is going to crash, regardless of which SDK.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c79a571c440b" width="1" height="1" alt=""><hr><p><a href="https://tech.iheart.com/tips-and-tricks-learned-from-monetizing-iheartradios-ios-app-c79a571c440b">Tips and Tricks Learned from Monetizing iHeartRadio’s iOS app</a> was originally published in <a href="https://tech.iheart.com/">iHeartRadio Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>