<?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 Christie on Medium]]></title>
        <description><![CDATA[Stories by Christie on Medium]]></description>
        <link>https://medium.com/@christieappbot?source=rss-4cc0ad9084d7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eBXl969lAIvXKdo4zD8Liw.jpeg</url>
            <title>Stories by Christie on Medium</title>
            <link>https://medium.com/@christieappbot?source=rss-4cc0ad9084d7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:44:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@christieappbot/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[Has iOS 11 really affected star ratings?]]></title>
            <link>https://medium.com/appbot/has-ios-11-really-affected-star-ratings-d9122b8c0403?source=rss-4cc0ad9084d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9122b8c0403</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Christie]]></dc:creator>
            <pubDate>Fri, 16 Mar 2018 05:07:57 GMT</pubDate>
            <atom:updated>2018-03-16T05:07:57.199Z</atom:updated>
            <content:encoded><![CDATA[<h4>We analyzed countless lines of data to find the answer</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k4o6r0JDLtvYu8Wg5HgSWQ.jpeg" /></figure><p>Recently at Appbot, many app developers and product managers alike have been asking us how star ratings on the App Store have been impacted since the release of <a href="https://medium.com/@euginedubinin/changes-to-app-store-ratings-5e6d13aafb3e">iOS 11</a>.</p><p>The general question on everyone’s minds has been:</p><blockquote>Have star ratings really been affected by iOS 11?</blockquote><p>Our gut feeling was generally a resounding “<strong>YES!</strong>” — but we couldn’t totally <em>confirm</em> why, nor did we have any idea of the <em>scale</em> of the impact.</p><p>Wanting to explore our knee-jerk reaction deeper, we chose to evolve the initial question to:</p><blockquote>Have star ratings really improved since iOS 11?</blockquote><p>With curious minds, we set about crunching the numbers.</p><h4>ALL of the data!</h4><p>To test out our theory, we sought out ratings data from the Top 50 free iOS apps from the US store, from August 2, 2017 (just over a month before the release of iOS 11) through to March 2, 2018.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*07dKsIq8nmwEMSzwOVvcpQ.png" /><figcaption>Top 50 free iOS apps for the US. Source: <a href="https://rss.itunes.apple.com/en-us">https://rss.itunes.apple.com/en-us</a></figcaption></figure><p>We then isolated apps that appeared in the chart consistently during the period — this left us with 38 apps to play with.</p><p>The results weren’t as we expected.</p><h4>The impact on average star ratings across the board</h4><p>Here’s what the average star rating for those 37 apps over the 7 month period looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IwzNvfnLKC9YoLSezdGQdA.png" /><figcaption>Average star rating Increase since iOS 11 (Unscaled)</figcaption></figure><p>This didn’t really tell us a lot. We may have been a bit optimistic.</p><p>So, we decided to zoom in on the y axis (stars) a little.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y1DvZBg1MaP75Frwc07IkQ.png" /><figcaption>Average star rating Increase since iOS 11 (Scaled)</figcaption></figure><p>Ah-ha. What we saw here was a modest, but steady, increase over the course of 7 months. Whilst the change wasn’t as abrupt as we first expected, the closer look meant our hypothesis wasn’t completely without support.</p><p>Based on the average star rating of our whole data set, Top Free apps have seen an average increase of 0.12 stars or 3% since iOS 11.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/351/1*164ZyvvswV8KBZb4580eVQ.png" /><figcaption>Average raw stars and percentage increase since iOS 11</figcaption></figure><p>The increase is small, but for an app that is sitting at 3.9 stars, it’s enough to push it into 4 star territory, or a 4.9 to a 5.</p><h4>The impact on rating count across the board</h4><p>Now, we know that the average star ratings have grown in a modestly positive direction in the previous 7 months, but what about the overall ratings counts?</p><p>This was where we discovered that the REAL changes have occurred.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*775kD2-Edcx1l4vpCXyeXg.png" /><figcaption>Rating count per day for apps in our sample since iOS 11</figcaption></figure><p>On the graph above we see an immense peak in rating count volume around the release of iOS 11, and a higher general rating count in the following months, compared to the time before iOS 11 was rolled out. That’s quite a spike!</p><p>Looking deeper at the data, the overall rating counts for the months at the start and the end of the time period show the following results:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/353/1*jkdUxDbfU1fykmF4PbwN2g.png" /><figcaption>Overall rating count comparison</figcaption></figure><p>That means the count of ratings in the last month of the period increased by 132% from the first month of the period (roughly a month before iOS 11 was released)<strong>.</strong></p><p>This has also translated to a average rating count increase, in this group alone, per app, of over 37,000 more ratings per month. Not bad at all!</p><p>So, our inkling about an overall improvement to ratings <em>appeared</em> to be correct — but what had prompted our hunch in the first place, and what did it mean for individual apps?</p><h4>The power of the ratings prompt?</h4><p>Our suspicions were initially based on <a href="https://medium.com/@clementdelangue?source=post_header_lockup">Clément Delangue</a>’s theory that the <a href="https://9to5mac.com/2017/06/09/app-rating-custom-prompts-app-store-banned/"><strong>native iOS ratings prompt</strong></a><strong>, </strong>introduced in iOS 10.3, but heavily utilized by developers from the start of iOS 11,<strong> </strong><a href="https://medium.com/huggingface/instagram-doubled-its-ios-reviews-in-a-week-thanks-to-this-new-in-app-review-popup-52333d4f4ce6">may be positively impacting app ratings</a>.</p><p>On the surface, we could see this theory holding true in many cases.</p><p>Our CEO, <a href="https://stories.appbot.co/@stuartkhall">Stuart</a>, for instance, introduced the native iOS ratings prompt when he updated his Wordboard app for iOS 11 — since then he has noticed a jump in both the number of ratings and average stars.</p><p>We‘ve also seen that the r<a href="https://stories.appbot.co/my-ios-ratings-prompt-verdict-4bcc0a834358">atings prompt worked insanely well for Instagram</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*BzdSNrlMCeRc25YvbEnVfg.png" /><figcaption>Image Credit: <a href="https://stories.appbot.co/my-ios-ratings-prompt-verdict-4bcc0a834358">https://stories.appbot.co/my-ios-ratings-prompt-verdict-4bcc0a834358</a></figcaption></figure><p>If this was happening for a couple of apps, surely it could be for more. This group could be what was caused the en masse increase that we saw earlier.</p><p>After some contemplation, this then lead us to our next question:</p><blockquote>Did apps that used the new prompt get better results?</blockquote><p>To answer that, we had to be able to spot them.</p><h4>Who do we think implemented the prompt successfully?</h4><p>Although it wasn’t clear who exactly implemented the ratings prompt successfully or at what time, there was a handful of apps we found that had enough rapid average star rating and rating count increase to presume the prompt was responsible.</p><p>Across the 7 month time period, we found 12 apps with an average star rating increase higher than the average star rating increase of 3.08% across the cohort:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LJVkTXf2vmCMpCLiCcHguA.png" /></figure><p>We were blown away by the swift escalations in all of the star rating trend-lines at various points in the time since we assume the prompt was first introduced in the apps. Although the peaks could be as a result of changes to the apps themselves in some instances, it’s a fairly big coincidence if that is the case in all instances.</p><h4>So, have star ratings really gone up since iOS 11?</h4><p>Based on the data above, it appears that ratings (both average stars and counts) are indeed improving for the better since iOS 11, largely, we suspect, thanks to the implementation of the native ratings prompt by many developers.</p><p>If you’re going to give it a go, think about where your prompt is placed in the app. The prompt below was received after completing a successful complete activity in the app, so why not follow suit and punctuate a success or milestone in your app with the prompt — you may just skyrocket your ratings!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*N8ZJn1ySs1ZnYyqD-eVo8w.png" /></figure><p><em>Like this? Let us know!👏👏👏</em></p><h4>About The Author</h4><p>Christie is the Customer Success Lead at <a href="https://appbot.co/">Appbot</a>. You can connect with her on <a href="https://twitter.com/ChristieHunter_">Twitter</a> or <a href="https://www.linkedin.com/in/christie-hunter/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9122b8c0403" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appbot/has-ios-11-really-affected-star-ratings-d9122b8c0403">Has iOS 11 really affected star ratings?</a> was originally published in <a href="https://medium.com/appbot">Appbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2 questions every developer should answer before building a new app]]></title>
            <link>https://medium.com/appbot/2-questions-every-developer-should-answer-before-building-a-new-app-3783cba2ce94?source=rss-4cc0ad9084d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/3783cba2ce94</guid>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Christie]]></dc:creator>
            <pubDate>Thu, 01 Mar 2018 06:56:37 GMT</pubDate>
            <atom:updated>2018-03-08T05:09:12.568Z</atom:updated>
            <content:encoded><![CDATA[<h4>You might save yourself a lot of time and money</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9L5dLa7W3ULXX-JSO_Cfjg.jpeg" /></figure><p>My job is to help app developers succeed with their product, and I speak to dozens of them every day.</p><p>One of the most common questions I get asked by those whose apps are struggling to get traction is simply:</p><blockquote>“How can I get more downloads?”</blockquote><p>Often, when I take a look at their app and the reviews users are leaving, it seems like the problem comes back to a lack of honest pre-build research.</p><p>That said, it’s not always easy to know what to think about when first starting to build the product.</p><p>So, before you create the app that’s been stewing in your imagination, ask yourself these two simple questions first:</p><h4><strong>1) Is it doing anything different?</strong></h4><p>If you’re trying to be the new Instagram, Spotify, or Netflix you really, truly need to consider whether what you’re creating is actually different, unique, or whether it is simply reinventing the wheel.</p><h4><strong>2) Are people actually going to use it?</strong></h4><p>Alright, so your idea is original. Awesome! Do you know if anyone will actually want to use this app? Are you aware of a demand for what you’ve created? If you have a beta of the app, have you tested it with a target audience to ensure it’s worthwhile? A little research goes a long way.</p><h4>“Don’t be a buzzkill, why does it matter?”</h4><p>I should be clear that this isn’t to stifle your creativity — it’s one thing creating apps to flex your skills and get yourself comfortable with coding.</p><p>It’s another thing putting the app out in the market, wanting people to use your app, and especially wanting to make money off of it.</p><p>Here are 3 reasons why being honest with yourself matters:</p><h4>1) The stores</h4><p>With the news that <a href="https://www.theverge.com/2018/1/30/16951996/google-android-apps-removed-security-2017">Google removed over 700,000 apps in 2017 for a variety of reasons</a> (and is continuing to tighten these measures) and Apple acting in kind, you’ve got to be sure your app is watertight so it gets into the hands of your intended users in the first place.</p><h4>2) The flooded market</h4><p>There’s nothing worse than seeing apps drown because they’re competing in a space they never had a chance in. Crowding the stores with an app trying to get in on a market that <a href="http://andrewchen.co/growth-is-getting-hard/">is heavily dominated and fairly content</a> is fairly futile if you’re not careful.</p><h4>3) The users</h4><p>Surely you know the feeling: there’s really nothing worse than downloading an unoriginal, poorly designed, or altogether unusable app. You don’t want to annoy the very people you’ve created the product for. Plus, your <a href="https://www.androidauthority.com/77-percent-users-dont-use-an-app-after-three-days-678107/">users won’t be patient for long if they’re not happy.</a></p><h4>Don’t be discouraged</h4><p>It’s so important to be circumspect and mindful before powering ahead with an idea to ensure those things don’t happen, and so you don’t lose any of your hard-earned money.</p><p>The world is full of rich and exciting apps, and we need more of them.</p><p>Just make sure yours is worth the work.</p><p><em>Like this? Let me know!👏👏👏</em></p><h4>About The Author</h4><p>Christie is the Customer Success Lead at <a href="https://appbot.co/">Appbot</a>. You can connect with her on <a href="https://twitter.com/ChristieHunter_">Twitter</a> or <a href="https://www.linkedin.com/in/christie-hunter/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3783cba2ce94" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appbot/2-questions-every-developer-should-answer-before-building-a-new-app-3783cba2ce94">2 questions every developer should answer before building a new app</a> was originally published in <a href="https://medium.com/appbot">Appbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good app? Bad app? Why you should take the time to review the apps that you use]]></title>
            <link>https://medium.com/appbot/good-app-bad-app-why-you-should-review-the-apps-that-you-use-f263923e9ceb?source=rss-4cc0ad9084d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/f263923e9ceb</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[review]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Christie]]></dc:creator>
            <pubDate>Tue, 27 Feb 2018 07:47:06 GMT</pubDate>
            <atom:updated>2018-02-27T09:24:59.744Z</atom:updated>
            <content:encoded><![CDATA[<h4>It makes a bigger difference than you might think.</h4><p>Historically, I didn’t really care about leaving reviews and ratings in the app stores. Why would I? The people that make apps are going to do what they want regardless of what I say, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*9sr7jSjcXzQQMJxmcebp-w.jpeg" /></figure><p><strong>EH, wrong.</strong></p><p>I’m not saying this applies to every app developer out there, there are some that simply don’t care about their users’ opinions.</p><p><strong>However, as I’ve discovered, the majority do truly care and <em>are reliant</em> upon feedback from their users</strong>.</p><p>In fact, it’s surprising just how eagerly app developers are actively seeking comment from users to help them improve their products.</p><p>You can see evidence of this all over the internet — there are many great posts like <a href="https://www.apptamin.com/blog/getting-feedback/">this one</a> offering advice to developers on how to get more feedback. They’re even asking this question on forums, like <a href="https://www.quora.com/What-are-the-different-ways-for-mobile-app-developers-to-get-feedback-from-their-users">Quora</a>.</p><p>But what does this mean for you, the user? Why does it matter?</p><p>Well, as with democracy, although not perfect, so too it is with app development. Think of voting for your Head of State, or favourite performer on a singing show: you may think your vote doesn’t count, but every vote does count, and the results are ultimately reflective of the will of the people. With enough people like you sharing their thoughts, there is the chance to make a difference as a collective to improve what the output is like — and apps are just the same.</p><p>Is there something bugging you? Is there something you’d like to see built that would make your experience so much better? Take the time to leave a 20 second review, requesting the changes you’d like to see.</p><p>Developers all over the world are spending time and money aggregating all of these types of reviews (good and bad) they receive each day, reading through and analysing what their users want and how they’re feeling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*zOHNiK7RXEozCiDp16D9RQ.jpeg" /></figure><p>Some larger app developers have entire teams dedicated to working out what is making their customers tick, how to make their users happy, and what direction to take their app in as a result.</p><p>Learning this has really driven home to me that I need to take the time to give my feedback to the people who create the apps that I spend hours in daily, even if it’s just sending through a rating.</p><p>So, every now and then, I take a minute to do so — especially the apps that I love to use. I‘ve learned that it’s important to help great apps get noticed when there are so many in the stores, and also to give eagerly listening developers some acknowledgement of the positive impact their product is having if it really is doing so.</p><p>You’ve got the power to help create your everyday app experiences, so why not start sharing your voice now?</p><p><em>Like this? Let me know!👏👏👏</em></p><h4>About The Author</h4><p>Christie is the Customer Success Lead at <a href="https://appbot.co/">Appbot</a>. You can connect with her on <a href="https://twitter.com/ChristieHunter_">Twitter</a> or <a href="https://www.linkedin.com/in/christie-hunter/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f263923e9ceb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appbot/good-app-bad-app-why-you-should-review-the-apps-that-you-use-f263923e9ceb">Good app? Bad app? Why you should take the time to review the apps that you use</a> was originally published in <a href="https://medium.com/appbot">Appbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hey, support teams: are you asking your customers questions?]]></title>
            <link>https://medium.com/appbot/hey-support-teams-are-you-asking-your-customers-questions-bbf007bedd30?source=rss-4cc0ad9084d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbf007bedd30</guid>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[customer-support]]></category>
            <category><![CDATA[tech-support]]></category>
            <dc:creator><![CDATA[Christie]]></dc:creator>
            <pubDate>Tue, 20 Feb 2018 00:58:40 GMT</pubDate>
            <atom:updated>2018-02-20T00:58:40.776Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>This small philosophical shift unlocks BIG opportunities.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*7dLwSjc-iXp7fLeuZvU-WQ.jpeg" /></figure><p>The requirement for organisations to better understand their customers’ wants and needs has never been greater.</p><p>In modern markets where every industry is flooded with competitors and disruptors, ensuring all of your customer-facing teams are doing their best to not only understand but nurture your customers is <a href="https://www.reforge.com/blog/retention-engagement-growth-silent-killer">critical to retention and sustainability</a>.</p><p>However, the greatest part that about things like customer service is that it’s often the little philosophies that have the biggest impact.</p><p><strong>One of the best pieces of advice I’ve ever received is simple, but so often under-utilised:</strong></p><p><strong><em>Want people to talk to you? Ask them questions.</em></strong></p><p>Stating the obvious? Yeah, it may seem so, but in fact, we tend to do it far less that we probably should.</p><p>When we’re drowning in tickets, customer interactions, users reviews, or any other source of feedback, it can be so very easy to want to fix the problem they’re having swiftly and to move on immediately to our next task.</p><p>Sometimes that means we miss what people are <em>really</em> thinking or feeling.</p><p>Even if it’s positive feedback, we may get so excited by receiving it that we miss out on the richness of the provider’s full views.</p><p>We shouldn’t let self-imposed time limitations or things that may make us uncomfortable hold us back from exercising our curiosity with the discussions with have with our clients.</p><p>Now, I don’t mean we get clingy (‘whatcha thinkin’ ‘bout?’) or that we ask obvious questions (‘so, when you’ve got a problem with your browser, is your computer turned on?’).</p><p>Here are 4 helpful examples of how to put this into practice:</p><ul><li>If a customer contacts your support channel with an issue with a part of the product or service they’re using, asking “what is your use case?”, if their context isn’t immediately obvious, may be one way to get to understand their situation more clearly, and reach a better outcome to their issue</li><li>If a customer has left a complaint about your app (for instance), <a href="https://support.appbot.co/help-docs/best-practices-replying-to-ios-and-google-play-reviews/">asking them for more information in a private or one-on-one channel allows them to vent</a>. Questions so simple as “Hey John, sorry to hear you’re having trouble! Can you email us at email@email.com with more information?” allows you to better understand what their issues are and address them accordingly</li><li>If they’ve left you positive feedback, asking them “what do you like most about the product or service?” is a great source of positive reinforcement for your product/management team, as well as assets for marketing materials (and maybe, with permission, a sneaky testimonial)</li><li>Better yet, in the case where you have a client who is feeling very negative and emotional in their communication, <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3596240/">asking them questions affords the opportunity for them to unpack what they’re feeling and better yet</a>, feel completely and utterly heard, so long as you reply with empathy, and with a constructive solution moving forward.</li></ul><p>I can’t tell you the amount of times I’ve stopped myself from moving on from a conversation quickly, taken the time to ask a question, and have been blown away by the willingness of a customer to talk, and the gems that they’ve shared.</p><p>Bear in mind, with great questions comes great responsibility, so be prepared to take the time to talk to the users who take the time with you (within reason, but you’ll know what that looks like for your organisation).</p><p>It’ll be worth it though — time that you invest in asking your users questions could be your greatest retention tool.</p><p><em>Like this? Let me know!👏👏👏</em></p><h4>About The Author</h4><p>Christie is the Customer Success Lead at <a href="https://appbot.co/">Appbot</a>. You can connect with her on <a href="https://twitter.com/ChristieHunter_">Twitter</a> or <a href="https://www.linkedin.com/in/christie-hunter/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbf007bedd30" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appbot/hey-support-teams-are-you-asking-your-customers-questions-bbf007bedd30">Hey, support teams: are you asking your customers questions?</a> was originally published in <a href="https://medium.com/appbot">Appbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Know thy app regulations!]]></title>
            <link>https://medium.com/appbot/know-thy-app-regulations-454c8114c38f?source=rss-4cc0ad9084d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/454c8114c38f</guid>
            <category><![CDATA[regulation]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Christie]]></dc:creator>
            <pubDate>Fri, 16 Feb 2018 00:34:33 GMT</pubDate>
            <atom:updated>2018-02-19T07:27:30.419Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Before you develop your app, you should read this.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*BzFQBwKPMQGADcrBWR4mPA.jpeg" /></figure><p>Are you compliant with all of the regulations relevant to your app?</p><p>Now, before you roll your eyes, I don’t <em>just</em> mean the rules of the relevant stores (but those <em>are</em> still pretty important).</p><p>With more apps being developed and used, more and more governing bodies are stepping in and enforcing their rules to ensure there is order in the apps that fall into their realm.</p><p>Some of these rules are simply cross channel (relating to any avenue of the industry, whether the output is apps or not), and some of these have been cultivated specifically to tackle the app world.</p><ol><li><strong>App Store Store Terms and Conditions</strong></li></ol><p>To state the obvious, both the <a href="https://developer.apple.com/terms/">Apple</a> and <a href="https://play.google.com/about/developer-content-policy/#!?modal_active=none">Google Play</a> stores have fairly stringent rules surrounding what you can and cannot do with your app.</p><p>There is a vast list of things that may get your<a href="https://developer.apple.com/app-store/review/rejections/"> app rejected</a> or <a href="https://support.google.com/googleplay/android-developer/answer/2477981?hl=en">pulled down</a> from the stores by the powers that be.</p><p>These guidelines are fairly well designed to ensure the content put out into the stores is relevant, valuable, and not violating any user privacy, security, or so on.</p><p>Reading through the expectations of the stores will not only mean you don’t waste your time building something that will just be rejected, but it will also mean that you’re going to have a sleeker app and smoother launch because of it.</p><p>Not all rules are there to restrict what you’re allowed to do — some are guidelines are there to ensure you <em>do things right</em> as well.</p><p>Who doesn’t want to be successful?</p><p><strong>2. Regional Laws</strong></p><p>This is where it gets a little interesting. Depending on your region, you may find that there is a greater and greater push for executive-level regulation of the local app economy.</p><p>Although there are limitations in power that governments can have (because internet), at the very least you need to be aware of the limitations that may be placed on you under relevant general consumer and privacy laws for where you are located, for which you are entirely accountable.</p><p>For instance, such guides have been developed for <a href="https://www.oaic.gov.au/agencies-and-organisations/guides/guide-for-mobile-app-developers">Australian devs</a> and for those <a href="https://www.eugdpr.org/">in the EU</a>.</p><p><strong>3. Industry Regulations</strong></p><p>At least once a month in my role at Appbot I speak with a different group of developers about the rules and restrictions placed upon them based on the industry in which they operate. The most common examples of these have been in the <a href="http://www.finra.org/industry/rule4530">banking</a> and <a href="https://www.hhs.gov/hipaa/for-professionals/special-topics/developer-portal/index.html">health</a> industries.</p><p>Understandably, the risk associated with the data is huge, and the regulations are in place to mitigate the chances of things going wrong in a very public way.</p><p>Although your app may not fall into a category with such high risk, it is always good to be mindful of what could implications your app <em>could</em> have. Using that as a jumping off point, you will then be able to look into what industry you may fall into, and potential areas you may need to tighten in your app to ensure it is seamless.</p><p><strong>How to make sure you don’t get into trouble</strong></p><p>First and foremost, and I can’t stress this enough: don’t do anything outrightly illegal. This is a sure-fire way to not only get yourself banned from the store, but you could get into far greater strife if you go too far down the wrong path. Check yo’self.</p><p>Secondly: research, research, research. Google is your best friend, and reading through a few pages of the resources so readily available in the internet will serve as a massive protection. This is something that requires prudence, but the energy you spend on this could serve as a solid safety net for you (and your users) in the future.</p><p>Thirdly, if you’re still unclear, contact someone trained in this, like a lawyer with specialisation in internet law or with commercial law experience in your region/industry.</p><p><strong>When it comes to creating your app, it’s better to be safe than sorry. Erring on the side of caution can ensure that you proceed with peace of mind knowing you’ll be doing the right thing, and are affording your users the protection that they deserve.</strong></p><p><em>Like this? Please clap to let me know!👏👏👏</em></p><h4>About The Author</h4><p>Christie is the Customer Success Lead at <a href="https://appbot.co/">Appbot</a>. You can connect with her on <a href="https://twitter.com/ChristieHunter_">Twitter</a> or <a href="https://www.linkedin.com/in/christie-hunter/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=454c8114c38f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appbot/know-thy-app-regulations-454c8114c38f">Know thy app regulations!</a> was originally published in <a href="https://medium.com/appbot">Appbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 powerful steps to fixing your broken app]]></title>
            <link>https://medium.com/appbot/https-stories-appbot-co-6-powerful-steps-to-fixing-your-broken-app-6485b590e528?source=rss-4cc0ad9084d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/6485b590e528</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[app-development]]></category>
            <dc:creator><![CDATA[Christie]]></dc:creator>
            <pubDate>Tue, 13 Feb 2018 07:01:08 GMT</pubDate>
            <atom:updated>2018-02-19T07:28:59.267Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Do not panic. I repeat: do not panic.</em></h4><p>I’ve seen some pretty stellar apps, aaaannnd I’ve seen some pretty messed up apps.</p><p>Part of my job is providing meta-analyses of app review data for some of the world’s biggest developers. I’m able to study their reviews at scale, give them (their customer service teams, marketing teams, etc) a chance to understand the trends in their users’ feedback, and to help them ascertain what to do next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bQ-s50nhlNfCwwU5OvuoqQ.jpeg" /></figure><p>As a result of this work, I’ve been able to see many organisations go through the ebbs and flows of the app world: a bug/issue occurs, the rise of negative feedback, the efforts to address the issue, then the levelling back to baseline once the problems have been dealt with.</p><p>I can assure you, it happens to the best of them.</p><p>It doesn’t always go to plan though, and I have seen some apps bottom out to the point of their developers shutting their doors. It’s sad when this happens, especially when they’ve exhausted every avenue to keep operations going.</p><p>To save you ending up in the app dev graveyard, and to help you recover quickly from a bad patch, I’ve put together a list of what can be done to save yourself. It’s by no means exhaustive, but it aims to provide a rough guideline to follow amidst the panic that may ensue when things suddenly don’t go to plan.</p><ol><li><strong>Find the problem(s)</strong></li></ol><p>Sometimes the problem is blatantly, and instantly, obvious.</p><p>Recently, I saw an app with a huge spike in negative reviews — far more than usual. Turns out, as I isolated my focus on the time frame in question, I saw that the vast majority of reviews left for the app were complaining about a huge update-related issue. It didn’t take a lot of reading to see that the problem was screaming to be heard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*orh3qvh1XfnkXajE-RawUw.png" /><figcaption><em>Review Volume and Sentiment Over 6 Months</em></figcaption></figure><p>Then, sometimes the advent of an issue is more pernicious — a low trickle of issues hitting users one by one, just enough to impact their experience, and put them off the app.</p><p>I saw this with one company recently who were experiencing a decline in review volume and their rating, but couldn’t work out why. When I took a deeper look at their reviews over time I could see that some users had a bug where they were being asked to update the app when there were none available, and yet they couldn’t proceed in the app without doing so. This happened slowly but surely over time, enough to just fall under the radar — a passive problem, hushed, when there were other matters in the app that elicited greater focus.</p><p>It’s not always even about a bug or an update issue — sometimes a feature of the product irks your users, and they wind up frustrated over time.</p><p><a href="https://stories.appbot.co/are-successful-app-redesigns-even-possible-1a4d4811596">Redesigns are also a common cause of a sudden escalation in negative feedback</a>.</p><p>Regardless of what you choose to research with, ensuring that you’re monitoring your reviews and tracking their evolution is a must if you’re managing reviews at scale. At the very least, if you only get a couple of reviews at a time, simply reading through them as they come through will help you keep tabs on user satisfaction.</p><p><strong>2</strong>. <strong>Prioritise</strong></p><p>Sometimes issues can be fixed or tweaks can be made alongside your normal workload. Sometimes things will need to be put on hold to fix an issue. This means time, this means money.</p><p>It sucks.</p><p>But, what will suck more is losing the user-base that you’ve worked so hard to acquire in the first place. In fact, losing a user has the potential to <a href="https://www.invespcro.com/blog/customer-acquisition-retention/">cost you far more money in the long run</a>.</p><p>Prioritisation, then, is key. Focus on the biggest issue at hand, and if you have the opportunity to knock out some ‘quick wins’ (easy ‘fix and ship’ issues) while you’re at it, then do them too.</p><p>The key here is to not get carried away by the issues that don’t matter.</p><p>Don’t completely redesign the app in response to an issue (unless things are <em>really</em> bad), don’t focus on fixing every single issue with your app all at once just for the sake of it, and definitely don’t get carried away by anything that isn’t critical. Use downtime periods for that.</p><p>Write a list of steps that need to be taken, determine how much time is needed, work out who needs to address what issue, and then you can begin to actually sort the problem out.</p><p><strong>3. Communicate</strong></p><p>A big thing you need to remember is to communicate with your team about what has happened, the impact, and what needs to be done, if it has the potential to impact your interaction with them or the ability to reach your deadlines.</p><p>If it’s just you, then this is obviously not an issue, but in a bigger team you need to share what is happening with all key stakeholders so that they can make allowances and adjust their expectations accordingly. This is a critical part of prioritisation that people forget to do amidst a fluster — simply talking with their teammates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HM4TNmMdnrbyS1aP8Ugd4A.jpeg" /></figure><p>At times, you may need to ask your users for more information, if the issue or solution isn’t clear. The reply functionality offered in the stores is a great way to elicit this information from your users — <a href="https://support.appbot.co/help-docs/best-practices-replying-to-ios-and-google-play-reviews/">asking them questions and to elaborate further will mean you can better understand the context of the issues, or their frustrations</a>.</p><p><strong>4. Fix</strong></p><p>Look — you’re going to be stressed, but keeping your cool and thinking of the fix as an ‘unanticipated project’ may be one way to manage the feelings that come with the situation.</p><p>Whether it could have been prevented or not, what is done is done, and focus must be on fixing the issue with a clear head, rather than letting the circumstance consume you.</p><p>You know what you need to do.</p><p>Do so calmly, methodically, and prepare to problem solve your little heart out.</p><p>Once complete, send that update out.</p><p><strong>5. Reach out</strong></p><p>Importantly, you need to tell your customers that you’ve heard them.</p><p>Whether it is replying to reviews, as mentioned above, or whether it’s just publishing <a href="https://stories.appbot.co/stop-f-ing-up-your-release-notes-4c0a2bace108">some comprehensive release notes</a>, you simply must be transparent with your users and make them feel validated and heard, and that you’ve fixed the problem.</p><p>If the issue was critical enough, outrightly promoting to your users that you’ve fixed the problem may be the only way they’re actually going to know you’ve fixed it if they’ve already abandoned ship — as such, social media or remarketing may be your best friend.</p><p><strong>6. Don’t forget the post mortem</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*L6Y-lbRAiSg2h0GJsjkI6g.jpeg" /></figure><p>You’ve worked hard now, it’s been frustrating, but you did it!</p><p><em>Go get yourself a doughnut and a coffee.</em></p><p>Important, there are things you must do to move on:</p><p>Briefly analyse what went wrong, how to prevent it, how you fixed it, how to maintain the fix, and make sure that you allow it to serve it as a motivator to be extra diligent with your work moving forward.</p><p>We ALL need that reminder from time to time. It’s not always your fault, of course. BUT, an extra bit of thought into ensuring things are watertight never hurt anyone.</p><p>Provide a summary to your team, if you have one, letting them know (in probably as little detail, but as comprehensively as possible) what happened, how you fixed it, and how you’ll prevent it in the future.</p><p>The next step is the most satisfying one: integrate the project into your standard monitoring tools, and commence business as usual.</p><p><strong>Alas! You got through it. Maybe with a few battle scars, but you did it. Don’t let it get you down, this is what wisdom is made of.</strong></p><p><strong><em>You’re a dead set legend 🤘</em></strong></p><p><strong>Side note</strong></p><p>I should point out that when it comes to UX or UI overhauls in particular, your users are almost ALWAYS going to have issues with them when they first get launched.</p><p>Like, always.</p><p><a href="https://stories.appbot.co/are-successful-app-redesigns-even-possible-1a4d4811596">People inherently don’t like change, and often it’ll take some warming up to the new design or way of doing things, which comes with time</a>.</p><p>The reality is, they may be initially frustrated by having to learn the new ropes, but people often just need time to get used to things.</p><p>BUT, what <em>IS</em> an issue is when the app is literally unusable.</p><p>Make sure, in preparation for a UX/UI redesign launch that you thoroughly test with objective parties, so you can make sure you’re not hiding any features that are critical to users, making their workflow more clunky, or omitting a critical part of your product for no good reason.</p><p>Another good way to check this, and test out workflows is to use an analytics tool like <a href="https://heapanalytics.com/">Heap</a>, or the like, to get to know your customer’s workflows and key features, to better inform your decision before acting on it.</p><p><em>Like this? Please clap to let me know!👏👏👏</em></p><h4>About The Author</h4><p>Christie is the Customer Success Lead at <a href="https://appbot.co/">Appbot</a>. You can connect with her on <a href="https://twitter.com/ChristieHunter_">Twitter</a> or <a href="https://www.linkedin.com/in/christie-hunter/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6485b590e528" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appbot/https-stories-appbot-co-6-powerful-steps-to-fixing-your-broken-app-6485b590e528">6 powerful steps to fixing your broken app</a> was originally published in <a href="https://medium.com/appbot">Appbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>