<?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 Ajeesh Achuthan on Medium]]></title>
        <description><![CDATA[Stories by Ajeesh Achuthan on Medium]]></description>
        <link>https://medium.com/@ajeeshachuthan?source=rss-76db82c4547c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2jRIXL4PHB6WyLHxtQzweA.jpeg</url>
            <title>Stories by Ajeesh Achuthan on Medium</title>
            <link>https://medium.com/@ajeeshachuthan?source=rss-76db82c4547c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:05:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ajeeshachuthan/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[Things to consider while you build your next mobile app product!]]></title>
            <link>https://medium.com/@ajeeshachuthan/things-to-consider-while-you-build-your-next-mobile-app-product-22d79ea1a151?source=rss-76db82c4547c------2</link>
            <guid isPermaLink="false">https://medium.com/p/22d79ea1a151</guid>
            <category><![CDATA[rest-api]]></category>
            <category><![CDATA[mobile-apps]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Ajeesh Achuthan]]></dc:creator>
            <pubDate>Fri, 07 Jul 2017 06:26:50 GMT</pubDate>
            <atom:updated>2017-07-07T06:26:50.902Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“Great companies are built on great products” — Elon Musk</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*3VoVg-NXfpA1Q8YBQGbmdQ.jpeg" /></figure><p>Well, it’s easy to build a mobile app, if you know a couple of programming languages like Java (Android), C# (iOS) on the client-side to PHP or Python in the back-end.</p><p>But is that all that is needed to get an app live which users would love to use?</p><p>Let’s take a look at certain aspects to consider before laying architecture for your mobile app.</p><p><strong>Mobile app - Handle with care</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/140/1*I1fXWrh2LbAkr7lB0bX73Q.jpeg" /></figure><p>Yes. It’s fragile, lightweight and it can crash!</p><p>It’s time to avoid squeezing in business logic into your app. Serve data (after all those ordering/paginations/calculations blah blah…) to your app, display-ready.</p><p>Your app should be kept free from performing any kind of heavy data processing (chronological ordering, ascending/descending sorts) other than parsing and displaying them. Agreed that it is an ideal statement and there might be times you might have to ignore it. Nevertheless, I’d suggest you stick to the fact that apps are light weighted. To ensure better performance, don’t bombard it with logics and processes.</p><p>Let the big daddy server take care of it.</p><p><strong>Loading…</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*DQD2jgFkU3988jJnRXLr8g.jpeg" /></figure><p>Patience is a virtue, they say. Well…not always. Having to wait for each and every screen you navigate through is not always a good idea.</p><p>Don’t confine yourself from serving data which a particular screen needs. Send along associated data in the same response which the user would expect to see without any delay.</p><p>For instance, let’s take a look at the below screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/270/1*gCeZq1CMJ6kmlO9EMYvg7w.jpeg" /><figcaption>Lists of products — Sellfie App</figcaption></figure><p>Ideally, the API response for this screen will have a collection of <strong>product name, amount, sold count, order details and other meta data</strong>.</p><p>Now, let’s take a look at what happens when you go inside on one of the listed cards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/270/1*SZK38dyf4z02hs8sjmH0zg.jpeg" /><figcaption>Additional informations like description, inventory shipping charge — Sellfie App</figcaption></figure><p>Well yeah, a lot more data!</p><p>In the first look, there would have been two API calls, one for listing the collections of cards and the other for fetching data for the individual cards. More the API calls, more the user has to wait for each navigation.</p><p>Always focus on reducing API calls between screens. Having to see ‘processing’ or the boring spinner every now and then is not a good user experience.</p><p>Use eager-loading wherever required in a balanced proposition to reduce multiple API calls between screens.</p><p><strong>Caching - Those ‘never-gonna-be’ fast APIs</strong></p><p>Does your mobile app feature activity feed (something similar to the Facebook feed)? or a never ending product list?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/270/1*SDAbqdCY_QvvTOJwJG44cA.png" /><figcaption>List of Products/Offers — Myntra</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/270/1*wM3sAxhbECABTwtnV2Fxrw.png" /><figcaption>List of restaurants — Zomato</figcaption></figure><p>Retrieving data from a cache source will tremendously reduce both latency and unwanted hits on your database.</p><p>The API which gets the list of objects (w.r.t the above screens) will be frequently called every time a user navigates to these screens. If you have 1000 active users simultaneously accessing these screens, the app will be hitting a request to this GET API, which in turn hits the database * 1000 times (<em>Well it hurts </em><strong><em>:( </em></strong>)</p><p>If you have a list of data to be frequently read (by n number of users at a time), build that GET API on top of a cache layer on the server side.</p><p>Read data from cache rather than from your database if it will be frequently accessed. Using a cache layer here reduces the latency of the API.</p><p>And most importantly…</p><p>You will not crash your server!</p><h4><strong>Mobile App Analytics</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*UMNu2qKMH7GUzVAjXypvTw.jpeg" /></figure><p>You added a new feature ‘Yo!’ on your P2P payment app and you ‘think’ it will make your app cool. But in reality your users are embarrassed with the feature and you never realised.</p><p>You kept releasing new features, ‘Yeah’, ‘Hey’, ‘Hi’…and lately, your users started waving ‘Bye’ and uninstalled your app!</p><p>Not a good day for you.</p><p>In today’s world, agility is very important. Intuitions never works when you release a tech product out in the market. Every touch the user makes on your app matters! Believe me, it does!</p><blockquote>The status feature of WhatsApp which was rolled out in February had an uncanny resemblance with rival messaging platform Snapchat’s Stories, which allowed users to share photos, animated GIFs or short videos overlaid with text, scribbles, doodles and even emojis which would be visible to friends you share with, for 24 hours, before disappearing automatically. However, not everyone was a fan, and many users preferred the older feature. Now, both options will be available in sync, and a user can choose the one they prefer.</blockquote><p>“<em>Many users preferred the older feature</em>” — Well, how did WhatsApp know what the users’@ preferred?</p><p>This is where analytics comes into picture.</p><p>Insights on critical actions performed by a user on your app is very important for its success. This lets you take a call on what features should ‘live’ and what to ‘die’. With analytics in place, you will know your users are annoyed with that ‘Hi’ feature in your app and thus killing it in the next release so that your app survives!</p><p>The usage of an analytics tool is not just about displaying user events, but also to act on it to improve the active user sessions.</p><p>All analytics tools which are available in the the market offers powerful features like segmented engagements, user-drop off tracking, sending automated messages to inactive users and so on.</p><p>Keep in mind what analytics SDKs you would need to integrate based on your business decision and the features of it you would like to integrate (push notifications, in-app notifications — <a href="http://info.localytics.com/blog/push-messaging-vs-in-app-messaging-whats-the-difference-for-app-marketing">more on this</a>). It should be integrated from the beta release on-wards as doing so in the future doesn’t make much sense. You need to know what your users do from the first day of roll-out.</p><p>Some of the analytics tools which I personally prefer — <a href="https://clevertap.com/">CleverTap</a>, <a href="https://www.appsflyer.com/">Appsflyer</a>, <a href="https://www.localytics.com/">Localytics</a>, <a href="https://developers.google.com/analytics/solutions/mobile">Google Analytics </a>(Free!)</p><p><strong>Push Notifications</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*w1-shOqV6uUc06iyxUkO7A.jpeg" /></figure><p>Effective communication is important in a relationship between two people. This holds true for your users and app.</p><p>Push notifications play an important role in maintaining relationship with your customers.</p><p>These can be delivered either through an analytics tool or from your server.</p><p>Now what is the difference?</p><p>Like I said, analytics tools allows you to create and run engagements, campaigns via push notifications.</p><p>But it is equally important to send messages to the user when certain actions are completed/triggered, for example:<em> ‘Congrats! You received a new order’</em>.</p><p>For this to happen, your server should collect the GCM id (Android)/Apple push id (iOS) of the device when a user registers on your platform. If you have them stored, you will have the control of sending push notifications to a user when certain system events are triggered.</p><p>Always include a server side push notification module as part of your back-end architecture which programatically allows you to send system specific push notifications when certain action/events are triggered.</p><p>Some examples of notifications sent from a server:</p><p><em>‘You have received a new order’, ‘You have a new message!’, ‘Your account upgrade has been approved by our team’ .</em></p><p>I personally prefer using <a href="https://onesignal.com/">OneSignal</a> for sending push notifications from back-end. It’s an all-in-one platform for push notifications which provides wide range of SDKs for the platform of your choice, push notification delivery statistics, push notification scheduling and more.</p><p>They have multiple servers which deliver notifications and the service is highly scalable. They provide REST APIs which can be integrated with your server, and a push notification can be sent by requesting to their API with the one-signal-user-id and message. OneSignal identifies the type of client (Android/iOS/Chrome) and delivers the notifications.</p><p>And the best part, it’s free :D</p><p>Building a mobile app product requires a lot of iterations and you will face challenges at each stage of your product life cycle . But thinking ahead of time on what could come and what would be needed makes a better planning.</p><p>Hope this post helped you understand some best practices for rolling out a mobile app product :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22d79ea1a151" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>