<?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 Mihir Shah on Medium]]></title>
        <description><![CDATA[Stories by Mihir Shah on Medium]]></description>
        <link>https://medium.com/@mihirshah_?source=rss-17210173b5c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*n2rVXhXgLxIbVaafdV_5sw.jpeg</url>
            <title>Stories by Mihir Shah on Medium</title>
            <link>https://medium.com/@mihirshah_?source=rss-17210173b5c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:10:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mihirshah_/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[How to Make an App like Uber: A Million Dollar Guide]]></title>
            <link>https://medium.com/hackernoon/how-to-make-an-app-like-uber-a-million-dollar-guide-bd289d892d15?source=rss-17210173b5c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd289d892d15</guid>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[uber]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[app-development]]></category>
            <dc:creator><![CDATA[Mihir Shah]]></dc:creator>
            <pubDate>Wed, 02 Aug 2017 11:46:38 GMT</pubDate>
            <atom:updated>2017-08-29T15:39:34.640Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*alE9n6ryF3QThkPdBqY0Og.jpeg" /></figure><p>Do you want to build an app like Uber? If yes, you may have been advised against building it as there are 2000+ such applications.</p><p>Do you know that in 2015 Rob Sadow saw a huge problem with the <strong>on-demand car pooling industry</strong>:</p><ol><li>85% working professionals were driving themselves to work each day</li><li>And, they contributed 6.2 tonnes of CO2</li></ol><p>Rob wanted to fill this gap and launched his own mobile app. Shortly, after 4 months of launching the application, Rob saw a whopping 20,000 plus rides and received $5.2 Million in funding.</p><blockquote>Now, most people may have never heard about Scoop before, and there are similar gaps that on demand applications can fill. Unfortunately, many entrepreneurs do not know how such apps are built, and unknowingly ignore the benefits of building such applications.</blockquote><h3>What will you learn here:</h3><p><strong>1. Features and technology required to build an MVP</strong></p><p><strong>2. How to implement those features</strong></p><p><strong>3. Building the perfect backend for your application</strong></p><p><strong>4. Selecting the marketing tech stack for your MVP</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5ba166%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5ba166%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc94023ae452d66d5b1db62c2e74d578/href">https://medium.com/media/bc94023ae452d66d5b1db62c2e74d578/href</a></iframe><p>An app like Uber, even in it’s most basic form should be able to allow users to request rides and make cashless payments. The entire ecosystem should provide real-time interactions between the server and application and process payments automatically upon completion of rides.</p><p>On top of that, refunding and rating drivers is another crucial factor to build an economically viable marketplace.</p><p><strong>Let’s look at these important features for MVP and how you can build them.</strong></p><p>● The first feature that comes to everyone’s mind is, real time tracking and notifications. Building which requires optimising the code for performance, socket programming and communicating with various Google Maps APIs.</p><p>● The app should also allows users to register using the mobile. Backed with the proper security setup, the details a user enters will then be stored on the database designed for this application.</p><p>● To request a cab, the app utilizes Google Maps to allow users to drop a pin upon the map. As the passenger confirms a cab request, a notification is sent out to the closest drivers. The distance, ETA can be easily returned using Google Map APIs.</p><p>● When a cab is booked, a push notification needs to be sent out. The app’s server component can either be custom created or can be implemented using 3rd party providers. For an app MVP we prefer Amazon’s SNS, as it is lightweight and costs little to nothing to the startup.</p><p>● Sending Push notification also requires SSL connection, which may feel be the hardest part of implementation.</p><p>● In order to facilitates payments via application, Braintree provides SDKs for both iOS and Android. Integrating those SDKs allows you to auto-deduct payments, invoicing and make refunds.</p><p>To start billing of a ride, the app can leverage motion detection.</p><blockquote>In short, your first MVP product should be able to let users request a service(ride), send push notifications, process real-time payments and use Google map API to pin a location. This all can be possible on a scalable and reliable backend architecture.</blockquote><p>Of course! This was just an overview… it takes a lot more to build an app . Unless you are a Polymath, you need to hire developers with the following skills:</p><ol><li>Mobile Apps: Objective-C, Java, Swift</li><li>Backend services for the apps: Node.js and PHP</li><li>App databases: MongoDB and MySQL</li></ol><p><strong>Now, what if…</strong></p><p>Let’s assume you’ve built the app with the best possible technologies available, and your app is so great that it is built on top of recommender algorithms to completely automate your tasks.</p><p>But.. you later discover that the you need to pivot the product to survive. But now that you’ve exhausted your budget, you can’t pivot to reach the product market fit.</p><p><strong>Truth to be told…</strong></p><blockquote>You don’t need an exact Uber technology to test the hot waters and acquire users. You need a minimum feature based product to test if you are heading in the right direction, and then build more as you progress.</blockquote><p>During it’s initial phases Uber didn’t had a state of art architecture, they used to build as they progressed. <br> <br> <strong>So.. what tech stack fits well for an MVP?</strong></p><p>A simple app built on top of the following will easily be able to handle thousands of users and permits scalability during sudden surge:</p><ol><li>High performance natively built consumer facing apps on programming languages like Objective-C and Java, one can also use Swift here.</li><li>Well optimized stack of web services on PHP and/or node.js</li><li>Well designed database storage on MySQL + MongoDB will be able to handle the loads easily.</li></ol><p>Back in 2011, Twitter used to rely on a simple stack of MySQL to process 250 million tweets. In this case MySQL and MongoDB can easily handle any sudden surge.</p><p><strong>But software development is risky…</strong></p><p>That’s why we go for MVPs and proper project management methodologies. Here’s what you should do for proper planning and execution of app development plans:</p><ol><li>Divide your projects and tasks into priority order.</li><li>Ensures tasks have been assigned properly to the designers, developers and project managers.</li><li>Creates deadlines for each tasks</li><li>Lists the top 5 priority tasks for each of your team member.</li><li>Remain up-to date with the project progress, problems and iterations</li><li>Talk to your development team and be an active part of the development process</li></ol><h3>Building the perfect backend for your application</h3><p>People learn from mistakes, but you haven’t made one. So, how would you learn?</p><blockquote>We have built hundreds of applications, some of which made it to millions of users within a month. The teams working with us often panicked, we spent nights fixing the architecture which was supposed to handle massive users.</blockquote><p>That was back in 2011, startups rarely cared for scalability of backend and features when they were into MVP phase. During those days even Uber was struggling to cope with surges.</p><p><strong>Post 2011, Node.Js happened…</strong></p><p><strong>Building real time location, display and tracking</strong></p><p>To build so functionality, you need to focus more on data extraction and optimization.</p><ol><li><strong>Do you know that an Uber like app communicates with the server after every 4 seconds to provide real time information? <br></strong> <br><em>Depending on how accurately or loosely you wish to track the cab’s location, you can change the frequency of communication.</em></li><li><strong>In case if you are wondering, the app frequently needs to communicate ETAs, GPS location, calculate the shortest distances, and other information that may be required. </strong><br> <br><em>The app utilizes following APIs to collect information: Google maps direction API, Distance matrix API, Geo-fencing, Google Place API, Google Maps Geo encoding API.</em></li><li><strong>This is going to be the most important part of building a real time experiences. A half-duplex-socket that could push real time information between your servers and mobile apps. </strong><br> <br>The reason why these protocols are so important is because they help reduce the communication overhead. <br> <br>In absence of sockets, a port has to be opened and closed whenever server receives a request. Also, HTTP protocols were built to pull data, and if a server wants to push data it has to poll.<br> <br>Unlike these HTTP protocols, a socket connected to a server always keeps a port open to allow easy exchange of information.</li><li><strong>Concluding this, you should have Nginx as your web server. Apache is another popular server, but it doesn’t performs well with real time, dynamic information.</strong></li></ol><h3><strong>Processing Payments through the app</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*bc5kBUfy5JWRug2L6w9gnQ.jpeg" /></figure><p>Braintree is a preferred payment gateway for such application, in the next 2 minutes we’ll show you why:</p><ol><li>Do you know that up to $50,000 total in transactions, Braintree won’t charge you anything? How awesome is that?</li><li>Another reason for using Braintree is that it facilitates auto-payments, refunds, monthly/weekly/bi-weekly recurring payments. <br> <br>And in case, if you are looking to add a split payment feature, Braintree also helps you integrate this functionality.</li><li>“<em>But I want to build my own Payment gateway…</em>” Wait, before you even think of that idea, kill that thought! It is not feasible to build your own payment gateway while being a startup. There are many compliance, complicated technologies and high costs involved. We would advise using an existing Payment Gateway.</li><li><em>But what about data security?</em></li></ol><p><em>That PCI Compliance thing</em>…Most app developers will tell you not to worry about it because most of the Payment Gateways are PCI compliant. <br> <br>While registering your account with a Payment gateway, most of them ask you to fill and submit a PCI SAQ_A-EP form. This is a part of self auditing your data security and declaration that you’ve followed compliance.</p><p>Even if you don’t know tech, please talk to your developer and make sure that you fill the right details.</p><blockquote><strong>A word of caution </strong>you still need to make sure that you are doing your part of data security and self auditing. The moment your app completes 20,000 transactions, you will be under VISA’s radar.</blockquote><ol><li>If it seems like a lot, don’t worry there’s little left. <br> <br> Ask your developer and make sure that he integrates the SDK properly with your app. Developers often integrate PG’s API rather than integrating the SDK with Mobile app.</li></ol><blockquote>This is a poor implementation and leaves sensitive information flow through vulnerable networks.</blockquote><p><strong>Other than that, you need to:</strong></p><p>1. Make sure to use SSL encryption<br> 2. Never store any credit card information locally<br> 3. Use Braintree iFrames whenever possible</p><h3><strong>Scheduling and booking rides</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*KLIKWuTm2716ph-2vg2cOg.gif" /><figcaption>Lyft</figcaption></figure><p>The ride booking or scheduling mechanism can work in two ways:</p><p>1. When an user requests a ride, the request goes out to the nearest highest rated driver. The driver then receives a notification upon which he can choose to respond or ignore. If he chooses to ignore, the request will go to the next nearest driver. <br> <br> OR<br> <br>2. When an user requests a ride, the request will go out to all the drivers in the proximity. Whoever accept first will be awarded the ride. <strong><br> <br></strong>A simple scheduling algorithm that has been well optimized for such an app looks something like this:</p><p><strong>Formula: 0.7*driver’s proximity + 0.9*driver’s rating + 0.7*UPR + 0.4* route traffic</strong></p><h3><strong>Building backend services using PHP and Javascript</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EMvZ96oQx1qJnw4ps1okBA.png" /></figure><p>What’s ideal is not always right. You can always build the entire stack on node.Js, but such an implementation will bring in additional costs that could be daunting for a startup business.</p><blockquote>A perfect backend for such app would have web services built on top of PHP and Javascript.</blockquote><p>A complete node.Js backend would involve using two or three MongoDB servers, which may increase the operating cost significantly. <br> <br>By building some of the web services on PHP, you reduce operating cost by including MySQL.</p><p>Also, PHP works way better with MySQL than Node.js.</p><blockquote>So, Two or three MongoDB servers along with MySQL and PHP/Node.Js would make a perfect backend to test your MVP.</blockquote><p><strong>Node.Js is really really important for building real time applications. The usefulness of node.Js is best described below:</strong><br> <br>1. In terms of handling real time features, it does so by sending an asynchronous task to the event loop, with a callback function and then executes the rest of the program. <br> <br>2. It again speeds up the work using realtime websocket running over TCP, reducing the any delay caused by HTTP.<br> <br>Next, you need to have two separate PHP-Laravel based implementations to build the web app and a REST API. With such an implementation, any future upgrade is easy to push, without the need to need to upgrade the web application.</p><h3><strong>Building a scalable architecture</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*EW7BA8uF7ghJ4sDLyhYHeQ.jpeg" /></figure><p>Uber started with a simple LAMP(Linux, Apache, MySQL and PHP) stack when they started.<br> <br><strong>The result…</strong><br> <br>LAMP stack couldn’t deliver due to performance issues and double dispatching, Or, in words of Curtis Chambers of Uber LAMP stack</p><blockquote>Leads to issues with double dispatching<br> — Curtis Chambers, Uber</blockquote><p>They had to quickly change and build something new, as they further faced the issue of scaling. <br> <br> Put simply, this is where we need node.Js. <br> <br> A simple highly scalable backend architecture looks something like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*iB60SN_O963CxWDpJOri2w.png" /></figure><p>Understanding this architecture is really easy. We are separating three components from each other: <br>1. Services to store and handle real time location based data<br>2. The real time logic <br>3. The business logic<br> <br>Let us explain what we mean by real time logic and business logic. Anything that has to do with payments, invoicing, sms, and other business related stuff is usually deployed on a server which we will call business logic. This portion also handles the third party SDKs and APIs.<br> <br>Anything that has to do with real time data and tracking, notification will then be taken care by our “Real time logic” which has its own server and operates independently of the business logic.<br> <br><em>90% of all incoming data in such apps is location based information.</em> This data should be stored on MongoDB servers, so that web services can request the information only when the need it.<br> <br>This architecture also prevent total system failures. Imagine a scenario, where you third party payment provider has failed. Your system currently loops around to get a response. The ride has already been finished, and the driver can’t be assured of the payment as the system is unresponsive, neither can he pick up another ride. <br> <br>With logic separation, both systems can operate independently. And failure of one won’t bring in a total system failure.</p><p>A user will find a system slow if the response rate is below 500ms. The proposed architecture has the potential to deliver as low as ~200ms as response times.</p><p>The app at a glance now:<br>1. Developed with Minimum viable features<br>2. Optimized for performance<br>3. Optimized for scalability<br> <br>Your future growth now depends on the type of users you acquire and the KPIs you’ll set for them. <br> <br>It’s highly unlikely that you’ll be able to see your users use the application. <br> <br>Then, how will you understand what they are doing inside of your app? How will you make sure that you are acquiring the right users? How will you know why that user uninstalled your application?<br> <br>In the next question, we hope to answer some of your questions. <br> <br>Marketing tech stack for an app like Uber<br> <br>To build a high performing market economy most of the decisions that app developers take should be based on user behavior.</p><p>The first step in understanding your user’s behaviour is to…</p><h3><strong>Segment your app users and monitor KPIs</strong></h3><p>Dividing your app’s users into different segments allows you to discover differences in their behaviours. <br> <br>For example, you may observe a 100% increase in rides, but what if this increase is coming from only two out of four segments.</p><blockquote>Upsight SDK allows you to discover your users, understand their attributes and build segmentations. After creating segmentations, you can perform targeted marketing and check the results.</blockquote><p>Upsight provides metrics explorer which helps developers understand how different variables affect their core KPIs. Upsight allows you to build KPIs specific to each user segment.</p><p>Some of the common growth KPIs that you can extract using Upsight are:</p><ol><li>Monthly average users</li><li>Daily average users</li><li>Average revenue per users</li><li>Total number rides by segments/users</li></ol><p><strong>Crash reporting<br> <br></strong>Crashlytics is one of the most preferred and used crash reporting tool being used by startups.<br> <br>Whenever your app crashes, you can get the crash analytics real time with a beautiful insightful reporting.<br> <br>We recently did a research on top performing apps on Playstore, Crashlytics was one the most used tools for 90% of the category defining applications.<br> <br><strong>Providing in-app customer support<br> <br></strong>App stores do terrific in terms of distributing your apps to billions of users, but they often bring in a huge disconnect between app developers and users. <br> <br>Most of the time, a user frustrated by an app would end up leaving one star review to reflect the dissatisfaction. This reduces an app’s discoverability in the app store.</p><p><strong>Providing ZenDesk based in-app customer servicing helps reducing this gap by directly putting user in touch with the app’s developer. Some other benefits of using ZenDesk are:</strong><br> <br>1. ZenDesk automatically collects the device information, which otherwise would require frequent back and forth emails, that often ends up frustrating customers.</p><p>2. ZenDesk also has a companion mobile app for support teams, which provides an easy to use micro blogging like website experience.</p><p>The only thing many have against ZenDesk is the involvement of support tickets. And, that’s why the rest prefer using Intercom. This is completely subjective.</p><p><strong>Growth hacking — Getting more app reviews and ratings<br> </strong><br>Asking for ratings and reviews is important. A common bad practice that we see is to prompt a user after completion of some number of events. This often feels intrusive and frustrating to most app users. <br> <br>By now, you should know that happy users are less likely to put a review, an angry user is most likely too.<br> <br>The only thing we suggest you to change is “The way of asking”. Use Apptentive… <br> <br>Apptentive utilizes a proprietary algorithm to identify user sentiments and prompt users at the right time to get desired ratings</p><p><strong>Reduce app uninstalls<br> </strong><br>Uninstall.io is an analytics tool that helps app developers understand important signals which leads to high uninstall. It helps you reducing app uninstall by:</p><ol><li>Identifying problems that users face within the app, or frustrating features/experiences that are causing these uninstalls.</li><li>Identifying advertising campaigns that do not retain users and are extremely expensive.</li><li>Finding users who uninstalled your app and provides a channel to re-target the lost customers.</li></ol><p><strong>A/B Testing<br> <br></strong>You may have done your research well and have narrowed down to the features to reach product-market fit. <br> <br>But what if you couldn’t decide between two features closely and want to test them as quickly as possible, without frustrating your entire user base? <br> <br>Using Optimizely SDK, you can divide your app’s user based into different parts. These parts will then see different features. <br> <br>You can collect information on what features are performing the best, what don’t work and take your product development strategy forward using these insights.</p><p><strong>Adding the element of virality<br> <br></strong>Remember when you got that text/Whatsapp from someone you know about a free ride for using Uber for the first time. <br> <br>To influence the buying decisions based on trust, we recommend using Appvirality for Referral marketing.</p><p>The best part of using such tools to market your app lies that it takes the referrer’s authority not just to the contact, but also to their social networks.<br> <br>Appvirality analytics dashboard provides a data driven approach for target marketing by using invites, clicks, install and revenue to channel efforts.</p><p><strong>Drip emails<br> <br></strong>We consider using drip campaigns as a vital part of building a ride sharing marketplace. As a marketplace never remains stagnant, it grows and requires the customers and users to grow with it.</p><p>Drip email marketing software makes it very easy to schedule drip email campaigns.<br> <br>Depending on your target audience, you can push re-engagement emails, email about new updates and features within the application, keep them training with growth hacks/good practices concerning your marketplace and share customer stories to keep them motivated.</p><p>Still struggling with your MVP, Say hello on <a href="https://twitter.com/mihir_simform">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd289d892d15" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/how-to-make-an-app-like-uber-a-million-dollar-guide-bd289d892d15">How to Make an App like Uber: A Million Dollar Guide</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why use AWS SNS for mobile push notification?]]></title>
            <link>https://medium.com/@mihirshah_/why-use-aws-sns-for-mobile-push-notification-55a46f703b11?source=rss-17210173b5c------2</link>
            <guid isPermaLink="false">https://medium.com/p/55a46f703b11</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Mihir Shah]]></dc:creator>
            <pubDate>Wed, 31 May 2017 00:00:00 GMT</pubDate>
            <atom:updated>2017-06-27T13:02:24.526Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*X6Ique-pXnloosQH.png" /></figure><p><strong>Why use AWS SNS for mobile push notification?</strong></p><p>AWS SNS is a cloud-based web service which enables devices and apps to send and receive push notifications from AWS cloud. It is widely used by millions of apps including Periscope, Hike, Yelp and Tinder, to name a few.</p><p>AWS SNS manages multiple type of notifications including push messages, email and SMS in real time between publishers and the app users. These notifications are fast, efficient and highly scalable.</p><p><strong>Let’s break it down into smaller steps — to know exactly how you can configure it with ease?</strong></p><p>So, how does it work?</p><p>* Create a topic(which is basically a communication channel to send the notifications)</p><p>* Subscribe to that topic(which means connecting an end point to the topic, where end point could be a web server, mobile app or an email address)</p><p>* Publish to the topic(Assigning the message to the topic, you’re free to create different messages for each protocol)</p><p>* Define the policy.</p><p><strong>But why should you even consider AWS SNS?</strong></p><p>* You’re done! The message will be sent to the subscriber (devices, web server) in real time or on assigned time.</p><p>The cloud web service market is very saturated and there are other vendors like Google Firebase, IBM and Microsoft who offers web push services with their cloud offerings.</p><p>AWS provides a range pre-built services for:</p><p>1. <strong>Easy segmentation</strong>: You can easily segment users in different categories and send custom updates, promo codes or news personalized to their preferences.</p><p>2. <strong>OS Compatibility</strong>: AWS SNS allows you to send push notifications to different devices across different operating systems like Android, iOS, Windows, Fire OS etc using one single API, instead of calling different APIs.</p><p>3. <strong>Transfer Protocols</strong>: It also supports a wide range of services and transfer protocols including their own Amazon SQS and HTTP/S, email, SMS, Lambda.</p><p>4. <strong>Subscribers</strong>: You can have as many as 10 million subscribers for each topic or channel which I believe covers nearly 90% of the apps, however for requirements larger than that AWS also provides custom offerings.</p><p>5. <strong>Global reach</strong>: Unlike other web services, AWS SNS can send notifications to worldwide users without any regulatory and compliance restrictions.</p><p>6. <strong>Built in-Analytics</strong>: AWS has in-built analytics tool which tracks the delivery &amp; failure rates and serves insights for better engagement and optimization decision making. You can also track the dwell time for the deliveries and customize as per your promotional strategy.</p><p>7. <strong>Scalable APIs</strong>: A single API call can deliver notifications to upto 10k devices, which reduces the server side loading and doesn’t compromise the app performance which is much better to other poorly configured mobile apps that crash or doesn’t send real-time notifications.</p><p>8. <strong>No limitations</strong>: The publishers get the ability to enforce the explicit sending limits to the subscribers, which means that you can send ’n’ number of push notification based on defined triggers and user action.</p><p>9. <strong>Multinational OTP support</strong>: AWS also supports phone numbers of more than 200 countries, making it highly scalable for your business.</p><p>10. <strong>Free till the first millionth request</strong>: There is no limit on how many requests you can make, and the good part is, they don’t charge for the first 1 million requests.</p><p>11. <strong>Device Compatibility</strong>: AWS SNS is compatible with all the platforms(Android, iOS, Windows) and most of the devices. In fact, they have built AWS SDK for Java, which you can be integrated seamlessly with your IDE.</p><p>12. <strong>Finally, a 100% managed service</strong>: The best part, AWS SNS is a managed service, so you don’t have to run or maintain.</p><p>Though I have shared the benefits of using AWS SNS, there are a few downsides that you should know as well. For example, if you have an iOS application, you won’t be able to track notification analytics since Apple’s APIs won’t respond back with fail or success status, making it difficult to measure the result of your campaigns.</p><p>Again, many would refute my concern with this, but as someone who builds customer-centric solutions for a living, <strong>not knowing whether app’s users love or hate push notifications is a huge problem</strong>. We often build workarounds to deal with these situations.</p><p>Other than such similar issues, AWS SNS is a dynamically scalable solution for any business that needs push notifications.</p><p>I recommend and use AWS SNS for push notifications, how are you enabling push notifications for your app? — Feel free to share your thoughts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55a46f703b11" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Minimum Viable product to prediction: A Learning Cycle]]></title>
            <link>https://medium.com/@mihirshah_/minimum-viable-product-to-prediction-a-learning-cycle-a3187c4503c7?source=rss-17210173b5c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3187c4503c7</guid>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Mihir Shah]]></dc:creator>
            <pubDate>Tue, 16 May 2017 00:00:00 GMT</pubDate>
            <atom:updated>2017-05-29T11:33:03.165Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hzoumyaG5FF9IeZT9IWPxQ.jpeg" /><figcaption>Lean impact</figcaption></figure><p>An MVP is not just a product, but a process of getting through the build-measure-learn feedback loop with the minimum amount of product iterations and experiments. Every product starts with an idea, and they build an MVP wrangling about what features to have or not.</p><p>However, some(many) startups believe MVP as a product with half or more features are blended in or a quicker way to take the product to market.</p><p>This explains the perception:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*sCwK7W9FDKhqCvOzEURBMQ.png" /></figure><p><strong>So, what would an MVP process look like?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*qzwxEOGbNM-wnCh7cnSoQg.png" /></figure><p>And, this is where you would end up having an average product with flaws and bugs which will hurt your reputation and most importantly your customers.</p><p>As you can see, it should be a strategy and process of idea generation, prototyping, presentation, data collection, analysis, and learning. One seeks to minimize the total time spent on the iterations and make sure to obtain a desirable product-market fit.</p><p>The startups approach this problem in a way that how many customers will sign up for the free trial and we believe it is enough information. But, it can lead to a lot of waste like how many features do you actually need to appeal to customers(early adopters).</p><p>Every extra feature is a form of waste, especially when you delay it, then it comes with a potential loss of learning and time cycle.</p><p>So, when you really create something and not have enough early adopters, your options boil down to these:</p><p>1. Retry: Change the features in some way and try again. Or leave out the non-essential features</p><p>2. Move: Moving is heading in some direction with the product or feature without validating your hypothesis.</p><p>3. Fail: Quit without having learned much. Try another idea and repeat the loop.</p><p>Learning is very essential in the process unless and until you’re scratching a clear itch or building something for a quick flip.</p><h3>The testing phase:</h3><p>After analyzing some MVP testing campaigns, I came across these ideas to run the experiments:</p><p>1. Landing page</p><p>2. Interviews or surveys</p><p>3. Product Video</p><p>While running this experiments, we will try to answers these questions:</p><p>1. What are you trying to learn with this particular MVP?</p><p>2. What data are you collecting about your experiment?</p><p>3. What determines the success or failure of this experiment?</p><p>Let’s boil down.Pretend like you have an idea for a mobile app or any software product. You decided to have a landing page for the value proposition and learning. Landing pages are popular as a form of MVP because it is the easiest thing to build as they can offer you good ROI for the time spent and expenses on the current assumptions.</p><p>Also, you can test whether customers understand your idea, collect metrics on the best ways (Adwords, Social media, community launch) to attract users and if users are willing to sign up.</p><p>A landing page could be a limited version of your product or a paper prototype that attracts the early adopters to talk about your product or any magic algorithm intended to solve customer’s need.</p><p>In the second case, you can write some questions to test whether the customers(now respondents) would be happy with the existing features. Most of the survey forms could be integrated with your product page to even validate whether they will be willing to pay or not.</p><p>The good starting point can be the people in your network and then reach out to communities. Asking questions aren’t easy and most startups hate it but days spent doing this could save you months of development time and efforts.</p><p>When we talk about product video, it would be unfair not to mention Dropbox MVP test. Following the Lean methodology, Drew Houston (the CEO of Dropbox) released a four-minute <a href="https://www.youtube.com/watch?v=7QmCUDHpNzE">video</a> highlighting only the deployable(main) features of Dropbox and surprisingly it got 70k people signed up within days.</p><p>This approach really appeals to many startups(you won’t see a single launch without an explainer video); and also videos are an easy way to explain the intangible aspects of how your product(app) will work rather than just using static words and pictures.</p><p>The measurable metrics are:</p><p>1. Number of visitors</p><p>2. Number of people watched it halfway(Wistia does the job well)</p><p>3. The click through rate</p><p>4. Their sentiments(feedbacks)</p><p>5. And, the number of people signed up</p><p>When done with the assumption validation, you should have an idea of “Is this the outcome that I wanted to see or not?” If the answer is a clear no, you can be confident that there was a problem with the basic premise of the idea or your product positioning.</p><p>And you need to think of other experiments to get the desired output. However, if the answer is yes, or better than you expected, then you can continue with confidence.</p><p>Feel free to share your thoughts or say Hello ! on Twitter <a href="https://medium.com/u/d836abe35993">mihir shah</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3187c4503c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build a dating application?]]></title>
            <link>https://medium.com/hackernoon/how-to-build-a-dating-application-55d5ca0c8f5c?source=rss-17210173b5c------2</link>
            <guid isPermaLink="false">https://medium.com/p/55d5ca0c8f5c</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Mihir Shah]]></dc:creator>
            <pubDate>Wed, 29 Mar 2017 13:07:25 GMT</pubDate>
            <atom:updated>2017-03-29T13:08:45.730Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*Il9bzhhYxnO9pzndMUlPfw.png" /></figure><blockquote>Spoiler: This is the most extensive guide to build a dating app on the concept, building MVP, optimization, backend stability, application security, real time chat implementation, tinder matching algorithm and content moderation.</blockquote><p>Want to build an app similar to Tinder for the dating niche?</p><p>You probably have heard a lot about dating apps being saturated and competitive, but..</p><p>That’s completely subjective, and timely disruptions often validates unsaturation! Even more so, niche dating is heavily unsaturated.</p><p>In the words of <strong>Sean Rad, Tinder Co-Founder</strong>..</p><blockquote><strong>It’s not just about swiping left or right, it’s about the underlying philosophy.</strong></blockquote><p>Too good to be true? Let’s see!</p><p>Some niche dating apps that have seen massive success recently:</p><ul><li><a href="http://www.twindog.co/"><strong>Twindog</strong></a> got nearly 100k users within 2 months after launch</li><li><a href="http://www.bristlr.com/"><strong>Bristlr</strong></a><strong>,</strong> an app for Women seeking bearded men</li><li><a href="http://www.theleague.com/"><strong>The League</strong></a>, a dating app for people that are too popular</li><li><a href="http://www.rlsb.org.uk/tech-hub/tingle-app-dating-personalities-not-selfies"><strong>Dating for the blind</strong></a>, developed at the RLSB</li></ul><p>Now, your crazy dating app idea doesn’t seem to be that crazy, right?</p><p>Notably, such apps evolve out of self-passion, so, it’s safe to assume that you are already familiar with some attributes of your niche. You can quickly put together some of your ideas, discuss and test to see if you have a market for that.</p><p><strong>NOTE: </strong>If in case you are planning to develop a clone, you should understand that your market validation has already been done.</p><h4>What will you learn:</h4><ul><li>Different ways to build a dating app?</li><li>Building a dating app MVP</li><li>Optimising your app for usability, performance and security</li></ul><h3>How to create a dating app?</h3><p>Here’s the deal, there are <em>no set standards</em> of app development for startups. Typically, there are three ways to build an app:</p><ol><li>Use an app builder</li><li>Develop a custom app</li><li>Customize a Clone script</li></ol><p>Lets have a look at these options</p><h4>Dating app builders</h4><p>There are many dating app builders that allows you to drag and drop to create user interface, tweak backends and play around a little bit.</p><p>The best part about using these app builders is the ease they bring in:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FY1xIR-VG2bY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DY1xIR-VG2bY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FY1xIR-VG2bY%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d4f28877f6272a2b75e3d2c894a03845/href">https://medium.com/media/d4f28877f6272a2b75e3d2c894a03845/href</a></iframe><p>Most of these WYSIWYG builders charge a monthly fees for the app to function, they host and keep your backend. They provide UI elements that you can use to make your application.</p><p>To assist you in creating apps, most of these app builders provide documentation. They also provide on call support if things get complicated. But they suffer from some serious issues:</p><ul><li>They are <strong><em>limited</em></strong> in terms of customization, innovative features (for Tinder it was swipe)</li><li>In some cases, the code that powers the app <strong><em>cannot</em></strong> be exported and becomes inaccessible once you stop the monthly payments</li><li>Almost <strong><em>impossible </em></strong>to optimize user experience; a core of such dating apps</li><li>Limited in terms of what they offer for the <strong><em>rapid </em></strong>changes in technology</li></ul><p>While in future we can expect to have reliable app builders, but right now, they are poor choice to build a dating app.</p><h3>Develop custom dating apps</h3><p><a href="https://en.wikipedia.org/wiki/Custom_software">Custom apps</a> can either be <a href="https://en.wikipedia.org/wiki/Native_(computing)">native</a> or <a href="https://en.wikipedia.org/wiki/Cross-platform">cross platform</a>.</p><p>They require a database to store their data, and a backend to function. When built natively these apps run more efficiently. Here’s a comparative study of <a href="https://www.simform.com/blog/native-vs-cross-platform-development">native vs cross platform development</a> we wrote a while ago.</p><p>Developing apps this way also favors iterative product development. You can actually pivot your entire product if required. But…</p><p>Custom app development brings additional costs to the table. Other than that, there are no drawbacks to have your app developed in this way. If you really believe in your idea, head over to How to make a dating app using custom development.</p><h3>Dating (Tinder) app clone script</h3><p>Basically, clone scripts are source code replica of existing popular apps available on online marketplaces. With this option, you look up on the internet for an already existing code available on the dating app you want.</p><p>You end up finding a dozen Tinder clone scripts out there. After buying a clone script, you will hire a freelancer to customize and help you upload the app to relevant app stores.</p><p>These scripts usually cost between $100–700 and customization costs that a developer might charge. So far so good, right?</p><p>Not really! <br>Apple will crack down on such rip-off’s, sooner or later!</p><h3>Wesley Dyson on Twitter</h3><p>@pschiller I believe this is your department now. Rip-off apps should never be showcased by Apple. https://t.co/480Pf4qu5O</p><h3>Philip Schiller on Twitter</h3><p>@WesleyDyson @Adora Shouldn&#39;t happen. We&#39;ll look into it. Thank you.</p><p>There are other downsides to the approach as well:</p><ul><li>First of all, extremely minor customizations can be done by any developer with ease. But, in case of even a little bit of <em>complexity</em>, the cost of customization goes up <strong>drastically</strong>.</li><li>At worst, the <em>developer may fail</em> or refuse to work on the code at all.</li><li>Experienced developers usually straightaway refuse to customize such codes. And recommend writing the code from the scratch.</li><li>More chances are that the code <em>won’t have a proper documentation</em>, comments in place to help your developer</li></ul><p><strong>What about scalability?</strong></p><p>Scalability is something that has killed many startups that topped App store rankings in the past. Often, such codes are poorly written and <strong>won’t scale</strong> at all.</p><p>Given that there is a market for your app, you still need to <strong>innovate</strong> <em>at least by 10%</em> with your product. A clone script just isn’t something that helps you doing that.</p><p>It is worth knowing here that a majority of <strong>people who use such clone scripts are essentially blackhat marketers</strong>. Most blackhat marketers are <em>not driven by the desire to serve users</em>. They rather intend to spam, and monetize quickly. <strong>User retention is pretty low</strong> in such cases.</p><p>Finally, whether you use a Dating app source code, app builders or custom development to build your app, <em>you need to immerse yourself</em> in the process to build a successful dating app.</p><p>It may seems overwhelming. Don’t worry…</p><p>In the section below we will show you a possible approach to build MVP and optimize application features. Not only that, you’ll also be able to properly understand ins-and-outs of critical app features.</p><h3>How to make a dating app — MVP</h3><p>Creating such an app MVP would require you to have iOS, Android and backend development skills. iOS development is mainly done using Swift and Objective C, while for Android you need someone with a Java experience.</p><p>For backend, you can have Javascript, PHP or any other language that you prefer. The choice is completely subjective. The best way to move forward is by following a minimum viable product approach. You should be very careful on how you decide your minimum success.</p><p><strong>Tinder co-founder, Sean Rad admitted this during his talk at Google I/O 2014:</strong></p><blockquote><strong>We drastically underestimated what MVP was…everything was just going to collapse down for 24 hours because this architecture has its bottleneck and it won’t go past that.</strong></blockquote><p>This happened when Tinder was about to move from 20k users to 500k users overnight. And it was extremely stressful for Sean. So, it’s really important to come up with a properly defined MVP.</p><p><strong>An approach to MVP has been illustrated by Arum Kang</strong> of Coffee meets Bagel in the video below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7pT51EZNcso%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D7pT51EZNcso&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7pT51EZNcso%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/27927d330a80a03224a776957ab80ee8/href">https://medium.com/media/27927d330a80a03224a776957ab80ee8/href</a></iframe><p>The following should be noted very carefully from her talk:</p><ol><li>You can actually build your MVP <strong>without</strong> a <strong>technical co-founder</strong></li><li>It becomes easier to find a technical co-founder once you build a MVP</li></ol><p>Now that you’ve properly defined your minimum success (MVP), you are ready to move on the next section.</p><p><strong>Most commonly, we have seen the following features within dating apps:</strong></p><ul><li>Swipe gestures</li><li>Matching users</li><li>Content Moderation</li><li>Real time chatting</li><li>Geo location</li></ul><p>The goal here should be to create features for usability, performance and security.</p><h3>Optimize your dating app</h3><h4>Building Swipe Gestures</h4><p>Building swipe gestures isn’t very difficult, and any good developer can do that. Though, care needs to be taken while implementing the swipe gestures. Chances are your implementation may not be optimized for the target audience.</p><p>The following drastically affects user friendliness of your swipe transitions:</p><ul><li>Distance from the middle required for an action to take place</li><li>How much the card will squeeze upon swipe, how much it should rotate</li><li>How much the card should shrink upon swipe</li><li>The angle of rotation and it’s strength</li></ul><p>The animation below nicely illustrate how the minor changes influence the experience of these swipe transitions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/314/1*9epEAbRBSIqnnwkeoYu9CQ.gif" /></figure><p>Find out what works best for your target audience and optimize swipe gestures.</p><h3>Build backend for scalability</h3><blockquote>Many often ask for the easiest way to have a scalable app, and we often repeat — <strong>Easiest is often not the best way to build a scalable application.</strong></blockquote><p>For a MVP, a <em>MySQL</em> + <em>MongoDB</em> database along with Node.js works best for such applications.</p><p>Some recommend standalone MongoDB for such apps, which is not the best way. Most such recommendations arise from myths surrounding MongoDB, checkout the video below to learn about myths surrounding MongoDB.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fb2F-DItXtZs%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Db2F-DItXtZs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fb2F-DItXtZs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4d405b40f01adeaac9d5fbbec4db678b/href">https://medium.com/media/4d405b40f01adeaac9d5fbbec4db678b/href</a></iframe><p>Tinder itself used MongoDB and ran into many issues. It got to a point where they were eventually <a href="http://thenewstack.io/tinder-is-scaling-with-mongodb-and-some-help-from-objectrocket/">forced to move their focus</a> from product to scaling the service.</p><p>Designing a database on MongoDB is a bit tricky. It requires you to plan in advance on what features you wish to implement, and what information you would need to extract.</p><p>To sum up, all the non-structured data of your app should go to MongoDB and the structured one will be stored on MySQL database.</p><p><strong>Node.js and static serving</strong></p><p>Node.js is great for variable tasks…but It doesn’t works well when it comes to static content. Using a caching mechanism eliminates the problem. You’ll read more about that later in the blog post.</p><p>Let’s get back to scalability.</p><p>Technology scalability should be at the center stage on your immediate product roadmap.</p><p><strong>Chris Lalonde, </strong>(who scaled Ebay to millions of users) spoke the following in context of scalability for startups:</p><blockquote><strong>I know a dozen startups that failed from their own success. These problems are only going to be bigger.</strong></blockquote><p>The graph below well illustrates importance of scalability from an ROI perspective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*0stP1_sbQ7AKotD0Aopv_Q.png" /></figure><p>The green line in this graph seems way too fancy to be true; more often than not, it isn’t.</p><p>For most startups, the actual path looks something like shown in the graph below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*tDqYPcgslNlLOkReU1eL9w.png" /></figure><p>Let’s take scalability even a step further, and <em>optimize the server queue</em>. Server queue is basically a model of how your app will handle and process requests.</p><p>So, while building server model for a dating app, we recommend rather than going for a <strong>N servers + N queues</strong> or single server + single queue, we prefer <strong>Single queue + N servers</strong>.</p><p>This ’N’ would depend on your incoming traffic, a part of system design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*Sv27Au7cdtyI4vVRfasU5w.jpeg" /></figure><p>Now, you can sit down with your product and development team to identify:</p><ul><li>What’s immediately going to happen after you release your app(frequency of messages, number of requests, etc)?</li><li>What model can handle the least requirements?</li><li>What are the risks involved?</li><li>And most importantly, How can you move to a different arrangement if required?</li></ul><p>Before proceeding, talk to your developers if the single server + N queue actually solves all of your concerns.</p><p>In next section, will help you optimize your dating app for a much better performance when it comes to node.js serving static files.</p><h3>API Caching to make node.js faster</h3><p>As we told you earlier, node.js isn’t the most efficient framework for serving static content(e.g images). A caching method would bring <em>huge performance boost</em> to node.js. Any request with caching appears to have been processed <em>instantaneously</em> to a user.</p><p>For the sake of simplicity, think about Caching as something that <em>stores information temporarily</em> so that it is easily retrievable when a user requests it again.</p><p>Take the image below as a reference, without Caching (in this case Nginx), your app would keep more than required socket connections opened up for no reasons. The <em>blue lines</em> indicate HTTP requests, the <em>red lines</em> indicates socket connections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/1*E3aM68kCTuDNEkISoXrPdw.png" /></figure><p>Caching drastically reduces the number of calls that your app needs to make to your primary database. With their own ups and downs, there are three ways to implement caching in your app:</p><ul><li>Direct connect cache</li><li>An API caching layer</li><li>Local cache</li></ul><p>Or, you can have all of them serving different purposes within your app. For a MVP, that’ll be an overkill.</p><h3>Making a safe dating application</h3><h3>BuzzFeed News on Twitter</h3><p>A Dating App For HIV-Positive People Leaked Sensitive Data https://t.co/663YeMCrn8</p><p>Dating apps are often vulnerable. And, there are simple tactics by which an individual’s private information can be extracted to induce harm.</p><p>While building a MVP, the inability of a startup to spend hundreds of thousands of dollars is understandable. That being said, you should take care of the common <em>easy to fix exploits</em>.</p><p>A common well know exploit is <a href="https://en.wikipedia.org/wiki/Trilateration#Derivation">Trilalteration</a>.</p><p><strong>How Trilalteration works?</strong></p><p>Dating apps often share location information within the user’s app.</p><p>However, the user on gets to see ‘3 miles away’ or ‘5 miles away’ in his app’s UI:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*0XoHb-YDmtdo3H7Go9yyTQ.jpeg" /></figure><p>But, if you play a little bit with the backend, you would find user distances in the form of ‘3.01156’ or ‘5.223254’.</p><p>In order to get an accurate location of a user, all you need here is to just create three different profiles, with 3 arbitrary locations in these accounts.</p><p>You will then get 3 distances, let’s say ‘3.01156’, ‘3.10022’ and ‘3.00011’. Anyone can then proceed with Trilateration to get a good approximate location of the target user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/1*W2__BipA_SNJzp7Ikqi7hw.png" /></figure><p>While Tinder used to provide this information, they don’t anymore. But, we see many apps are still doing that, compromising user security. Most of the time, entrepreneurs behind such apps don’t even know that it is so easy to get the exact location.</p><p>Exposing user’s information in such way could be fatal for your app’s users. Grindr, a gay dating app also shared information the same way as Tinder. Egyptian authorities exploited this information to get exact location of gay people <em>and executed</em> them.</p><p>To avoid this, simply don’t provide accurate location information to your mobile UI.</p><p>Another way to hackers get access to user’s data is via <a href="https://en.wikipedia.org/wiki/Decompiler">Decompiling</a> your app.</p><h4><strong>Decompling a dating app</strong></h4><p>It’s extremely easy to <a href="https://www.simform.com/blog/how-to-avoid-reverse-engineering-of-your-android-app">decompile your app</a>. Once your code has been decompiled, attackers can:</p><ul><li>Source out any hard coded 3rd party backend’s ID’s and login credential.Which they can use to gain access to app’s server.</li><li>See debug messages if they are not turned off by the app developers.This allows attackers to access potential stream of sensitive information.</li></ul><p>To make attacker’s work a bit more difficult, you need to:</p><ul><li>Obfuscate the source code. It shouldn’t be in plain text.</li><li>Make sure no login credentials are not hard key coded within the source code.</li></ul><p><strong>Encryption and cryptographic hashes</strong></p><p>Each communication your app makes with the server should be encrypted. A <a href="https://en.wikipedia.org/wiki/Pretty_Good_Privacy">PGP</a> based cryptographic encryption will suffice here.</p><p>We don’t recommend cryptographic hashes, since it’s very easy to buy or download a list of hashes for all phone numbers.</p><p>The security measures listed here are extremely easy and cost effective to implement, making the best security tech for a dating app MVP.</p><h3>Real time chat Implementation</h3><p>When your users match, they’ll exchange messages before meeting each other.</p><p>Now, you should know that there’s a huge difference between <em>a simple chat</em> and <em>a real time chat</em> implementation. The former requires users to refresh the app to get new messages, while in the later, the chat gets updates automatically.</p><p>A simple(HTTP) based chat app would:</p><ul><li>Waste unnecessary resources</li><li>Provide poor performance and user experience</li><li>No assurance that messages will be delivered timely</li><li>Won’t scale properly, and ultimately fail</li></ul><p>Real time chat is present in each famous chat app that we’ve seen so far.</p><p>How to implement real time chat in your dating application?</p><p>Well, you can do that by:</p><ul><li>Socket programming</li><li>XMPP server integration</li><li>Using 3rd party SDKs like WeChat</li></ul><p>Each has it’s own merit and demerit. The last one is mainly used if there’s a budget constraint.</p><h4><strong>Socket programming?</strong></h4><p>Implementing a chat functionality from scratch isn’t the most preferred solution for startups. It just takes too much time and effort to build it.</p><p>There’s a reason why Layer charges <em>$1,500 per month</em>. A better way is to either go with <a href="https://firebase.google.com/">Firebase</a> or <a href="https://www.igniterealtime.org/projects/openfire/">OpenFire</a>. They both provide XMPP protocols for chat functionality. Both are good options and often deliver equal results.</p><p>However, there are a few differences:</p><ul><li>Firebase is paid; and will take care of high speed and scalability</li><li>Openfire on the other hand is free, but you will be responsible for speed and scalability</li></ul><p>If there are no budget constraints, you should go for Firebase, otherwise you can stick with Openfire.</p><p><strong>MYTH</strong>: Many claim that the maximum number of simultaneous users Openfire can handle is 4,000. Actually…</p><p>Unix like systems limits the number open requests Openfire can have. It usually is set as a default to 4,000. You can customize and increase it easily.</p><p>This setup can easily handle up to 50,000 users active at the same time. Some other benefits of using XMPP:</p><ul><li>More resistant towards censorship</li><li>Muti-device experience, synchronization of messages</li></ul><p><a href="https://layer.com/"><strong>Layer</strong></a> is another good option to build chat functionality within your app.</p><p>It utilizes pre-packaged building blocks for chat infrastructure as opposed to custom chat solutions. This drastically reduces the time required to build chat functionality:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ZSJ0ECzr1QwSxAAAIfQN3Q.png" /></figure><p>Layer is extremely expensive, and only a small percentage of startups could afford using it. They claim it to be one stop solution for <a href="https://layer.com/use-cases">chat in dating apps</a>, and provide everything from GIFs, stickers, music or any other rich media.</p><p>But often we’ve seen unique use cases where Layer falls short. Take for example, there’s no predefined “<em>Last seen</em>” feature in Layer, and requires a developer to customize the Layer implementation to implement it.</p><p>Another interesting part of a developing a Tinder like dating app is the matching algorithm.</p><h4>How does Tinder algorithm works?</h4><p>On a depressing note, nobody except a few knows what exactly goes behind Tinder’s algorithm. But, at the macro scale, it’s a combination of machine learning inspired by real world system dynamics to provide most contextual profiles to it’s users.</p><p>This has proven extremely effective when it comes to matching users accurately. But creating a proper Machine learning algorithm means overhead costs for startups. It often increases the total cost of ownership by 4–5 times.</p><p>So, what should a startup do?</p><p>Well, if you don’t have a Machine learning guy in your team, you can always observe your niche and find out how they interact and how relationships foster. Here are some general attributes that you should try to map:</p><ul><li><strong>Degrees of connection — </strong>How degrees of connection (1st, 2nd and 3rd) affect matchmaking success. Note that, there could be two different types when it comes to degrees of connection: 1. From your dating ecosystem 2. From Facebook.</li><li><strong>Influence</strong> <strong>of</strong> <strong>similarity/dissimilarity — </strong>Here you would mainly evaluate how to add weights to similar or dissimilar interests to make the match making process more effective.</li><li><strong>Profile completion — </strong>An incomplete dating profile tells a lot about a user. You can look at various fields inside the user’s dating profile to tune your algorithm.For example, you can add weight to the dating equation if the user has a Profile picture, has added work details, the number characters used to describe himself/herself, or whether he/she has added personal details or not, etc</li><li><strong>Are Push notifications enabled? — </strong>Social apps have a iOS push notification <a href="http://andrewchen.co/why-people-are-turning-off-push/">opt-in rate</a> of 30–45 %. This bias of time sensitive value propositions serves as an important parameter in the dating algorithm.A user that opts-in might intuitively understand that the push notifications will play an important role in the functionality of the dating app.Which could also be translated to high seriousness towards the dating ecosystem.</li><li><strong>Niche related parameters — </strong>These are parameters that are extremely specific to your niche. For example, if you are building a professional dating you may wish to add some weight to number of professional degree a person has obtained.</li></ul><p>By observation, testing and iterations you can easily come up with a mathematical formula that can provide upto 90% accuracy for your MVP.</p><h4>Tinder matching algorithm: The love equation</h4><p>The formula to rank a user on a scale of 100 could look something like this:</p><pre><strong>Points</strong>  = H1(<strong>min</strong>(1st degree, x1)/x1) + H2(Degree on <strong>Facebook</strong>) + H3 + H4(<strong>min</strong>(2nd degree, x4)/x4) + … + Hn(yn)</pre><pre>Hi is the coefficient of independent variables xi and yi.</pre><p>As the app matures and acquires more users the diversity and complexity of interactions makes it difficult to match users using an exact mathematical formula. When that happens, it’ll be the right time to migrate towards Machine learning to matching users.</p><h3>Improving user quality</h3><p>A lot of dating apps suffer from fake profiles, which often devalues the dating ecosystem and drive users away. The problem is so serious that there are many guides on the internet to <a href="http://www.lifehacker.com.au/2015/10/how-to-a-fake-profile-on-tinder/">detect fake dating profiles</a>.</p><p>At the very basic level, you could ask users to sign up on Facebook and get their identity verified from Facebook’s data. Now, how long do you think it will take for you to create a fake Facebook profile?</p><p>Probably a minute (even less!).</p><p>An easy fix: You can fetch user’s data from Facebook, <em>put a threshold</em> on the number of users, profile information, likes, etc that a valid user must have.</p><p>This threshold can easily reduce fake profiles from your Facebook. Another good way to improve user quality comes from content moderation.</p><h4>Content Moderation in Dating apps</h4><p>Dating apps are often flooded with all kinds of spam and inappropriate content that you might imagine.</p><p>On top of that, often instances of bullying and harassment surfaces in such apps. And, it shouldn’t be dealt with casually.</p><p>You can:</p><ul><li>Provide users with a way to report inappropriate content or harassment of any sort.</li><li>You can add a threshold, e.g. a threshold (number of times a content/profile has been reported) after which the content/profile gets deleted/suspendedOr</li><li>Do <strong>Both</strong></li></ul><p>Upon receiving the flags, an admin can manually moderate and take justified actions.</p><h4>Processing Payments</h4><p>Purchases made on dating apps generally fall under the category of digital goods. Hence, the use of any Payment Gateway is prohibited.</p><p>To process in-app purchases within your app, you need to integrate Apple and Google’s wallet within your app.</p><p><strong>Why to build a dating app this way?</strong></p><p>Dating apps rarely do sufficient upfront monetization for the developers to survive in the early days. And the moment number of users start to increase, it increases the need for a reliable app infrastructure as well as the operational costs to run it.</p><p>And, there comes a time when it no longer is feasible, and startups often have to look for fundings. Your future investors won’t entertain apps built on top of app builders and clone scripts, they might take it as a not-so-serious venture.</p><p>After all, if you believe that they should invest in your startup, why wouldn’t you invest in it? Right.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55d5ca0c8f5c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/how-to-build-a-dating-application-55d5ca0c8f5c">How to build a dating application?</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>