<?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 Shashank Kumar on Medium]]></title>
        <description><![CDATA[Stories by Shashank Kumar on Medium]]></description>
        <link>https://medium.com/@shashankkumar?source=rss-782c6b0005b7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OXHGPEJw9rW0LmUo-7oEWw.jpeg</url>
            <title>Stories by Shashank Kumar on Medium</title>
            <link>https://medium.com/@shashankkumar?source=rss-782c6b0005b7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:54:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shashankkumar/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[Track your Shopify app listing using Google Analytics in the new App Store — Dec 2022 onward]]></title>
            <link>https://shashankkumar.medium.com/track-your-shopify-app-listing-using-google-analytics-in-the-new-app-store-dec-2022-onward-dd7c20ad7aaa?source=rss-782c6b0005b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd7c20ad7aaa</guid>
            <dc:creator><![CDATA[Shashank Kumar]]></dc:creator>
            <pubDate>Wed, 21 Dec 2022 12:51:39 GMT</pubDate>
            <atom:updated>2022-12-21T12:51:39.975Z</atom:updated>
            <content:encoded><![CDATA[<h3>Track your Shopify app listing using Google Analytics in the new App Store — Dec 2022 onwards</h3><p>Shopify has slightly changed how the Google Analytics integration works. Here’s the quick updated guide.</p><ul><li>Open up Google Analytics, go to ‘Admin’, ensure Property is set to the Shopify App Store GA tracking, and then click on “Goals”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qNPJ1TcTz_u-pYcV5yil4w@2x.png" /><figcaption>Goals in Google Analytics</figcaption></figure><ul><li>Create a “New Goal”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gh_VoZHSOZPLSF_jZtNg_A@2x.png" /><figcaption>New Goal</figcaption></figure><ul><li>Goal Setup</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sm1r95wstYJv1BfGdV_xFg@2x.png" /></figure><ul><li>Give your Goal a name</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*WaOefXoo6_TmbggP9c0Lfg@2x.png" /></figure><ul><li>Fill in the “Goal details” exactly below and verify to check.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*P3dc7LNVfpevkb6JBzHXRQ@2x.png" /></figure><p>Google Analytics doesn’t show historical data for goals. But going forward the new goal of App Store installs will be tracked.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd7c20ad7aaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing Access scopes for Shopify Apps]]></title>
            <link>https://shashankkumar.medium.com/managing-access-scopes-for-shopify-apps-c93b3cf3541b?source=rss-782c6b0005b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c93b3cf3541b</guid>
            <category><![CDATA[shopify-apps]]></category>
            <category><![CDATA[shopify-partner]]></category>
            <category><![CDATA[shopify-app-store]]></category>
            <category><![CDATA[shopify-app-development]]></category>
            <category><![CDATA[shopify-app-developer]]></category>
            <dc:creator><![CDATA[Shashank Kumar]]></dc:creator>
            <pubDate>Fri, 07 May 2021 18:35:30 GMT</pubDate>
            <atom:updated>2021-05-12T15:59:32.329Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UGIjecOYE0r9v8oCl9pMcg.png" /></figure><p>Shopify Access Scopes are used as a part of the <a href="https://shopify.dev/tutorials/authenticate-with-oauth#step-2-ask-for-permission">authorization process</a>, which specifies what parts of a shop’s data the app would like access.</p><p>Example list of scopes are: read_script_tags, write_script_tags</p><p>Your app should ideally only request scopes which it is currently using. Esp. for new apps — Shopify app review team might not approve your app if there is no valid use case for the scope.</p><p>Let’s say you launched a hypothetical app that adds add a simple popup to the store. To achieve this, you need to install your javascript code on the store. And hence you launch your app with justread_script_tags, write_script_tags scopes, which allow you to install your code on the Shopify store upon installation.</p><p>Since the use case was simple — your code would ask the above two permissions on every new installation. Something like this:</p><pre>INSTALL_SCOPES = “<a href="https://example.myshopify.com/admin/oauth/authorize?client_id=%7Bapp_client_id%7D&amp;scope=read_script_tags,write_script_tags&amp;redirect_uri=%7Bredirect_uri">read_script_tags,write_script_tags</a>”</pre><pre><a href="https://example.myshopify.com/admin/oauth/authorize?client_id=%7Bapp_client_id%7D&amp;scope=read_script_tags,write_script_tags&amp;redirect_uri=%7Bredirect_uri">https://{subdomain}.myshopify.com/admin/oauth/authorize?client_id={app_client_id}&amp;scope={INSTALL_SCOPES}&amp;redirect_uri={redirect_uri</a>}</pre><p>However, apps evolve, and sometimes, adding new features need access to new scopes for your app.</p><p>Merchants started asking for new features for your newly launched hypothetical app. And one of the features requested was to add a discount code when a customer clicked on your popup. But for your app to read or create a discount code, your app would need read_discounts, write_discounts permissions.</p><p>While it’s easy to set things up for new installs, existing installed stores haven’t given you this permission, and adding a feature to create discount codes in your app would not work with them.</p><p>So first thing first: We would need to know which store has which permissions. So instead of hardcoding your permissions and assuming everyone has the same permissions, maintain a list of scopes along with store details. At PushOwl, we store this data in a website table.</p><pre>website:</pre><pre>- shopify_plan (str)<br>- scopes (str) # comma separated list of scopes<br>- status (enum: installed | uninstalled)</pre><p>For every installed website, we maintain a list of scopes we have access to. If a website uninstalls, we reset the scopes and ask for a fresh set of permission to re-install (if they do 😅).</p><p><strong>Strategy 1: Ask for permissions on the next login to your app</strong></p><p>While this is the easiest to build. Whenever a merchant tries to access your app, check in your database if you have all the necessary permissions — if not, re-initiate the OAuth flow with new scopes, and after that, they can reaccess the app.</p><p><strong>Pro</strong>: Easy to build and Ship</p><p><strong>Cons</strong>: There is an edge case over there.</p><p>Shopify stores have staff that uses apps regularly (it can be a VA fulfilling orders or a marketing person at the store) and might not have all permissions to re-auth your app. In those cases, a store owner or another staff with necessary permissions typically installs the app, and other staff members use it. If the app is getting accessed by a staff member who doesn’t have the required permissions, the app will become inaccessible to them unless the store owner or staff with the necessary permissions re-authenticates your app.</p><p>Shopify apps cannot know whether which staff has which permission scope, and also, there is no redirect to the apps in case installation fails due to lack of permissions to the app members. This can lead to frustrating experiences and those staff members reaching out on support to fix this.</p><p><strong>Strategy 2: Lock feature and ask for re-authorization</strong></p><p>If a feature needs a particular scope to function, we lock it behind an overlay that says: “Re-authorise the app to gain access to this new feature,” or whenever they try to use it — we automatically redirect them to new OAuth flow with a fresh set of permissions.</p><p>While this needs additional efforts but ensures you can seamlessly support existing and new users.</p><p><strong>Strategy 3: Advanced: Smart Authentication &amp; Lock Feature</strong></p><p>While it might not be possible to tell whether a staff has necessary permission for a scope when they re-install the app — a Store owner by default has all the permissions. You can use the technique listed in <a href="https://medium.com/pushowl/smart-authentication-for-shopify-apps-36bf6bb61222">Smart Authentication for Shopify Apps</a> to check if the person logging in your app is store owner or not. And if the person is store owner, you can go use Strategy 1: re-direct auth flow with new permissions and if they are not store owner (staff or collaborator) — you can move implement Strategy 2.</p><p>Do follow my blogs for more tips and tricks. We are also launching Owlytics.io (A platform for Shopify App developers to give insights to their churn and growth metrics — Sign up on Beta to get early access). I am available on Twitter(<a href="https://twitter.com/shashankkr9">@shashankkr9</a>) to chit chat anything about Shopify Apps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c93b3cf3541b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Marketing Shopify App — Partner Friendly Apps]]></title>
            <link>https://shashankkumar.medium.com/marketing-shopify-app-partner-friendly-apps-a948f28cde07?source=rss-782c6b0005b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a948f28cde07</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[bootstrapping]]></category>
            <category><![CDATA[shopify]]></category>
            <category><![CDATA[shopify-app-development]]></category>
            <dc:creator><![CDATA[Shashank Kumar]]></dc:creator>
            <pubDate>Fri, 08 Jan 2021 17:21:37 GMT</pubDate>
            <atom:updated>2021-01-08T17:35:41.251Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IZpZQm32QoS4GwP89viFYg.png" /></figure><h3>Marketing Shopify App — Partner Friendly Apps</h3><p>One of the major growth channels at PushOwl had been Shopify Partners (ie. Shopify Agencies, Experts, Freelancers, Youtubers, Influencers) using our Shopify App.</p><p>This blog is for Shopify App Developers who have launched a freemium or paid app and looking for ways to expand the reach of their apps. It’s really a small thing that leads to a huge growth impact. So small, that it would literally take less than 5 lines of code to implement it. However, when you look at the App Store only 303 out of 5000+ apps on Shopify have done it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*j27Nf0eq44Z_53X_wqqNQw.png" /><figcaption>303 Partner Friendly App</figcaption></figure><p>So before we dive into how to make your App Partner Friendly, let’s look at what are Partner Friendly Apps.</p><h3>What are Partner Friendly Apps?</h3><p>Partner friendly apps can be installed for free by Shopify Partners. These apps are free to test in development stores. And the app partner only charges once the store is switched over to a paid plan.</p><p><strong>So what are development stores?</strong></p><ul><li>Shopify Agencies typically create new stores as a development store. This is especially used when they are building a new store — getting the designs and functionalities implemented. Shopify doesn’t charge the plan during the development.</li><li>Development Stores are also used by Agencies to be replicas of live stores, where they push new changes first, test, and then set it live. We have especially seen Agencies working with high volume stores (mostly Shopify Plus) test functionalities of our Apps before putting it live on the store.</li><li>Shopify App Developers also use development stores to test apps. To get inspiration from other apps, or test out an integration with apps.</li></ul><h3>Why should you make your App Partner Friendly?</h3><p>In all the cases above, especially in the case when a Shopify partner is trying to set up your app on behalf of your customer — they might get this screen below if you try to charge them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ByE19be0TnqNY8ADyiCesQ.png" /></figure><p>So by not making your app partner-friendly — you are losing on an insane opportunity. I recently saw this in the Shopify Partners Facebook group, and you can tell how frustrating it is for the Shopify Partners.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*sgzsbnnsZr5EYX6k0GIB-g.png" /></figure><h3>How to make your app partner-friendly?</h3><p>Now this section might be a bit technical and is meant for folks who do the hard work ie code 🧑‍💻</p><p>There are two steps:</p><ul><li>Bill using test charge when upgrading for partner stores</li><li>Cancel the plan when the store becomes a paid plan</li></ul><h4>Bill using test charge when upgrading for partner stores</h4><p>Now, here’s come the less than 5 lines of code magic. All you need to do is pass a flag {test: true} when billing your app for Development Stores.</p><p>Reference: <a href="https://shopify.dev/docs/admin-api/rest/reference/billing/recurringapplicationcharge">https://shopify.dev/docs/admin-api/rest/reference/billing/recurringapplicationcharge</a></p><p>You can identify if a store is a development store or not using the Shopify Plan. This data is found in the Shop API At PushOwl we store shop data in our database, so it’s quick to identify a development store without calling the Shop API at the time of upgrade.</p><p>Typically a development store has Shopify Plan as affiliate . But in recent days we have identified ~27 distinct Shopify Plans. I have <a href="https://gist.github.com/shashankkr9/78aebed308a2aac49c607464857c7e6f">listed them all here</a>.</p><p>At PushOwl we do test charges for Shopify Plans which are:</p><ul><li>affiliate</li><li>partner_test</li><li>plus_partner_sandbox</li></ul><p>Apart from development stores we also do test charges for stores run by the Shopify team and alumni.</p><ul><li>staff</li><li>staff_business</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tDBBsCToigj4VnFbpJlNWQ.png" /><figcaption>Python Code Snippet to Allow Test Charges</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/1*oevtnR93cug2lc6nqjl0DQ.png" /><figcaption>Python Code Snippet to Initiate Test Charge</figcaption></figure><p><strong>Cancel the plan when the store becomes a paid plan</strong></p><p>Listen to the shop/update Webhook, so when the store switches to a paid plan, you can cancel the paid features. You can also consider sending an email to remind the merchant to switch back to the paid plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sd5Q6OJgrKlIR4MgLmFPyg.png" /><figcaption>Code Snippet to cancel Paid Plan</figcaption></figure><p>Once you have made your app partner-friendly, submit your app to Shopify to get included in the partner-friendly apps collection. The form can be found <a href="https://docs.google.com/forms/d/e/1FAIpQLScFaLRzz6TA-QpwkwmnN-oZ_aVITd7HBoOKmPPBoxkaOaE0Qg/viewform">here</a>.</p><ul><li><a href="https://apps.shopify.com/collections/partner-friendly-apps">https://apps.shopify.com/collections/partner-friendly-apps</a></li></ul><p>That’s about it. You just made your app better for Shopify Partners and opened up a new channel for marketing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a948f28cde07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Smart Authentication for Shopify Apps]]></title>
            <link>https://medium.com/pushowl/smart-authentication-for-shopify-apps-36bf6bb61222?source=rss-782c6b0005b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/36bf6bb61222</guid>
            <category><![CDATA[shopify-development]]></category>
            <category><![CDATA[shopify-apps]]></category>
            <category><![CDATA[shopify-app-development]]></category>
            <category><![CDATA[shopify]]></category>
            <category><![CDATA[shopify-plus]]></category>
            <dc:creator><![CDATA[Shashank Kumar]]></dc:creator>
            <pubDate>Mon, 25 May 2020 15:40:16 GMT</pubDate>
            <atom:updated>2020-05-25T16:08:20.993Z</atom:updated>
            <content:encoded><![CDATA[<p>There is one thing which every app company does in Shopify, is to build authentication. But what if, we could do little differently. A small tweak which would not just help you authorise/authenticate a merchant but also tell you a little more. A lot of times, it’s not the account owner, but a staff or a collaborator. They log in at different times and might be using your app for different use cases. This blog is about sharing what we learnt in the last two years. And hope your comments will teach us more, and together we can build better apps for entrepreneurs.</p><h3><strong>Basics First</strong></h3><p>Let’s revise some of the concepts. A merchant can reach your app through one of the following ways:</p><ul><li>Click on “Add App” button in Shopify App Store — Signup Flow</li><li>Come back to your app from Shopify App Admin — Relogin Flow</li></ul><figure><img alt="Signup Flow — Clicking on “Add App” button in App Store" src="https://cdn-images-1.medium.com/max/746/1*VJuzVniE2sBo-63qHmxE4g.png" /><figcaption>Signup Flow — Clicking on “Add App” button in App Store</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MxISrI9u8bTeEP7914aN4A.png" /><figcaption>Relogin Flow — From Shopify Admin &gt; Apps</figcaption></figure><p>In both the scenarios, Shopify is going to hit your backend on the url in the App Setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*_FjzKCjZFY0ewPuGJ_kOvQ.png" /><figcaption>Shopify Authentication Endpoint</figcaption></figure><p>There might be few other Auth flows:</p><ul><li>From a dedicate signup/signin page by entering their subdomain</li><li>Custom Auth — Username/Password, or Google Login</li></ul><h3>The First Optimisation</h3><p><em>Log all attempted installs and use minimum scope during signup</em></p><p>Every time the API Endpoint is hit, Shopify passes an identifier for the shop and an HMAC which can be verified using the App Secret Key. The identifier is sent in url parameter in format examplestore.myshopify.com. Our system strips (.myshopify.com) part, and just uses the subdomain (examplestore) as the identifier. And on every auth, I can assume all of us check our database to find if the store was already installed or not to initiate Signup or Relogin flow.</p><p>In the Signup flow, the backend will be generating a Shopify Permission Url which will add all the scopes, the app needs to perform.</p><p>A lot of times, the apps are getting installed by a staff and if the staff is not having necessary permissions, then the app install will fail without any warning to backend. There are two things which can be done here:</p><ul><li>Ensure before redirecting to the Shopify OAuth keep a record in your system. We keep a record in our database as “Attempted Install” table.</li><li>Try to minimise the scope you initially need, if you see a lot of failed installed. Some of the optional permissions can be taken later with new permission flow (described later)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g6lBE54w6UjgNsdUSgmIfA.png" /><figcaption>Measuring App Install Success</figcaption></figure><blockquote>Monitoring and success of your signup can potentially lead to ~5% more signups</blockquote><h3>Identifying actual users</h3><p>If you look at the authentication documentation for Shopify App, you will probably won’t see a way to identify subscribers. Most of us app developers use the Offline Access Method (<a href="https://shopify.dev/concepts/about-apis/authentication#offline-access">https://shopify.dev/concepts/about-apis/authentication#offline-access</a>) which allows apps to exchange a permanent access token with Shopify to do API calls during the time an app is installed at merchants store. We can call the shop.json API, and that gives the account owner name and email among other things to setup the authentication system in app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*884Vt5LJYeIA0t3NuxsVIw.png" /><figcaption>Simple Auth Flow — Flowchart with offline authentication</figcaption></figure><p>What typically gets missed is the online access method (<a href="https://shopify.dev/concepts/about-apis/authentication#online-access">https://shopify.dev/concepts/about-apis/authentication#online-access</a>). The documentation says:</p><blockquote><em>An access token created with this access mode is temporary, and is guaranteed to expire after some amount of time.</em></blockquote><p>Since the access token is temporary, it’s no use for most apps. But it does have one cool other feature as per the documentation:</p><blockquote>After your app is installed, requesting this access mode will always return an access token restricted to the scopes available to the user. The app can inspect scope and associated_user_scope to determine if a user is lacking certain permissions.</blockquote><p>Let’s dive deep on what the response actually looks like.</p><pre>{<br>  &quot;access_token&quot;: &quot;shtemp_btestecetoken9cfa48c8adb1eb572a4&quot;,<br>  &quot;scope&quot;: &quot;write_content,read_products,read_customers&quot;,<br>  &quot;expires_in&quot;: 86398,<br>  &quot;associated_user_scope&quot;: &quot;write_content,read_products,read_customers&quot;,<br>  &quot;session&quot;: &quot;8dce9adf88757bf1eab4c771297ba2cff5e3ed87cb3ddeae95377c1944a06e78&quot;,<br>  &quot;associated_user&quot;: {<br>    &quot;id&quot;: 117977220,<br>    &quot;first_name&quot;: &quot;John&quot;,<br>    &quot;last_name&quot;: &quot;Doe&quot;,<br>    &quot;email&quot;: &quot;<a href="/service/mailto:contact@examplestore.com">contact@examplestore.com</a>&quot;,<br>    &quot;account_owner&quot;: true,<br>    &quot;locale&quot;: &quot;en-IN&quot;,<br>    &quot;collaborator&quot;: false,<br>    &quot;email_verified&quot;: true<br>  }<br>}</pre><p>Voila! We have the logged in user information in the associated_user key!</p><ul><li>“account_owner”: true means the logged in user the owner. Obvious! And you should be able to match the data from shop.json API call as well</li><li>“collaborator”: true would mean the logged in user is a Shopify Partner. As an app developer you might want to reach out to them for collaboration. <br>Sometimes your competitors spying from a real merchant store ;)</li><li>“account_owner”: false and “collaborator”: false would mean the person is a staff of the store.</li></ul><p>I would suggest to log an entry in the database for each of these login events. This will potentially show you the most active user of your app. So if you want to reach out to the relevant person for let’s say an upgrade, you are actually talking to the most relevant person.</p><h3>Putting Authentication and Identification Together</h3><p>So how do you get the best of both world. Apparently, after you have done offline authentication, redirecting a merchant to online authentication will happen silently without clicking on “Allow” on the OAuth Screen. Which means, you can do silent online authentication. A merchant might see a quick redirect happening for a microsecond, but your backend will get all the necessary data. Here’s how a typical flow chat would look like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TbPWr4IEQrzBYGm-Pr4Y3Q.png" /><figcaption>Updated Authentication Flow Diagram</figcaption></figure><blockquote>Don’t forget to add online auth callback url in whitelisted url</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/979/1*WMf7JpiUQNNqY171lkYG4g.png" /></figure><h3><strong>Doing things asynchronously</strong></h3><p>Exchanging Online Authentication token to get login user data and doing further processing is something which I would recommend doing on a background process. Since these additional seconds of processing means, we are delaying access to our app (not a good UX!)</p><p>Frameworks like Django have queuing systems like RabbitMQ + Celery or RoR has Sidekiq to get things done on background (or worker) servers.</p><h3>Slack Notifications</h3><p>At PushOwl, we stick more data in order to form a unified view of the person using the app. We send real time pings to our support team via Slack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*O5ZYaSQcFNuY_VEUeu6Ofw.png" /><figcaption>A typical Slack Ping</figcaption></figure><p>For Slack, you can utilise their Incoming Webhook feature to send real time updates.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.loom.com%2Fembed%2F31728ae1237e4e5c9fded02b7211f692&amp;display_name=Loom&amp;url=https%3A%2F%2Fwww.loom.com%2Fshare%2F31728ae1237e4e5c9fded02b7211f692&amp;image=https%3A%2F%2Fcdn.loom.com%2Fsessions%2Fthumbnails%2F31728ae1237e4e5c9fded02b7211f692-00001.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=loom" width="948" height="711" frameborder="0" scrolling="no"><a href="https://medium.com/media/1f1dd25cb31a433edb56a81b46183479/href">https://medium.com/media/1f1dd25cb31a433edb56a81b46183479/href</a></iframe><p>So combine all the data in the background and send a ping to your Slack. And all it takes is a small API request to send data like this.</p><p>Attaching a screenshot of some of the field we find really useful. It helps us qualify merchants on the kind of support we need to provide to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*O5ZYaSQcFNuY_VEUeu6Ofw.png" /></figure><p>Some useful fields that can be considered adding:</p><ul><li>Store Created At or the age of the store</li><li>Shopify Plan (we exclude trial stores from our Slack Pings)</li><li>Signup At</li><li>Intercom Link (We call Intercom’s API to get one click link to start having convo with them. Every second is import when it comes to real time chat)</li><li>Country and Phone (In case your Sales team does calling)</li><li>Activity (using the login data we have stored, we can figure out how engaged a merchant is)</li><li>Business Metrics (In our case, subscribers gained, campaigns sent and revenue made)</li></ul><h3>Further Optimisations</h3><p>Once you have stitched all this data and more, there are multiple use cases which you as an app can track during lifecycle of the app.</p><ul><li><strong>Uninstalls</strong> — When an uninstall happens you can send an extra data when was the last login. Some scenarios:<br><em>- Last login happened few minutes back:</em> Worth taking a look in screen recording session of the merchant (FullStory, LuckyOrange or HotJar), and see what might have caused the uninstalls (Dead Clicks, Rage Clicks etc)<br><em>- Last login was long time away:</em> It means the app has been dormant for quite sometime. Which means you as an app dev need to work on retention<br><em>- Uninstall happened by different person than installation:</em> Some other team member didn’t like your app. Maybe want to check if it was a mistake.</li><li><strong>Sales Qualification: </strong>Reaching out to folks when they are actually using the app always leads to more conversion. You are not waiting for your email to be opened in that case. Tip: Send a ping to a dedicated Slack channel</li></ul><h3><strong>Bonus: Managing Scope of Your App</strong></h3><p>One of the important aspects of the whole approach is the scope your app uses for authentication. As the app keeps evolving, potentially the app might need new permissions. Not managing the scopes can lead to following issues:</p><ul><li>Old signups will see API errors since your app doesn’t have necessary permissions</li><li>If you start asking everyone new permissions, a staff account potentially won’t be able to access the app, if they don’t have necessary permissions 😱</li></ul><p>Our DB schema maintains the list of permissions a store has. And if someone tries to use a new feature which needs additional scope, it redirects them to Offline Auth Flow again, and after getting the new permissions, we write it back to the DB.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*DvyP6sJoDHYwr5-SvHirQg.png" /><figcaption>Using Offline Auth to trigger new permissions</figcaption></figure><h3><strong>Final Notes</strong></h3><p>As the Shopify ecosystem is growing, hope to add a little value to the entrepreneurs who code so that we can support the millions of entrepreneurs who sell online. Feel free to reach out to me over email shashank@pushowl.com or my team.</p><p>And if you are looking to join a small and happy team — We are a team of 12 humans and 2 dogs looking for superheroes to join us. Our job listing is usually live at: <a href="https://angel.co/company/pushowl/jobs/">https://angel.co/company/pushowl/jobs/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36bf6bb61222" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pushowl/smart-authentication-for-shopify-apps-36bf6bb61222">Smart Authentication for Shopify Apps</a> was originally published in <a href="https://medium.com/pushowl">PushOwl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Startup with the Greedy Algorithm and a Bunch of Misfits]]></title>
            <link>https://shashankkumar.medium.com/building-a-startup-with-the-greedy-algorithm-and-a-bunch-of-misfits-e84a2ec21382?source=rss-782c6b0005b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e84a2ec21382</guid>
            <category><![CDATA[bootstrap]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[shopify-apps]]></category>
            <category><![CDATA[founder-stories]]></category>
            <category><![CDATA[shopify]]></category>
            <dc:creator><![CDATA[Shashank Kumar]]></dc:creator>
            <pubDate>Tue, 30 Apr 2019 10:16:38 GMT</pubDate>
            <atom:updated>2019-04-30T10:35:57.806Z</atom:updated>
            <content:encoded><![CDATA[<h4>Greedy is an algorithmic paradigm that builds up a solution piece by piece, always choosing the next piece that offers the most obvious and immediate benefit</h4><p>When I quit my job at Microsoft back in 2015, I didn’t have any solid reason. The reason I say so is because I had just gotten a promotion, and I didn’t have any startup ideas. Probably the only reason to quit was to not to lead a life which seemed like a formula. Get a Job, pay bills, take a home loan and keep paying it for the rest of the life. With no practical skill sets, no team, and no product idea, I started my journey. Probably a little bit of self-taught python coding.</p><p>As of today 29th April 2019, our company PushOwl reached 2 milestones. We just crossed <strong>10K active merchants and $50K in monthly recurring revenue</strong>.</p><p>Our small company is run by 8 folks whom I can heartily say are the closest thing to family. (Thank you, <a href="https://medium.com/u/5acfcbe6afef">Kunal</a>, Rameez, Nitesh, <a href="https://medium.com/u/b6327346709e">Asiya</a>, Felix, <a href="https://medium.com/u/f97e729f45b7">Adhithya</a>, Raj and <a href="https://medium.com/u/67a371040d1d">Vanhishikha</a> for being part of the journey.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZLsHQ7m7L8v9Ouin4cBZYQ.png" /><figcaption>Milestone</figcaption></figure><p>What happened in between is my story!</p><p>And this blog is meant for every individual who is starting a company <em>without any clue, without any north star, without a billion dollar idea, without any product skill, probably an introvert, without any design skills, no understanding of Venture Capital, and no idea on how to build a team</em>. Basically nothing. The only component which worked out is having 24 hours a day (every day). And mistakes — a lot of them.</p><h3>Phase 1 | Prologue: A series of unfortunate events</h3><p>With enough savings in the bank to last six months ($360USD/month to be precise), I started my journey. To save cost, I started working from home. In retrospect that was one of the worst ideas. When at home, I was either working, sleeping or doing nothing. Staying indoors like a zombie and having no context switches, my productivity started to drop exponentially.</p><p>After about six months of doing nothing (supposed to be my peak time given that I had all the enthusiasm after quitting the job), I decided to switch to a co-working space. In the meantime, I had also learned that starting a company with folks who have a day job doesn’t pan out — job priorities, weekend commitments, reduced productivity. You end up waiting too long for their work to be done. And if the folks are your friends, it only gets worse.</p><p>My next learning was working with a team where the priorities are just not aligned, and working on a “hot” trend. Since Chatbots became cool back in 2016, we started building a company around that. The company mission was to automate chat support. But personally, someone wanted a Lamborghini, someone else wanted to work on cool tech and another person just wanted to build a startup 🙌. Clearly, it didn’t work out and I ended up leaving midway while breaking so many personal ties.</p><p>After a bunch of failed ideas under my belt and trying to start a company with my friends, I was out of time, without any friends, and a complete failure (or that’s how it felt at the time).</p><p>Nobody understood what was I trying to do; neither did I.</p><h3>Phase 2 | Let’s be an Indiehacker</h3><blockquote>Building a product with zero revenue but a tonne of learnings.</blockquote><p>Being an avid reader of hacker news, I regularly read stories about solo founders who have built a self-sustainable business. The best part of being an indie-hacker is that you don’t have to raise funds nor build a team (or at least I thought so). You can travel and earn on the go. For a person like me, that seemed like the perfect solution. Around that time, I came across push notifications. There were existing solutions, I found them to be an MVP as well. And I thought I could build something at par or even better with few weeks of hacks (or at least I thought so). A push notifications service with a mobile app would be killer! 😂</p><p>So on May 1st, 2016 I registered <em>pushowl.com</em> (tried a few combinations of push + random stuff, ultimately found “owl” and it resonated quite well with me. I had a habit of working late at nights or not sleeping at all). Old habits die hard, and I soon asked a few of my friends to help me with my idea. And so they did, but only for some time.</p><p>I was back to square one!</p><p>So, I realized that I suck at building teams, and I decided to continue the journey alone. After building the MVP, the next challenge was to build a landing page with the help of my freelance friend Nitesh. I think we rocked it! 🙈</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*qMVauWvbmpi3KSSqZF8YZQ.png" /><figcaption>My first attempt at building a landing page</figcaption></figure><p>I was ferociously teaching myself copywriting, design, SEO, growth hacking, pricing. There was so much to learn. While I wasn’t getting any customers, I was happy that I had a prototype which I could use for my learnings. Somehow, I was patient, probably because I never had any expectations of success. For the next year, I slept in my co-working space on the sofa with a sleeping bag every alternate day (taking a shower is important :P). I didn’t feel like going home or taking any weekend off. I was happy being anti-social (probably watched too many <a href="https://medium.com/u/c4ec9163657c">Gary Vaynerchuk</a> videos). I used ‘<em>OneNote’</em> and filled it with things to do today and in the future. In this period, I met a great designer and friend who helped me build a polished version of our landing page. However, we still didn’t have a single paying customer!</p><p>After almost spending a year in kind of a trance (now 2017), I was woken up by my dwindling bank balance and reminders from my parents to get stable. It had been two years since I quit my job, almost a year of PushOwl and nothing much to show. Almost in a panic mode, I started picking up random things. I started pitching to a few VCs to raise funds (of course, it didn’t work out — a single guy in an overly competitive market with zero paying customers), going to startup events, and working on side projects.</p><p>Around the same time, I met the Shopify team who co-incidentally took an office in the same co-working space that I was working in. After having a conversation with <a href="https://medium.com/u/da4a3a069c02">Vargab Bakshi</a> and Namra from Shopify, I decided to give it one last shot — focus and build an app which is highly tailored for Shopify merchants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N2LlTyFTxpdfgeTEZBo6FA.png" /></figure><p>However, I was still not sure things would work out, given my history. So, I explored the idea of taking my old job after receiving an inbound request from my manager.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/487/1*CSVWo68ALfsM9PDH-1XpeA.png" /></figure><p>But when I went to my old office again, I felt like I was quitting. I was giving up on my dreams (which weren’t even so big!). I just couldn’t fake it. So I cursed myself for even thinking about going back and decided to give it one more chance. Then, Shopify happened!</p><h3>Phase 3 | Facing my fears</h3><p>While building products and PushOwl, I had always been escaping one thing. Talking to people! I wasn’t talking to customers and I didn’t want to build a team. Being anti-social wasn’t helping. With my last chance, I finally started doing the one thing, which I should have done from Day 0. <strong>Talking to the customers</strong>. Soon, I realized Shopify merchants could be found in a lot of FB groups. Still being anti-social, I didn’t comment on anything but, I just read through all the posts every day. I had subscribed to pretty much all the groups and read every post and every comment.</p><p>I was afraid to even mention PushOwl in any of the posts because I felt that it won’t provide any value. So I didn’t. But I came across a few common problems after observing a lot of posts. <em>What theme is this store using? Which app is on this store? </em>Being a developer, I could quickly look at the code and know the answer. So, my first few social interactions were just helping folks with problems that were unrelated to what I was actually working on.</p><p>My <em>‘OneNote’</em> reminded me of side project marketing. So I built WhatStoreTheme.com and WhatStoreApp.com. My first social media post after a long while was about my side projects — something that I felt solved real problems. I added a small “Powered By PushOwl” link and this was how I got my first initial customers. <a href="https://medium.com/u/c988df17f9e5">Satish Kanwar</a> (GM of Shopify) commenting and appreciating the work was the highlight of those days 😊.</p><p>Around the same time, Kunal joined our team. Almost at half of his last salary, he had moved to a new city to work for a startup (project). He had accidentally applied on an internship post, thinking it was a full-time job. Anyways, the mistake happened, and he joined a few months before we officially launched on Shopify. Kunal was given random tasks. I remember once, he was given a target to get 5 customers in a week (which he miserably failed, not his fault though). I was paying him with the leftover cash I had after selling Microsoft shares.</p><p>By the time we launched on Shopify, we were broke. To manage things, I applied for Storetasker (run by an amazing guy and now mentor, <a href="https://medium.com/u/b750d01db52f">Jonathan Kennedy</a>) and fortunately, I got accepted. Working at nights, I managed to earn enough to keep the lights on. I also thought I could pitch PushOwl to the customers that I worked with on Storetasker (but I was wrong, the context matters. Or I was just too shy). But, I did end up pitching to a client, <a href="https://medium.com/u/782e501e4e58">Simon Rodrigue</a>, who was an advisor for Smile.io and an ex-SVP Walmart. As of today, I still reach out to Simon, whenever I have a problem which only a few folks would understand.</p><p>Things turned for the better when PushOwl got selected as a “New and Noteworthy app”.</p><h3>Phase 4 | Path to Happiness</h3><blockquote>We take care of the <strong>people</strong>, the <strong>products</strong>, and the <strong>profits</strong> — in that order.<br>- The Hard Thing About Hard Things</blockquote><p>Having realized the benefits of talking to people, I started reaching out to app developers to take advice. And you know what — I got help from folks whom I was inspired from. The right direction from the start really helped become what we are. Thank you, <a href="https://medium.com/u/bdd29cf2541">Bjorn Forsberg</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QgKaFbizq6uyLZxX0T5i9Q.png" /></figure><p>After almost two years in the journey, I was finally able to define happiness for me. My happiness was directly proportional to the happiness of the people whom I interact with. The more I could be a part of someone else’s dream getting fulfilled, I was happier. Which meant, our merchants getting sales via our platform, or my teammates getting their dreams fulfilled.</p><p>Over the next year, building a place where folks enjoyed working was my source of enjoyment. Kunal adopted a dog (Dany) against the wills of his parents (it wasn’t tough for his parents to start adoring Dany though), Rameez got a camera which he always dreamt of, Asiya lives independently in Bangalore after coming from an orthodox family, Felix runs his strategy his own way without our interruptions, and Adhithya is taking complete ownership of design. When our company became the source of our team’s happiness, everyone took their job to their hearts and did them as owners of the job. They call me the boss, but in my eyes, they will be the bosses of the respective departments which they are going to build in Phase 5, making me redundant.</p><p>We really didn’t have to do any crazy marketing (Shopify App Store took care of it), except to do what we loved. We helped our merchants — they gave us stellar reviews. We provided a platform which helped them do more sales — and they paid for subscriptions. I started being more social (at least online) and made more friends in the last 2 years than I did my entire lifetime. Our team has now traveled to Vietnam, Singapore, Malaysia, London, Taiwan, and Sri Lanka. In every place we landed, we had a Shopify Partner to go out for a coffee. This is an ecosystem I am honored to be part of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DlbH8ZJ2EiVSha4siYiwpw.png" /><figcaption>Last 2 years — Team and Travel</figcaption></figure><h3>Phase 5 | To Infinity and Beyond</h3><p>What started as a learning project, is now a platform which is used by 10K merchants online. <strong>5 million notifications are sent out of our platform every day. </strong>And PushOwl has not just become a part of the marketing activity of these brands. Our mission is to empower merchants with a new version of PushOwl which will help them do “more sales with fewer notifications”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fkd7PZDOZ2VxSzu6Z8lDLQ.png" /></figure><p>And yes, the next stop is 100K. We are lucky to have the footsteps carved by so many amazing folks already. <a href="https://medium.com/u/bab76dfc19b0">Shopify</a>, <a href="https://medium.com/u/8da401febedf">Privy</a>, <a href="https://medium.com/u/41143622e6ef">Bold Commerce</a>, PixelUnion, Smile.io, Recart, Forsberg+Two, Shogun, Fera, ShopMessage — We are learning from you!</p><p>And we know our next step is going to be challenging, but full of learnings.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e84a2ec21382" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Geeks, Beers and no tech talk]]></title>
            <link>https://shashankkumar.medium.com/geeks-beers-and-no-tech-talk-c773ef3f163d?source=rss-782c6b0005b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c773ef3f163d</guid>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Shashank Kumar]]></dc:creator>
            <pubDate>Mon, 23 Nov 2015 15:04:06 GMT</pubDate>
            <atom:updated>2015-11-23T17:11:34.929Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KVynKPWyDS5WTLuVBuo9Bw.jpeg" /></figure><p>A lot of times when folks(techies, geeks, programmers, etc. etc.) come together, they really love to talk about the last great technical feat they accomplished, and how awesome their current app, website or product is. So we decided to have a learnathon among the folks we knew in our network and share the secret sauce. The entry criteria: everybody talks non-tech.</p><p>And I believe this was one of the best times we had. Because we were not talking about the tech stack but the life stack of geeks. The journey to reach the goal became the focus, rather than the goal. The driving force during the times of highs and lows became the focus, rather than the number of downloads or page views. And perhaps this is the stuff which can be learned only when you have had a few bottles of beer and some friendly folks around.</p><p>We started with one of the stars of the Indian startup ecosystem, Ankur Saxena, SVP Engineering, Grofers.com and more importantly the first engineer over there. The key takeaway being that when the technology aligns business, the magic happens. Getting to know that the Grofers team worked 120 days, non-stop and churned out an app whose UI/UX was only competed by Google News app, and soared the engagement multiple times, was awe-inspiring.</p><p>Anup Reghunathan, a 15 year veteran at Microsoft, who ran the Bing bootstrap team in his last stint, which he called a startup within Microsoft, talked about his journey. He quit Microsoft on the exact 15th year, after moving back to India three years back, and talked about the cultural differences in the Indian and US tech ecosystem.</p><p>Now that these guys had already captured our attention, we had somebody among us who had not worked on computers till he had entered college. Coming from a very humble background, Sanjeev, now a developer at Commonfloor, talked about the sleepless nights he worked once he got hooked on to programming.</p><p>I wish I could share the share the talks of everyone, but let me conclude it with, Eric Simons, co-founder of <a href="http://thinkster.io/">thinkster.io</a>, an online platform to “Supercharge your web &amp; mobile engineering skills by building real projects” live streaming from Silicon Valley, 8:00 AM in his timezone. I had come across thinkster, when I was learning Django + Angular after quitting my job at Microsoft, to enhance the backend of <a href="https://play.google.com/store/apps/details?id=com.bazzingalabs.adviceapp">Counsel</a>. But I believe apart from my tech learning, I really loved how Eric managed to grow and maintain a lovely community on the thinkster pro channel. Though it was a 30-minute live stream, we all enjoyed every second of it and had many key takeaways. Firstly, if you eat shit, you will code shit, hahaha. So keeping a healthy body and mind is the key to having a productive life. Secondly, to grow a community is like welcoming every new user to a party. Having seen this first hand, when I joined the pro channel, I realised how this small gesture really made THE difference.</p><p>We officially ended the party at 10:00 PM, but most of the folks hung around till 2:00 AM, and talked and showed each what they had been up to. This was one of a kind meetup and we really wish to have more of these, and grow a community of folks to build a strong tech culture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cyG-z9tIEtQVnwvfNonzkg.jpeg" /><figcaption>Live stream with Eric Simons</figcaption></figure><p>Here’s a list of folks who were present.</p><p>1. Anup Ragunathan: ex-Microsoft, one of the first engineers at Microsoft One Drive<br>2. Eric Simons: Co-founder, thinkster.io [Live stream]<br>3. Ankur Saxena, SVP Engineering, Grofers.com [Live stream]<br>4. Deven Bhooshan: Developer, Amazon<br>5. Shobhit: ex-Hike Messenger<br>6. Tarun Chaudhary: Software Engineer, Livspace<br>7. Mohammad Shabaz Moosa: Android Developer, Microsoft Office<br>8. Manpreet Singh Bedi: Full Stack Developer, Morgan Stanley<br>9. Prafful Gupta: Cofounder, Solvify<br>10. Sanjeev Kumar: Developer, Commonfloor<br>11: Sarvesh Soni: Software Engineer, ex-Microsoft<br>12: Girish: Android developer, Freecharge<br>13: Abhik Mitra, Software Engineer, Office for Android<br>14: Shashank Kumar, Software Engineer, ex-Microsoft</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c773ef3f163d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A note of thanks to the people who have influenced my life.]]></title>
            <link>https://shashankkumar.medium.com/a-note-of-thanks-to-the-people-who-have-influenced-my-life-478887869dc9?source=rss-782c6b0005b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/478887869dc9</guid>
            <dc:creator><![CDATA[Shashank Kumar]]></dc:creator>
            <pubDate>Thu, 02 Oct 2014 10:37:29 GMT</pubDate>
            <atom:updated>2014-12-07T07:56:25.676Z</atom:updated>
            <content:encoded><![CDATA[<p>It was way back in 2012 when I heard my friends talking about an upcoming course on “Making a search engine” on udacity.com. And my roomates and me decided to give the course a try. And this began my journey to get to know so many amazing people, who are freely sharing the vast repository of knowledge. I cannot how my life would be if I had not taken those courses. I never attended classes after my high school. Even in college, I used to bunk most of the classes, as the classes just seemed to make sense. Everthing taught was years old syllabus. Just one question stopped me from going to classes, “What’s the use of me studying, if I cannot work to make the life of other people on this planet a little better !”. Thanks to these couses I not just learn but build stuff too.</p><p>Here’s a list of people whom I would like to thank:</p><ol><li>Steve Huffman: Thank you, for the taking the time out to teach the “Web Development” course on udacity. <a href="https://www.udacity.com/course/viewer#!/c-cs253">https://www.udacity.com/course/cs253</a><br>I made my first website <a href="http://quizzera-dev.appspot.com/">http://quizzera-dev.appspot.com/</a> after taking the course and started understanding how large scale websites actually work.</li><li>Dave Evans: He is the guy who tricked me into learning python via the “Intro to Computer Science course”. He is one nerd I always admire for his simplicity with he explains tough concepts. <a href="https://www.udacity.com/course/cs101">https://www.udacity.com/course/cs101</a></li><li>Colt McAnlis: Performance matters. Whether its a website or an app. Super cool guy. I watched the “Compressor Head” video series by him, just because he is damn fun to listen.</li><li>Tim Roughgarden: Took the coursera course by him, <a href="https://www.coursera.org/course/algo">https://www.coursera.org/course/algo</a> and started appreciating the power of algorithms. I owe my placement to this guy.</li><li>CodeSchool Guys: Thanks you guys for helping me get started in web development.</li><li>Udacity Android Development Team and Ben Jakuben: Thanks for helping me build an app for myself. In just 2 weeks time I was able to learn android from scratch and make an app. <a href="https://play.google.com/store/apps/details?id=com.coolcrazyapps.statuscentral">https://play.google.com/store/apps/details?id=com.coolcrazyapps.statuscentral</a></li></ol><p>Thank you, thank you. For giving free education to one and all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=478887869dc9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>