<?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 Neil Mathew on Medium]]></title>
        <description><![CDATA[Stories by Neil Mathew on Medium]]></description>
        <link>https://medium.com/@metalwihen?source=rss-aab0d1af7441------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*p0kpLiE8ikCplUof.jpeg</url>
            <title>Stories by Neil Mathew on Medium</title>
            <link>https://medium.com/@metalwihen?source=rss-aab0d1af7441------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:11:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@metalwihen/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[Why your Push Notifications never see the light of day]]></title>
            <link>https://medium.com/free-code-camp/why-your-push-notifications-never-see-the-light-of-day-3fa297520793?source=rss-aab0d1af7441------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fa297520793</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[push-notification]]></category>
            <category><![CDATA[androiddev]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Neil Mathew]]></dc:creator>
            <pubDate>Sat, 28 Oct 2017 18:55:46 GMT</pubDate>
            <atom:updated>2018-01-10T08:08:53.408Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1KfeXO-IedHQ9cUI83cV3g.jpeg" /></figure><h4>Push Notifications fail on specific Android phones. Here’s why.</h4><p>I recently added support for <a href="https://firebase.google.com/docs/cloud-messaging/">Push Notifications</a> in the <a href="https://play.google.com/store/apps/details?id=com.kayako.android.k5">Kayako App</a>. I tested and shipped it. And I thought I did pretty good job.</p><p>But then one by one, my users start commenting that the the app doesn’t show any notifications about 95% of the time. At first, I thought it was a mistake because the Push Notifications were working as intended on my emulator and devices. But as I dug deeper, it became clear how serious and valid this problem was. This was but the tip of the iceberg. Close to 50% of our Android app users were affected but only few informed us about it.</p><h3>So, what’s the problem?</h3><p>Push Notifications are <strong>not</strong> working properly on specific Android phones.</p><p>I use the word ‘properly’ because users receive push notifications when the app is open but <a href="https://github.com/firebase/quickstart-android/issues/41">not when it is closed</a>, which defeats the purpose of push notifications.</p><p>I use the words ‘specific Android phones’ because this issue is noticed only on phones by manufacturers like Xiaomi, Oppo, One Plus, Vivo, Lenovo, Huawei, Samsung, and a few others.</p><h3>Why is this happening and how do we fix it?</h3><p>To understand the problem, let’s first understand the Android UI and the expected behavior of Push Notifications.</p><p>On Android, we have three buttons at the bottom as part of the Navigation Bar. The square button, on click, opens the <strong>Recents</strong> screen. The <strong>Recents </strong>screen lists all the ongoing tasks or apps recently opened. We can clear these applications at any time, as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/1*XEtNqABphvIvKN8VSTq8QA.gif" /><figcaption>Recents Screen</figcaption></figure><p>Yet on certain <a href="https://www.xda-developers.com/what-is-custom-rom-android/">stock ROMs</a> (Android operating system customized by device manufacturers), clearing an application kills that application and its background services. This is bad because we need background services to show Push Notifications.</p><p>When the server informs the Android device of a new Push Notification, it would normally re-start the application’s background services to show the notification to the user. That’s good because background services will automatically start to show push notifications.</p><p>The image below shows the expected behavior which is the case for vanilla ROMs. This is the original Android firmware that is not customized by manufacturers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*75GUN09vdpH5zQKuQqOoWw.gif" /><figcaption>Expected Push Notification Behavior</figcaption></figure><p>Yet despite this, some Android phones using the Kayako app are <strong>not</strong> receiving Push Notifications when the app is cleared from <strong>Recents</strong> screen. The reason is that phone manufacturers like Oppo, Xiaomi, and One Plus use a stock ROM that disables the re-starting of background services for most apps. This is bad because we’re back to where we started with no way to show Push Notifications.</p><p>Thankfully, these stock ROMs have a Settings page to enable the re-starting of background services. Although the auto-starting of background services are disabled by default, users can manually enable this feature by following some instructions. This is good because now background services can be automatically started to show Push Notifications. But, it’s an ugly solution because it involves some manual work that the user has to do.</p><p>The intentions of the manufacturers are to conserve battery and improve performance. The app users now have to open their settings app, navigate to the correct page, scroll through a list of apps, and then enable the feature for the Kayako app.</p><h4>But wait, why don’t apps like Gmail and Slack have these problems?</h4><p>Top-popular apps like Gmail, Slack and Whatsapp are whitelisted by these stock ROMs. That means these apps have auto-launch enabled for them by default.</p><p>However our app, along with many many others, have auto-launch disabled by default.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/1*3HnDu4uXzuAEP_Ga1oRXwA.png" /><figcaption>One Plus ‘Apps auto-launch’ Settings page</figcaption></figure><h4>I can’t find the settings to enable auto-launch. Where are they located?</h4><p>The steps to enable auto-launch for an app are different for different manufacturers. This is because this is not a native Android feature and is very specific to stock ROMs.</p><p>It should also be noted that the terminology used by each manufacturer is different. The auto-launch feature can be referred to as app auto-start, start-up manager, auto-start manager, app optimisation, protected apps, or background app management.</p><p>To make matters worse, the auto-launch settings page is not easy to find. For One Plus devices (using <a href="https://www.android.com/versions/nougat-7-0/">Nougat</a> or below), you need to open up Settings, click Apps, then the gear icon located on the toolbar, and then Apps Auto-launch under the Advanced sub-category at the very bottom.</p><h3>Alright, what’s the solution?</h3><p>In the end, the user will have to perform the steps manually. This can not be programmatically enabled for all devices. The best we can do is to make it as easy as possible for app users to do so.</p><h4>Create a support article</h4><p><a href="https://medium.com/u/a7348f7b8ea0">Kelly O’Brien</a> and I wrote an article which makes an attempt to identify all the device manufacturers with this problem and explain the steps to enable Push Notifications on those devices. You can read about it <a href="https://support.kayako.com/article/1461-why-aren-t-push-notifications-working-on-my-android-app">here</a>.</p><h4>Inform users in-app</h4><p>As I mentioned before, not everyone takes the time out to complain. I can not expect users to contact the support team or search for the support article online. At the same time, there’s no easy way to automatically identify if Push Notifications aren’t working when the app is closed.</p><p>I decided to show a small footer on the Push Notifications Settings page where the article is available to the user at all times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/437/1*fC666S4pXYFTlFjklMRQzw.gif" /><figcaption>Push Notification Settings Page</figcaption></figure><h4>Open the concerned settings page in-app</h4><p>I’ve found many Stack Overflow answers like <a href="https://stackoverflow.com/questions/34149198/how-to-enable-auto-start-for-my-app-in-xiaomi-programmatically">this one</a> which recommend programmatically opening the concerned settings page by detecting your device manufacturer. While I like the idea, I have not implemented this. I haven’t had the chance to test if the device-specific code actually works which puts me at unease.</p><p>If you have other suggestions or ideas, I welcome them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fa297520793" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/why-your-push-notifications-never-see-the-light-of-day-3fa297520793">Why your Push Notifications never see the light of day</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to help your customers help themselves on your mobile app?]]></title>
            <link>https://medium.com/@metalwihen/how-to-help-your-customers-help-themselves-on-your-mobile-app-2f6421b8f5fc?source=rss-aab0d1af7441------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f6421b8f5fc</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[customer-support]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Neil Mathew]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 06:03:01 GMT</pubDate>
            <atom:updated>2017-10-17T06:03:01.617Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a5SjR4EtZeHn9qMfDdzx0g.jpeg" /></figure><p>We complete so many transactions on our phones. Be it shopping for a new pair of shoes, booking a cab ride home, or just ordering Chinese food. The transactions that occur on a day-to-day basis become so habitual and involuntary, that when something goes wrong, do you really have the time or patience to fix it? Rather than calling support, I’d prefer to figure it out on my own, provided I find what I’m looking for.</p><p>Self-service is not a new concept, yet <a href="https://www.kayako.com/blog/customer-retention-self-service/">it has not been leveraged enough</a>. This is particularly true for mobile apps — which is where Kayako comes in. We, at Kayako, are trying to make it insanely easy for the customer to find what they want, figure out what’s wrong, and fix it. Few taps on the screen, an ‘aha’ moment, and done. Problem solved.</p><p>That said, I’d like to introduce to you our Mobile Support SDK which enables you to add a knowledge base to your apps in a plug-and-play fashion. Think of it as an in-app <a href="https://www.kayako.com/help-desk-software/knowledge-base">Help Center</a> for your mobile users.</p><h4><strong>Find what you’re looking for</strong></h4><p>The Kayako Help Center is state-of-the-art and you shouldn’t limit your self-service to a <a href="https://www.kayako.com/blog/design-rules-faq-page/">long list of FAQs</a>. Your content can be anything: latest news, release notes, documentation, interactive tutorials, useful tips, etc. All this information is nicely broken down into navigable sections and made easily accessible through a search bar that no one can miss. Kayako’s smart search understands you and instantly makes suggestions as you type.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7T7brZZ7BbMg4l3I." /></figure><h4>An app built to keep up with you</h4><p>Mobile apps are globally available and the next person who downloads your app could be from anywhere. We believe that localizing your app is important. The user’s default language is automatically retrieved and set. And if they wish to change it, the option to do so is placed right on top where it matters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*fBPK9MJHiEs44nWh." /></figure><h4><strong>Content that speaks to you</strong></h4><p>In the end, it’s the articles you write that make all the difference. Kayako supports rich text formatting, inline images, and videos that enable you to educate your users in ways a phone call may not. The SDK transforms your rich content into a beautiful mobile-friendly format.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*3XMGNjI4ofvcZttm." /></figure><h4><strong>Plug &amp; Play</strong></h4><p>About ten years back, Nokia released their 6300i model. While the phone itself is irrelevant, the marketing slogan they used for it defines our intentions perfectly.</p><blockquote><em>Simply beautiful. Beautifully simple.</em></blockquote><p>The support SDK is designed to be simple for both the customers who use the app as well as the organizations that implement it. The SDK is very easy to set up which involves copying and pasting a few lines of code. No hassles.</p><p>And the best part? The support SDK not only <a href="https://www.kayako.com/blog/why-impatient-customers-really-love-self-service/">places the customer in control</a>, which is especially desired when dealing with information that is confidential or embarrassing, but also <a href="https://www.kayako.com/blog/the-self-service-guilt-trip/">reduces the customer service effort</a> for your organization. That’s a win-win in my book.</p><p>The Mobile Support SDK has come a long way since this article was originally written. Alongside the in-app <a href="https://www.kayako.com/help-desk-software/knowledge-base">Knowledge Base</a>, we’ve added the <a href="https://www.kayako.com/live-chat-software">Kayako Messenger</a> - a new, more personal and effortless way to talk live with your customers.</p><p>Set up the Mobile Support SDK by following the instructions <a href="https://developer.kayako.com/messenger/">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IvJnhxBC8Fko92HnYEVUnw.png" /></figure><h3>Credits</h3><p><em>Big thanks to </em><a href="https://twitter.com/aliciaverbs">Alicia Carney</a><em> for helping me with this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f6421b8f5fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>