<?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 Ankit Pandole on Medium]]></title>
        <description><![CDATA[Stories by Ankit Pandole on Medium]]></description>
        <link>https://medium.com/@ankitpandole93?source=rss-b909f9d85b78------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hgLCHjcvMzrHO_4ahHu12A.png</url>
            <title>Stories by Ankit Pandole on Medium</title>
            <link>https://medium.com/@ankitpandole93?source=rss-b909f9d85b78------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:37:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ankitpandole93/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[Not Every Feature Has to Scale]]></title>
            <link>https://tales.pratilipi.com/not-every-feature-has-to-scale-78fa6efc9fae?source=rss-b909f9d85b78------2</link>
            <guid isPermaLink="false">https://medium.com/p/78fa6efc9fae</guid>
            <dc:creator><![CDATA[Ankit Pandole]]></dc:creator>
            <pubDate>Fri, 27 Jun 2025 12:16:36 GMT</pubDate>
            <atom:updated>2025-09-16T07:19:21.315Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>A quiet example of inclusive product thinking at Pratilipi</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_7pum3u-exyBw4C1" /></figure><p>In product and design, the features we usually tend to celebrate are the ones that move metrics — drive revenue, increase retention, or unlock growth loops. But once in a while, we build something that doesn’t do any of those things. And still, it sticks with us.</p><p><strong>“Ask Someone Else to Pay”</strong> is one of those features. It was quietly launched in November 2022, with no big announcements or dashboards watching it. It’s not something we highlight in performance reviews or roadmaps.</p><p>But for a few of us on the team(me personally), it’s still one of our favourites — because it was born from empathy.</p><h3>Where It Started</h3><p>This idea emerged from a mix of user support queries and real-life anecdotes — stories that surfaced not just from those who <em>paid</em>, but from those who <em>wanted</em> to pay and couldn’t.</p><p>We heard things like:</p><blockquote><em>“I bought the subscription for my mom.”<br> “My parents don’t have a UPI ID or bank account — I have to help them every time.”</em></blockquote><p>But what struck us most came from a user study where we asked someone why she hadn’t renewed her subscription. Her answer was simple, and quietly devastating:</p><blockquote>“I don’t know how to pay. My daughter usually does it. She’s in the hostel right now, so I’m waiting until she comes home.”</blockquote><p>That wasn’t just a technical issue — it was a pause in access, a story left unread, not because of affordability, but because of digital dependency.</p><p>And it wasn’t rare. Several of us on the team had experienced similar situations with family. I’ve lived this myself. My mom is an avid Pratilipi user, and I’ve helped her pay for subscriptions. That moment — where someone wants to pay, but can’t — stuck with us. It wasn’t about technology. It was about access. These weren’t edge cases. They were real. And we knew they deserved a better solution.</p><h3>What We Built</h3><p>The idea was simple: if a user can’t pay themselves, let them ask someone else to pay on their behalf.</p><p>We called it (because we’re terrible at naming) — <em>Ask Someone Else to Pay</em>. Not a fancy product name. Just what it was.</p><p>The first version sat right next to our main Premium Subscribe CTA, with a small link: “Ask a Friend to Pay,” accompanied by a WhatsApp icon. Tapping it opened a bottom sheet explaining the 3 steps:</p><ol><li>Share a payment link via WhatsApp (or copy it).</li><li>Friend/family receives it and pays.</li><li>The user gets access instantly.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*ppVb3aun44dcyVWkPi9Yfg.png" /></figure><p>Simple. Direct. Frictionless. Especially for Indian users, where WhatsApp is often the most widely used channel of communication.</p><p>Later, as we launched our <strong>Custom Checkout Page</strong> (with all major payment methods), this feature was moved there, as one more way to pay. That small shift in placement made a big difference. It aligned with the user’s natural decision flow: <em>“How do I want to pay?”</em> instead of <em>“Can I even pay?”</em></p><h3>The Human Problem It Solves</h3><p>This feature was — and still is — about <strong>access</strong>. We often forget that not every user is fluent in digital payments. Some don’t have UPI. Some don’t have a bank account. Some just don’t trust the system.</p><p>Pratilipi was built to make stories accessible in any language, any format — and this feature extended that vision to payment. It said: even if you can’t pay yourself, we’ll help you find a way.</p><p>It also solved a practical gap. Previously, someone trying to help their parent would have to take their phone, click ‘Buy’ on that device, and then complete the payment on another device. It was fine if they were nearby. But what if they weren’t? This feature solved that silent friction.</p><h3>The Results? Quiet.</h3><p>Today, the feature’s impact on revenue is tiny. Usage-wise, it’s minuscule.</p><p>But that was expected. As digital literacy and UPI adoption improve in India, fewer people need it. And that’s okay. That’s actually a good thing.</p><p>Still, the feature has continued to see steady(if modest) growth in usage over time.</p><h3>Why I Still Love It</h3><p>Most days, we build to optimize. Push a metric. Increase a number. Win a graph.</p><p>But this feature? It had no burden of performance. It existed simply to help the users.</p><p>To me, that’s what great product design is about: making sure no one gets left behind.</p><p>I believe this was a <strong>novel idea</strong>, maybe even the first of its kind in Indian subscription platforms. (Fun fact: Google later added something similar to Play Store payments.)</p><p>That’s why I love it. Not only because it scaled, but because it served.</p><p>Team mentions — Himashree Kalita, Ranit Das, Tanvi Goyal, Sai Prasad.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78fa6efc9fae" width="1" height="1" alt=""><hr><p><a href="https://tales.pratilipi.com/not-every-feature-has-to-scale-78fa6efc9fae">Not Every Feature Has to Scale</a> was originally published in <a href="https://tales.pratilipi.com/">Team Pratilipi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pratilipi Monetization Journey]]></title>
            <link>https://tales.pratilipi.com/pratilipi-monetization-journey-c408a57778c4?source=rss-b909f9d85b78------2</link>
            <guid isPermaLink="false">https://medium.com/p/c408a57778c4</guid>
            <category><![CDATA[strategy-execution]]></category>
            <category><![CDATA[monetisation]]></category>
            <category><![CDATA[creator-economy]]></category>
            <category><![CDATA[monetization]]></category>
            <category><![CDATA[subscription-economy]]></category>
            <dc:creator><![CDATA[Ankit Pandole]]></dc:creator>
            <pubDate>Wed, 07 Feb 2024 10:03:23 GMT</pubDate>
            <atom:updated>2025-09-16T07:18:56.510Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Pratilipi as a company has different verticles. Here I will be talking in the context of </em><a href="https://play.google.com/store/apps/details?id=com.pratilipi.mobile.android&amp;referrer=utm_source%3Dpratilipi_main_web%26utm_medium%3Dweb_app_badge%26utm_campaign%3Dapp_download"><em>Pratilipi Literature.</em></a></p><blockquote>Background :</blockquote><blockquote>Pratilipi Literature is a UGC(user-generated content) storytelling platform. It currently operates in 12 Indian languages, each language being a community of readers and writers. Readers of Pratilipi consume long-form multi-episodic series, published by the writers on the platform, in the language of their choice. Readers can rate and review the stories and follow writers to get the latest updates on their newest episodes.</blockquote><blockquote>Interestingly, the majority of our writers are not professional authors. They typically start as users, enjoying the stories written by others. As their interest and creativity grow, they transition into becoming writers or creators themselves. This transition highlights the democratization of storytelling, where users evolve from consumers to contributors, shaping a community where everyone has the opportunity to share their stories and perspectives.</blockquote><blockquote>To know more about how we grew our supply side, I highly recommend reading Shally Modi’s (Co-Founder) blog series — <a href="https://medium.com/@sahradayimodi/supply-as-a-business-moat-part-1-605ab78b1e88">Supply as a Moat</a>.</blockquote><h3>Bringing Behavioural Change in Users</h3><p>Since its inception, Pratilipi users have been accustomed to reading stories freely on the platform. When we initiated revenue experiments in 2020, the big question was: how to instigate a shift in behavior among Pratilipi users, encouraging them to engage in any form of monetary transaction on the platform. The main consideration was identifying features that would not only provide added value to users but also enable us to capture value in return.</p><p>Pratilipi’s engagement numbers are among the best in the industry(~60% of subscribers use the app every single day with avg. 3.5 hours per day reading time for subscribers). We also saw the behavior where readers put in time and effort to interact with authors, be it by writing and discussing their newest published story in the review section, trying to DM them, or meeting them in person to felicitate them. All these reader-writer interactions gave us insights that led us to build our first monetization experiment — <strong>Virtual Gifting.</strong></p><h3>Virtual Gifting (Stickers)</h3><p>Virtual Gifting is a feature where readers can send virtual gifts in the form of stickers to the authors. These stickers can be bought by the readers through Pratilipi Coins, our virtual currency. When the authors accumulate enough stickers, they can cash them out for actual money.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v-jq8uR-L2ijf-akwr8QmQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q1aRcL60IWXMwtelvxsXRA.png" /></figure><p>We introduced Pratilipi Coins as part of gamifying the whole experience. Readers could purchase stickers from coins, but they could earn bonus coins by taking part in the Reading Streak Challenge or Referring a friend to Pratilipi. Readers were also given 10 free coins to begin with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hSIXdkgl0zDdmJ3fEKZHPg.png" /></figure><p>The bonus coins gave readers a taste of the fun. It gave them gratification and encouraged them to consider purchasing more coins to continue enjoying the experience. Within one week of launching Virtual Gifting, we saw great momentum within the community. The response was much better than what we had expected. Some of the snippets post the launch:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n5wbu6WP8zELIejjACTc9w.png" /></figure><p>Now that we had established a buying mechanism on the platform, we wanted to double down on the momentum. As virtual gifting increased on the platform, we saw another interesting phenomenon- Some writers were given a lot more stickers than others. These writers also had a very high engagement in their reviews/chat messages. This gave us another idea for a feature that can leverage reader love towards writers. Thus came our second feature in monetization: <strong>Superfan Subscription</strong></p><h3>Superfan Subscription</h3><p>Superfan subscription is a feature where readers can become superfans of certain eligible writers by paying a monthly subscription fee. In return, the readers will get :</p><ul><li>Early access to newer episodes of their subscribed writer’s ongoing stories.</li><li>Exclusive access to writer-specific Superfan Chatrooms.</li><li>A superfan badge to flaunt within the community.</li><li>Visibility on writer&#39;s profiles as their superfans.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aR6gw_UVUFBf0jPZic0e-A.png" /></figure><p>On the supply side, writers could start earning directly from superfan subscriptions. They also had a superfan eligible writer badge on their DP which made them stand out from other writers on the platform.</p><ul><li>With non-superfans, writers could now write more series on a timely basis to increase and engage their followers(via post section or live streaming or review section) so that at a later point they can convert into subscribers.</li><li>With Superfans, writers can now gauge the early reactions to their newer episodes and can engage with their superfan chatrooms to discuss story plots, fan theories, Q&amp;As, etc.</li></ul><p>We launched Superfan Subscription with a monthly subscription fee of ₹25. Over time we added 6 monthly and yearly plans to the subscription. This fee empowered the writers to earn, while Pratilipi captured value through a percentage cut.</p><p>Since it was a subscription feature, we were a bit skeptical about user perception of the feature but it exceeded our expectation when we saw the response. Within months, we saw good user engagement towards the features. Some snippets to bring the point out:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qpy3irGH-Q8kOpGkyQ8rwA.png" /></figure><p>Once the subscription feature reached a steady state, we again went to our drawing board. We realized that a lot of readers were becoming superfans of multiple writers at once. That meant they were paying for multiple subscriptions to extract the same value from multiple writers. Also, selecting a subscription plan and repeating the process for multiple subscriptions demanded a simpler experience.</p><p>The signs naturally pointed towards evolving into a platform-level service. As our next experiment in monetization, we introduced <strong>Pratilipi Premium </strong>— a tiered subscription for the entire platform.</p><h3>Pratilipi Premium</h3><p>Pratilipi Premium is a platform-level subscription program for the readers to unlock any content at any time. It caters to power users by enriching their reading experience.</p><p>Pratilipi Premium subscription included benefits like</p><ul><li>Early access to newer episodes of all the superfan writer’s ongoing stories.</li><li>Unlimited access to Premium exclusive series, a lock-free experience.</li><li>Priority support to all your queries.</li><li>Access to future premium-only features to enhance the reading experience.</li></ul><p>Although premium subscribers will get the superfan benefit of early access episodes, they will not get the superfan badge and access to some superfan-only features. We kept it this way because we wanted to keep the path open for readers to keep supporting their favorite writers by becoming their superfans.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ki3An9Naay0aZtrKlZxyjA.png" /></figure><p>Premium Subscription starts with a monthly subscription of ₹150, along with 6 monthly and yearly subscription plans. The highest plan is the yearly plan at ₹1500 per year.</p><p>We pondered a lot to figure out this pricing system. Many said that the price point of ₹150/month is too high and Indians especially our user base won’t be paying that much for a digital subscription. However, we wanted to challenge this stereotype and we were reluctant to devalue our product. We firmly believe that users recognized the value in our stories, evident through the insane engagement on our platform. Therefore, we stuck to this price point.</p><p>The risks reaped rewards. We saw an amazing response from our users, and in a short time, Pratilipi Premium became the highest revenue-driving lever for Pratilipi, so much so that today, 21% of our D.A.U.(Daily Active Users) on Android is a paid subscriber. The number goes even higher for iOS at 33% of DAU.</p><p>These numbers are also aided by the fact that despite having all these subscription products, users can still read everything for free if they want through <strong>Wait and Unlock</strong> — One episode unlocks every day for free for everyone who has read the story till that point, and the next episode tomorrow and so on. This mechanism has resulted in some of the most novel and interesting outcomes:</p><ul><li>A very high % of active premium subscribers (discussed above) as users convert over time.</li><li>Negative churn(<a href="https://medium.com/@sahradayimodi/the-beauty-of-negative-churn-e47340f9114e">read more about it here</a>).</li><li>Very high engagement even for <strong>free users</strong> with an average non-subscriber spending over 90 minutes per day on the platform.</li></ul><p>All these monetization levers exist in the app today as well. They work beautifully with each other giving us some interesting user funnels:</p><ul><li>Virtual Gifting becomes a low-cost entry point for users to start supporting their authors and making them habitual to the coin ecosystem.</li><li>Superfan becomes an entry to the subscription funnel which culminates into a Premium subscription.</li><li>Wait and Unlock becomes an important funnel to convert free users to paid users. We do multiple different experiments to boost this funnel.</li><li>Premium subscribers get used to the lock-free experience while reading completed and ongoing stories during their subscription period, which drives them to continue their subscription for the subsequent month as well. It reflects in the engagement numbers for the paid users as well. The time spent per day for a subscriber reaches &gt;2.5 hr on average on the platform.</li><li>Because of the engagement numbers, the resubscription rate for M1 sits at a decent 48%. This is again a lever where we do experimentation to keep improving the resub rate(<a href="https://x.com/ThEbmr/status/1753683456012517468?s=20">read more</a>).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X8lcMknm3anmhSO128oR9A.png" /></figure><p>Our journey through shaping user behavior in monetization has been full of learning at each step. This is one of the first in a series of blogs about bringing behavioral changes in users. Feel free to let me know if there’s anything specific you’d like more information on or if any questions you have. You can reach me on <a href="https://twitter.com/ankitpandole">Twitter</a> or <a href="https://www.linkedin.com/in/ankit-pandole-05658152/">LinkedIn</a></p><p>Next, I will be writing about how we revamped the writing behavior at Pratilipi. Till then, Adios 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c408a57778c4" width="1" height="1" alt=""><hr><p><a href="https://tales.pratilipi.com/pratilipi-monetization-journey-c408a57778c4">Pratilipi Monetization Journey</a> was originally published in <a href="https://tales.pratilipi.com/">Team Pratilipi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WhatsApp Remind Feature — a UX case study]]></title>
            <link>https://uxdesign.cc/whatsapp-remind-feature-a-fun-project-476cfd9cd213?source=rss-b909f9d85b78------2</link>
            <guid isPermaLink="false">https://medium.com/p/476cfd9cd213</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[mobile-app-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[whatsapp]]></category>
            <dc:creator><![CDATA[Ankit Pandole]]></dc:creator>
            <pubDate>Thu, 16 Aug 2018 11:35:20 GMT</pubDate>
            <atom:updated>2021-02-23T08:04:44.223Z</atom:updated>
            <content:encoded><![CDATA[<p>I want you to have a look at these conversations:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*CiWGGqOwgTKsyFvNZpzkKw.png" /><figcaption>Have you had similar conversations on WhatsApp?</figcaption></figure><p>What’s the common trend in these conversations?</p><p>In each scenario, the recipient is given the task to remember events and in some case remind the sender back in a certain period of time. Personally, I keep forgetting such things said to me on WhatsApp(and I imagine, many people do).</p><p>This led me to think of adding a new feature called <strong>“Remind”</strong> in WhatsApp. A feature which can allow us to convert any message into an event reminder in the app itself. This would allow users to make a reminder of any message in the chat.</p><p>But before jumping in the design, let us have a look at WhatsApp’s design philosophy and how they go about adding features in the app.</p><p><strong>Background 😬</strong></p><p>WhatsApp is the most popular messaging app on the planet right now. People have their own reasons to love WhatsApp, but as a designer, I was most fascinated by their design philosophy.</p><p>You might wonder, what’s so great in the design. It’s not flashy, and boring most of the time. But that’s where the success lies for the design. The app is so intuitive that it feels boring. The design is easy to use, simple enough that WhatsApp doesn’t have to educate users about any new feature that they introduce. In the blog posted by <a href="https://medium.com/u/269bb90f584d">Charlie Deets</a>(product designer at WhatsApp at the time), he specifically mentioned WhatsApp’s design philosophy:</p><blockquote>“If a feature needs explanation, it’s not ready.” 👏</blockquote><p>This line got me excited about WhatsApp’s design. And since I was working on a <strong>Remind</strong> feature in WhatsApp, I thought, let me design it the way the WhatsApp design team would do. So, I researched about their philosophy, the things they put attention to it, the subtle design choices they make and the design principles they religiously follow, and used my design senses to build a comprehensive flow for the <strong>Remind</strong> feature.</p><h3><strong>Problem Statement</strong></h3><p>Design a new Remind feature in WhatsApp and integrate it with the current design of WhatsApp… all this while having some fun 😜.</p><h3><strong>Design Principles</strong></h3><p>I have followed the design principles that are used in the WhatsApp design team(read more in the <a href="https://medium.com/facebook-design/one-year-designing-at-whatsapp-c20b4c46bae6">blog</a> by <a href="https://medium.com/u/269bb90f584d">Charlie Deets</a>):</p><ul><li>The interface should feel native to the device(in our case, Android)</li><li>Simple Interface with quick animations and user actions</li><li>Any new feature addition should provide obvious utility that it requires very little introduction.</li></ul><h3><strong>Feature Design</strong></h3><p>Let’s take a look at this conversation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/288/1*i2msu3dOgDamRH0_XIYtTQ.png" /></figure><p>In this, Tony is asking our user to bring the stormbreaker to the falafal place. We want our user to make this message into a reminder so that he gets reminded on a specific time before the party to take the stormbreaker with him.</p><p>For the remaining part of the case study, we would take this conversation as our basis.</p><h3><strong>The flow</strong></h3><p>The flow starts with selecting the message:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*cxoPPjs9FBSTBZsPgK1Xyg.png" /></figure><p>The Remind icon appears on the top bar:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*VKzFpddZkOOtjyIahQkVTg.png" /></figure><p><strong>Brief Backstory 😒</strong></p><p>Before reaching to this final design, I researched about the different ways people interact with a message:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zGSKv_IdbFhgczGLMRKQTg.png" /><figcaption>Ways in which a user interacts with a message</figcaption></figure><p>The interactions were either long press to react on messages or auto detect the dates and make it clickable. All of them were good options but none of them felt native to the WhatsApp experience. They had their limitations as auto detection can detect date and time(number based) in messages, but doesn’t give the users the freedom to convert any message in a reminder. And since, WhatsApp is an encrypted platform, data interpretation and keyword searching is also not feasible.</p><p>Therefore I decided to keep the interface same and add a new icon in the top bar, pushing the less used feature(starred message) inside the vertical ellipsis, thus keeping up with the design principles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*_ZA5PRruq80DBTmyEBH5Fw.png" /><figcaption>Mark as Important(starred messages) gets pushed inside the vertical ellipsis</figcaption></figure><p>Back to the flow 😅…</p><p>Upon selecting the Remind icon, a new event screen opens up. It has 3 sections, the Reminder text(copied from the selected message), Event time and Date &amp; Repeat Event options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*n-yU61yQDao-PfOIsKJ9JQ.png" /><figcaption>Upon selecting the Remind Icon, the New Event screen opens up</figcaption></figure><p>Once the Event text is copied from the message, the user can either modify it to a reminder like message, or keep the same text as the reminder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hNRKlGAL9y9REbfRxbRrhQ.png" /><figcaption>The original message modified to a more reminder like message.</figcaption></figure><p>Now, changing the date and time</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DIVdcPLUbmBJxBjlOzpJEA.png" /></figure><p>Now, upon saving, the alert becomes a reminder and gets saved. But if you are introducing a reminder list, you need a screen to showcase it all.</p><p>This is how the current home-screen looks like 😐:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*5lkcIfUN8BVkQvVGxF6ujA.png" /><figcaption>Current Homescreen</figcaption></figure><p>And this is how it will look after the introduction of a reminder list 😎:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*ddwZNk_djAgWaHHcCKSOvg.png" /><figcaption>Homescreen with the addition of a new “Event” list</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*6L2y_7wYoxPGJSAIq1Ga6Q.png" /><figcaption>“Event” feature with the list of reminders</figcaption></figure><p>And Voila, the WhatsApp reminder is here 😌:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*pyvFtdDH4bBZr8rM-kQwTw.gif" /></figure><p>NOTE 😶</p><p>This was a hypothetical fun project. So the feature introduction might not align with the business requirements and the product directions of WhatsApp as a company. But if ever WhatsApp wants to release this sort of feature(why would they?), they can take some cue from here 😉.</p><p>Spell Correction- Falafel, not F̵a̵l̵a̵f̵a̵l̵ 😓.</p><h4>References</h4><ul><li><a href="https://medium.com/facebook-design/one-year-designing-at-whatsapp-c20b4c46bae6">One Year Designing at WhatsApp- Charlie Deets</a></li><li><a href="https://medium.muz.li/why-whatsapps-design-makes-it-the-best-instant-messenger-aa706bf7a41d">Why Whatsapp’s design makes it the best instant messenger- Chris Lee</a></li><li>Image Credits: Google Images</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=476cfd9cd213" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/whatsapp-remind-feature-a-fun-project-476cfd9cd213">WhatsApp Remind Feature — a UX case study</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shuffl- Play your own music at a party]]></title>
            <link>https://uxdesign.cc/shuffl-play-your-own-music-at-a-party-f256997b510b?source=rss-b909f9d85b78------2</link>
            <guid isPermaLink="false">https://medium.com/p/f256997b510b</guid>
            <category><![CDATA[music-player]]></category>
            <category><![CDATA[wireframing]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ankit Pandole]]></dc:creator>
            <pubDate>Thu, 01 Feb 2018 20:48:39 GMT</pubDate>
            <atom:updated>2018-05-31T15:49:36.662Z</atom:updated>
            <content:encoded><![CDATA[<p>Problem Statement- To make a mobile app which allow guests at a party to play their own songs. The app should solve the problem by enabling the users to queue their favourite songs and play them in sequence.</p><p>There will be 2 user profiles:</p><ul><li>A Host</li><li>Guests</li></ul><p>The flow of the app is made for these 2 user profiles.</p><p>A host throwing a party will create the main party group. He will have the right to play, pause or skip. He can even remove the guests from the group and can give the host rights to others. This was done so that there will be minimum hassle for play/pause or skipping any song. A central authority(or 2) would be better to take care of these things and let other people enjoy the party.</p><p>The Guests will choose the active party group in the app, enter the party code and will directly go to the music homescreen. On that, they can see the current track playing and the next songs in queue. They can start adding their songs on that screen itself.</p><p>There are more details and screens which are detailed below:</p><h3>App Flow Chart</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kxnwWtT52Dby7RAU29R9Xg.png" /><figcaption>App user flow for the host and guest user profiles</figcaption></figure><h3>Wireframes for the app</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ZJNll_VSthA4MTIzWXpVg.png" /><figcaption>Wireframe design flow for Host</figcaption></figure><p>I will be breaking down the wireframe and explain the flow section wise.</p><h3>For Host</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lX29y9UPTgFQp0tSd7fvtw.png" /><figcaption>The flow for host to start a party group.</figcaption></figure><p>Upon opening the app, the user is given the choice to either Join a Party(Guests) or Create New(Host). When Create New is chosen, the host enters his credentials, set a party code(for guests to select the correct party group).</p><p>The host can then choose to pick the streaming service from where he wants the songs to play from. Right now, for this app, I have included the 3 most popular streaming services but there can be more. Then based on the genres selected by the user in the next screen, the app will populate the song list. This would serve the purpose of playing music till more and more guests starts arriving and start adding their own choice of songs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/411/1*Aup5A8pa5zM_uI_M9kM1fQ.png" /><figcaption>The Host can remove some songs from the initial curated list by right swiping the song and choosing ‘Remove’.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-uerKCu7pq-md6scCLeemg.png" /><figcaption>Options to Start the playlist or play at a later stage</figcaption></figure><p>On this screen , the host is given 2 choices, either to start with the party or he/she can save it for later. This was done keeping in mind that the host might not want to keep the guests waiting and so, will have a playlist ready beforehand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/1*7g48ythgDXlTR5YPDK7HjQ.png" /><figcaption>Music Screen</figcaption></figure><p>When ‘Start the Party’ option is selected, the music opens up with the curated playlist and the current track being played. The option to play, pause or skip will only be shown to the hosts.</p><p>In addition to the playlist, the music screen has 2 main elements:</p><p><strong>‘Add new track’ button-</strong> Allows user to start adding songs of their choice.</p><p><strong>‘Guest List’ floating button-</strong> Shows the list of people connected to the app in the party.</p><h3><strong>Adding a track</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FLGdhxDSt8rpsinLokVxlw.png" /><figcaption>Adding track using the ‘Add new track’ button</figcaption></figure><p>The ‘Add new track’ buttons opens a search screen where user can type their choice of song and based on the result, can queue multiple songs in the playlist. The songs will be streamed from the streaming service the host has chosen in the beginning.</p><h3>Guest List</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RLWskG1FHtYo6uwD3oiwGA.png" /><figcaption>The floating button opens up the Guest connected to the app.</figcaption></figure><p>The star denotes the host rights(play,pause or skip). Only the main host can give the other guests the host rights or can remove the people from the app, both by left and right swiping on the list. The floating button also shows notification whenever any new person connects to the app.</p><h3><strong>Promote your choice of music</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/411/1*l1S3B56tUbG37SOAUiUSpw.png" /><figcaption>The heart rating system</figcaption></figure><p>The app also has a rating system for the songs in the playlist, denoted by the heart symbol. This was introduced for scenarios where people might find their choice of music already in the list and they can promote it so that it pushes up in the list. If more and more people promotes it, the heart symbol fills and the song keeps pushing up the queue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JChYn-fsRRhSg1X0DqFt1A.png" /><figcaption>Left and right swipe actions to promote or push down any track.</figcaption></figure><h3>For Guests</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SBlY4PYqRHUxslivm17twg.png" /></figure><p>Breakdown of the wireframe flow for guests</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PLyLFA6sUzHMe5HaFjKZAA.png" /><figcaption>The flow for guests to join a party group.</figcaption></figure><p>The guests can join a party from the ‘Join a Party’ button. They have to select the party and fill in their credentials. If the photo isn’t provided, the image will be the abbreviation of the name provided.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XVrMzveHoPrW3onhnTpS4A.png" /><figcaption>Music screen remains same for host and guests.</figcaption></figure><p>The music screen remains same for host and guests, except the guests won’t see any audio controls. They will just be shown the progress bar of the track.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OLou5ixASl_hIKwlwEB3Bw.png" /><figcaption>Adding new track and floating button flow for guests</figcaption></figure><p>This is the complete wireframe flow for the mobile app. In the next part, I came up with the visual design for the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FJ1vrZIH-Hr1DIHXWubHJA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WXcx1VV4hK8a9rk4jSO_KA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qy9uGoyfNDBHLCOSGMh27w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YoAHzVK3UqYZ3UpSVNorGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fkJ0yHC8ff6u--0yfwxshQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xgIFkE13xcxBOhXn5njXyQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-FWcqZJ60mauTsK-g0jUyw.png" /></figure><p>Looking forward to your comments and suggestions.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f256997b510b" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/shuffl-play-your-own-music-at-a-party-f256997b510b">Shuffl- Play your own music at a party</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>