<?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[BONZA - Medium]]></title>
        <description><![CDATA[Product Group - Medium]]></description>
        <link>https://medium.com/bonza-product?source=rss----d7593900edc4---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>BONZA - Medium</title>
            <link>https://medium.com/bonza-product?source=rss----d7593900edc4---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:17:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/bonza-product" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The perils of permissions priming]]></title>
            <link>https://medium.com/bonza-product/the-perils-of-priming-for-permissions-2156ac5cbda1?source=rss----d7593900edc4---4</link>
            <guid isPermaLink="false">https://medium.com/p/2156ac5cbda1</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[engagement]]></category>
            <category><![CDATA[retention]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Dave Collins]]></dc:creator>
            <pubDate>Wed, 27 Dec 2017 15:34:10 GMT</pubDate>
            <atom:updated>2017-08-11T15:08:57.619Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Hypothesis:</em> <em>Adding on-boarding priming screens for iOS system permission requests, will increase the rate of users allowing them. This is because the priming screens will educate new users about their benefits, before being presented with the dialogues to do so e.g. Allow push notifications to be alerted about relevant content updates.</em></p><p>Results have revealed that the above assumption is false for some apps. It’s been observed that placing a permission priming screens in front of permission dialogues can impact permission allowing <strong>by up to 100%. </strong>There are a couple of theories as to why this happens.</p><h4><strong>Bypassing permissions</strong></h4><p>Firstly most permission priming screens give users the option of by-passing the actual permission dialogue, like the <a href="https://itunes.apple.com/us/app/domain-real-estate-and-property/id319908646?mt=8">Domain</a> app below, where users can tap ‘Not now’ on and completely bypass each permission dialogue, where not allowing is also an option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*4PrO0O0RzOGIJo0742LBfg@2x.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*qIomVBWk4WBxeiBxGdDR_A@2x.png" /></figure><p>We’re now seeing more apps (particularly more popular ones like the car sharing app <a href="https://itunes.apple.com/us/app/drivenow-carsharing/id435719709?mt=8">DriveNow</a>, below) doing away with permission priming screens. As a result their on-boarding experience is fairly terse, but no doubt optimised towards conversion of the their iOS permissions. One could also presume that popular apps have stronger brand, and therefore trust attributes. This may reduce their need to essentially try and convince new users to allow permissions with primings screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*LhCZMbga-2oz7dSkzwK_tQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*c0TTqKa1F_DYsv9WlBYpLw.png" /><figcaption>DriveNow have done away with permission priming screens for their iOS on-boarding experience</figcaption></figure><h4>Contextual placement</h4><p>Another potential factor contributing to the poor performance of placing priming screens in the on-boarding flow, is that they aren&#39;t contextually placed. Some users may not get why allowing permissions is useful, despite your best efforts to explain why. During on-boarding users might be more interested at generally activating in the app e.g. doing their first search or transaction.</p><p>Perhaps a better tactic is to present permissions (for those that are yet to allow them) at the exact point in which they can be useful within the app’s experience. This way certain functionality can serve as the priming e.g. Conducting a current location search as <em>priming</em> to present the iOS location services permission. Allowing the permission in this case is actually needed to complete the task so the conversion should be much higher.</p><h4>In summary</h4><p>When permission priming screens are used in the on-boarding flows, impacts to other important conversions, like account signup and new user activation rates have also been observed.</p><p>So it is worth considering how popular your app is (active user and install base), as the more popular it is, the less likely they are needed. If not already done, considering how to contextually place permissions, to catch users who didn’t allow during on-boarding is also a worthy exercise.</p><p>If your app currently does use permission priming screens it really does pay to understand if they are impacting the rate of users allowing permissions, and other adjacent events within the on-boarding flow. Form my experience the opposite to desired effect can occur which is never good. Knowing where you stand here can be achieved by running an A/B test, with tools like <a href="https://www.optimizely.com/">Optimizely</a>, where the statistical significance of impacts are calculated on the fly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2156ac5cbda1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bonza-product/the-perils-of-priming-for-permissions-2156ac5cbda1">The perils of permissions priming</a> was originally published in <a href="https://medium.com/bonza-product">BONZA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Smarter push notification frequencies]]></title>
            <link>https://medium.com/bonza-product/smarter-push-notification-frequencies-79d97fbf6ce2?source=rss----d7593900edc4---4</link>
            <guid isPermaLink="false">https://medium.com/p/79d97fbf6ce2</guid>
            <category><![CDATA[mobile-apps]]></category>
            <category><![CDATA[engagement]]></category>
            <category><![CDATA[push-notification]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Dave Collins]]></dc:creator>
            <pubDate>Wed, 27 Dec 2017 15:30:24 GMT</pubDate>
            <atom:updated>2017-11-13T11:14:33.747Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*9ngAZRzpmd6G3BBFAGgRXw.jpeg" /></figure><h3>Solve the user need and grow the app</h3><p>Notifications are powerful. As <a href="http://www.phiture.com/">Andy Carvell</a> puts it, if you create an activity notifications topic that’s highly relevant to users, has extensive reach across your user-base, and is delivered at a healthy frequency — then expect postive impacts to user engagement and retention as shown in his <a href="https://mobilegrowthstack.com/what-is-the-mobile-growth-stack-426c6e474329">Mobile Growth Stack</a>.</p><p>In this article I wanted to dive into the topic of notifcation frequency, for even if you’ve nailed the relevance and reach with your topic, the frequency at which notifications are pushed, can make or break the whole topic.</p><h3><strong>Why move to a smarter push frequency</strong></h3><p>If your app pushes activity notifications at set intervals to subscribers, say twice daily for when new content is listed in a favourite search, our assumption is that highly engaged users, will appreciate being informed about a newly listed item in as-close-to-real-time as possible. This is because it’s <em>likely</em> these users are under pressure to enquire or transact and need to beat the clock and the competition coming from other users .</p><p>Towards the other end of the engagement spectrum, you might have a lot of users going through their initial, and sometimes prolonged discovery phase, perhaps day-dreaming about what could be, exploring multiple options and not under any significant time pressure to purchase or transact.</p><p>The challenge for apps that fit this bill, is to ensure that push notifications frequencies are altered to suit the different engagement levels of users at various stages of this spectrum.</p><h3>Approach</h3><p>Of course you could always add a notifications frequency controller within your notifications settings area, however this might not give you the desired network effect, given the awareness of settings areas is usually pretty low. An alternative is to go down the path of automatically altering notification frequencies based on user engagement levels . This type of approach of making your notifcation frequencies a little smarter, will probably have a more wide-spread effect on your user-base.</p><h3>Establishing a baseline</h3><p>First up if it could be interesting to understand the baseline impacts of straight up real-time notifications (assuming your push server and back-end systems allow real-time push), without any rules to alter the frequency depending on users engagement levels. You could achieve this by setting up an A/B test (<a href="https://blog.optimizely.com/2017/01/24/new-mobile-sdks-available-optimizely-x/">Optimizely X</a> works great for native apps) to understand this effect, compared to a control group that continues to receive notifications at your current set frequently (twice daily, this is pretty common).</p><p>Some goals for the test could be;</p><ul><li><strong>Notification volume and conversion rate</strong></li><li><strong>App sessions / app sessions per user</strong></li><li><strong>Customer enquiry</strong></li><li><strong>Notification disables (in-app topic and notification permission levels)</strong></li><li><strong>App uninstalls</strong></li></ul><p>To summarise your baseline test, you should expect to see an increase in push volume, and despite a negative impact to the notification conversion rate, you’ll most likely start to see an immediate increase in sessions (more from the same users). But of course, you’ll probably be brining user into the app, too frequently, so expect to see a negative impact on key engagement metrics like customer enquiry rates, compared to the control group. You may also see a spike in notifications opt-outs and app uninstalls. Don’t be to alarmed here, remember that these impacts should be quarantined within the safety of your experiment. The value in doing this is that it give you important insights to work with and improve.</p><h3>Now to try introducing some smarts</h3><p>Not every mobile developer has access to their own Machine Learning capability to automatically segment users who should receive notifications at different frequencies (maybe <a href="https://firebase.google.com/docs/predictions/">Firebase Predictions</a> could change the game here?). So start with some simple logic to change the real-time frequency back to your set internal. This could be triggered by certain postitive or negative user events . For example, say a user swiped away the notification or they didn’t enter the app after sending a certain amount of notifications. You may find that despite altering notification frequencies based on these fairly simple signals, the impact to your goals could be significant.</p><p>Relative to the raw real-time experiment results, your slightly smarter notifications should improve the notification conversion rate, improve customer engagement metrics and have an even higher potential for sessions growth. This is because you should see less notification opt outs and less app uninstalls, due to the notifcation frequency backing off for the less engaged segment of users, who’d be the highest risk churners. You’d essentially be retaining more of your audience as your notifications would be responding appropriately to their engagement levels, albeit basically.</p><h3>Getting the balance right</h3><p>The long-term goal is to send notifications at a frequency relative to user engagement levels. If you get this right you should be able to maximise sessions growth, whilst not impacting customer enquiry rates, notification opt outs or app uninstalls — you might even be able to reduce the latter metrics and really get the best from both worlds.</p><p>Achieving this would require ongoing commitment and fine-tuning of your rules. Perhaps aim for a method that allows for server-side configuration to minimize your overheads and to prevent being dependant on app versions to deploy updates. The other advantage with this approach would be consistent behaviour for your iOS and Android notifications (if you have apps for both platforms).</p><p>Perhaps the best-case scenario is that the insights gained from your experiments help sell the even greater growth potential that could be realised through an investment in an approach involving more advanced Machine Learning capability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79d97fbf6ce2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bonza-product/smarter-push-notification-frequencies-79d97fbf6ce2">Smarter push notification frequencies</a> was originally published in <a href="https://medium.com/bonza-product">BONZA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>