<?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 Toshika Badjatya on Medium]]></title>
        <description><![CDATA[Stories by Toshika Badjatya on Medium]]></description>
        <link>https://medium.com/@badjatyatoshika91311?source=rss-9c008139d933------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nqa_6W7aIgYnVlDEZAoMZA.jpeg</url>
            <title>Stories by Toshika Badjatya on Medium</title>
            <link>https://medium.com/@badjatyatoshika91311?source=rss-9c008139d933------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:06:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@badjatyatoshika91311/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[Spotify — Product Analytics Breakdown]]></title>
            <link>https://medium.com/@badjatyatoshika91311/spotify-product-analytics-breakdown-setup-0842516b469b?source=rss-9c008139d933------2</link>
            <guid isPermaLink="false">https://medium.com/p/0842516b469b</guid>
            <category><![CDATA[experimentation]]></category>
            <category><![CDATA[ab-testing]]></category>
            <category><![CDATA[funnel-analysis]]></category>
            <category><![CDATA[cohort-analysis]]></category>
            <dc:creator><![CDATA[Toshika Badjatya]]></dc:creator>
            <pubDate>Tue, 14 Jul 2026 18:03:14 GMT</pubDate>
            <atom:updated>2026-07-14T18:05:07.604Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sYD5v5lrD4ZFSNO-y55nsg.png" /></figure><h3>Product Context</h3><p>Spotify is an audio streaming platform supporting 100 million tracks, 7 million podcasts, and 700,000 audiobooks. <br><strong>Business Model: — Freemium (Paid for ad-free)<br>Key Metrics: ARR:</strong> $19.5 billion USD ($16.4 billion USD from premium); <strong>MAU:</strong> 760 billion users<br><strong>Key Competitors: </strong>— Apple Music, YouTube Music, Savana, etc. <strong>Market Share: </strong>— 31%</p><h3>Business Problem Statement</h3><p>Increase premium subscription conversion by improving early-user retention and engagement.</p><h3>Altitude Maps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v3fn1ubMYfd10N57IYUtTw.png" /></figure><h3>North Star Metrics: Weekly Engaged Users</h3><p><strong>Definition:</strong> No. of users</p><p>listen on ≥3 days/week</p><p>spend ≥30 mins/week</p><p>complete ≥1 intentional action</p><h3>Product Area Scorecard</h3><p><strong>Activation:</strong> Time to Value (10+ mins listening)</p><p><strong>Retention:</strong> WAU (North Star)</p><p><strong>Engagement:-</strong> Average Listening Time, playlist shared, playlist revisit frequency</p><p><strong>Value:</strong> Premium features like ad-free, offline download, shuffle, AI-DJ</p><p><strong>Conversions:</strong> offline/shuffle/mix playlist attempts and music download failure attempts. (Upgrade intent)</p><p><strong>Business:</strong> ARPU (via premium subscription)</p><p><strong>Guardrail Metrics: </strong>— Free tier engagement (due to conversion levers)</p><p><strong>Experimental Metrics: </strong>— Ad frequency and exposure (Low: **** no friction, conversion intent, High:- Session drop &amp; Optimal:- Upgrade intent</p><p><strong>Vanity Metrics: </strong>— Ad skip attempts (user friction not guaranteed to lead to conversion attempt), Time spent on app (not a sign of effective engagement), No. of playlists created (playlist created but abandoned)</p><h3>Instrumentation</h3><p><a href="https://docs.google.com/spreadsheets/d/1M8FoagSmZ23rHMaSAvjBm3QjnjEPHVf1z7Ug_662n0s/edit?gid=1846030172#gid=1846030172">https://docs.google.com/spreadsheets/d/1M8FoagSmZ23rHMaSAvjBm3QjnjEPHVf1z7Ug_662n0s/edit?gid=1846030172#gid=1846030172</a></p><h3>Segmentation</h3><ol><li><strong>Outliers (not considered for the analysis):</strong> Passive users; churned users; podcast listeners (high listening time; offline listening on free; minimal ads); and price-sensitive users (structural non-converters, indicated by demographics [geography, device usage, usage patterns, and high tolerance to friction]).</li><li><strong>Repetitive Listeners:</strong> Track repeaters, album or artist loyalists; avoid the cognitive load of choosing.</li><li><strong>Background Listeners: </strong>— Passive music consumption while doing activities like driving, going to the gym, etc., has a minimal engagement window; it has a higher average listening time but lower engagement.</li><li><strong>Musically Engaged Users:-</strong> Experiment heavily with music consumption, driven by trends, friends’ playlists, searching for music, and following artists.</li><li><strong>Socially Engaged Audience: </strong>— Create and share playlists; prefer a community-driven music experience</li><li><strong>Friction Intolerants:-</strong> People irritated by friction, aggressive tapping of buttons, checking of premium features, and high consumption but with less patience.</li></ol><h3>Funnels Design</h3><ol><li><strong>Engagement Funnel</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*Y0diCeVtY8z8uj7bl6gkgQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*aCMGhEsSXrlAtrZuWulB7g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*IDkBlzPDNunkr3yUkC1SRQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*bm39rgOCvcaPUdxUDlL8oA.png" /></figure><h3>Retention Analysis</h3><p><strong>Duration:</strong> 21 Weeks <br><strong>Metrics:</strong> Weekly listening retention, Weekly action retention<br><strong>Examples:-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tXOeFEXLDrQU7JyyIUrYqg.png" /></figure><h3>Cohort Analysis</h3><p>Behaviour analytics for retention for users from the same date (1 June)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qURfY1Zb8xxD1hLuH4-ufA.png" /></figure><h3>Observations</h3><ol><li>Poor discovery + friction cause maximum churn due to dissatisfaction.</li><li>Payment intent is highest among people who visited the Gateway 2× in these initial sessions. The next 2 weeks can be a high-intent period when a nudge or time-bound offer can be the right lever.</li></ol><h3>A/B Test</h3><ol><li><strong>Hypothesis:</strong> If a user skips 2 songs within the first 15 seconds, skip the upcoming ad to reduce friction. <br><strong>Constraint:</strong> Fewer than 3 intentional actions in the previous week [to exclude users who are finding the right match and are not agitated]. <br><strong>Test setup:</strong> 10% of the user base [avoid early adopters &lt;1 month on the platform]. <br><strong>Quality:</strong> Select random users across different parameters (e.g., age, gender, device type, music genres, listening patterns [background, late-night, etc.]). <br><strong>Time Setup:</strong> 2 weeks.<br><strong>Metrics:</strong> Session drop-off rates. <br><strong>Guardrails:</strong> Drop in ad revenue &gt; 5%. <strong>Decision tree:</strong></li></ol><ul><li>Metrics improved → <em>Ship it.</em></li><li>Guardrails affected &amp; metrics unaffected → <em>Abort and iterate.</em></li><li>Guardrails &amp; metrics unaffected → Retest with a different user segment.</li><li><strong>Review &amp; tradeoffs:</strong> Random spikes in skip rates could deliberately trigger ad suppression.</li></ul><p>2.<strong> Hypothesis:</strong> If a user visits the payment page twice (spending nearly 10 seconds), show a banner like, “You are a lucky user,” with either [one remix playlist option / 3 days ad-free] or [3 days offline (primarily for background users)]. <br><strong>Constraint:</strong> Include users with ≥5 sessions/week for ≥6 of the past 8 weeks. <br><strong>Time Setup:</strong> 1 month.<br><strong>Test setup:</strong> 20% of users satisfy the constraints. <br><strong>Quality:</strong> Select random users across different parameters (e.g., age, gender, device type, music genres, listening patterns [background, late-night, etc.]).<br><strong>Metrics:</strong> Paid conversion, ARPU. <br><strong>Guardrails:</strong> Net profit (gross conversion profit − experimentation cost) &gt; expected thresholds. <strong>Decision tree:</strong></p><ul><li>Metrics improved &amp; guardrails accepted→<em>Ship it.</em></li><li>Metrics significantly improved &amp; Guardrails hit → Alter strategy and lucky user cadence and retest</li><li>Guardrails affected &amp; metrics unaccepted → <em>Abort and iterate.</em></li><li>Guardrails &amp; metrics unaffected → Retest with a different user segment.</li><li><strong>Review &amp; tradeoffs:</strong> Payment page views can be random actions; even after offers, conversion potential may remain unaffected.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0842516b469b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Instagram Case Study:- Engagement→ Retention→ Growth Loops→ Monetization]]></title>
            <link>https://medium.com/@badjatyatoshika91311/instagram-case-study-engagement-retention-growth-loops-monetization-cc4202f260a1?source=rss-9c008139d933------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc4202f260a1</guid>
            <category><![CDATA[growth-loop]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[casest]]></category>
            <dc:creator><![CDATA[Toshika Badjatya]]></dc:creator>
            <pubDate>Mon, 15 Jun 2026 09:31:50 GMT</pubDate>
            <atom:updated>2026-06-15T09:31:50.622Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yvd3_IsntG-fLJtMkcMONg.avif" /></figure><h3>1) Snapshot</h3><ul><li><strong>Category</strong>: Social media</li><li><strong>Platform(s)</strong>: Primarily Android and iOS, secondary web</li><li><strong>Key Business and Value Proposition:</strong> Instagram provides a platform for users to share photos and videos with their followers. The monetisation frameworks are built around ads and the Instagram businesses.</li></ul><h3>2) Problem &amp; user</h3><ul><li><strong>Casual Browsers:</strong> Use the platform casually as a low-effort, low-commitment way to pass time, avoid boredom, and consume light entertainment without deep engagement. <strong>JTBD:</strong> When I have free time or feel bored, I want quick and effortless entertainment so that I can relax, stay occupied, and mentally switch off without mental coercion to choose and receive an instant dopamine hit. <strong>Triggers:</strong> Boredom, need for instant gratification, lack of commitment, or specific preference on what to watch. <strong>Alternative:</strong> YouTube Shorts, play a game, watch content, or do any low-effort task.</li><li><strong>Social Butterfly:</strong> Uses the platform to connect with long-lost buddies, make new connections, and know about their lives. <strong>JTBD:</strong> When I want to feel socially connected or stay updated on people I know, I use this platform to reconnect and build newer bonds to stay socially relevant. <strong>Triggers:</strong> Maintaining older relationships, FOMO, curiosity about other people’s lives, and the urge to build newer connections. <strong>Alternatives:</strong> Facebook, actual meetups, phone calls.</li><li><strong>Life Documentors:</strong> Use the platform to document key moments of their day-to-day life, share them with close circles, and save them for the future. <strong>JTBD:</strong> When I experience a meaningful or special moment, I want to capture and share it appealingly so that I can preserve the memory, express myself, and feel acknowledged. <strong>Triggers:</strong> Self-expression and social validation.</li><li><strong>Passionate Viewers:</strong> Use the platform to view more content around their point of interest, such as an activity, sport, location, or person. <strong>JTBD:</strong> When I want to dive deeper into something, I use the platform to explore content and express opinions so that I can stay entertained and informed. <strong>Triggers:</strong> Seeking inspiration or escapism, curiosity, and staying updated.</li></ul><h3>3) Key Features &amp; Strategic Purpose</h3><ul><li><strong>Stories and Highlights</strong></li><li><strong>Span of 1 day</strong>: Drives daily frequent opens and lowers posting pressure; encourages authentic/low-effort sharing, as it does not stay permanently on the profile.</li><li><strong>Music + filters</strong>: Increase creation rate and quality, and make it more emotionally expressive. They generate drive for creation and consumption, creating a personal hero moment.</li><li><strong>Highlights + group highlights</strong>: Converts temporary stories into a semi-permanent profile layer, bridging the gap between post and story. Grouping creates a personal playbook experience.</li><li><strong>Story liked + viewed</strong>: Creates lightweight feedback loops (validation for posters; social signalling for viewers), drives engagement, increases app open frequency via notifications, and builds a low-effort interaction medium.</li><li><strong>Ordering based on user interaction</strong>: Maximizes relevance and watch time by prioritizing “who matters most” sequencing.</li></ul><p><strong>Posts and Grid</strong></p><ul><li><strong>Permanent in nature</strong>: Suitable for the moments that matter. Builds social identity and creates progress effects, often leading to reluctance to churn. Supports follow conversion and is a driver for viewer retention.</li><li><strong>No limit on posts</strong>: Supports long-term retention. Drives posting intention to create a memory lane.</li><li><strong>Tags + mentions</strong>: Improves content and profile discovery, and drives notifications for re-engagement.</li><li><strong>Like/share/comment</strong>: Core engagement drivers that create feedback loops, increase session depth and duration (comments), and become input for further recommendations. Share builds a loop for conversion.</li></ul><p><strong>Explore Tab</strong></p><ul><li><strong>Focused Explore (topic-led)</strong>: Search and related topics increase relevance for passion-driven browsing and improve session duration.</li><li><strong>Curated Explore (behaviour-led)</strong>: Personalizes recommendations using watch time, likes, saves, shares, and follows — increasing content consumption and improving retention through “endless relevance”.</li></ul><p><strong>Follow and Following</strong></p><ul><li><strong>Supports Focused Explore (interest deepening)</strong>: The following graph seeds recommendations for content and “similar accounts”, increasing commitment (longer sessions + repeat visits).</li><li><strong>Re-engagement via notifications</strong>: “X followed you”, “X requested to follow you”, “New post/story from X”, and “Suggested accounts” create return triggers and social reciprocity loops (open app → respond → browse).</li><li><strong>Maintains privacy + safety (control = lower churn)</strong>:</li><li><strong>Private accounts + follow requests</strong>: Let users participate without broadcasting to everyone.</li><li><strong>Remove follower / restrict / block</strong>: Reduces harassment risk and increases psychological safety (especially for younger/risk-averse users).</li><li><strong>Close Friends</strong> (Stories) complements privacy by letting users share with a smaller circle.</li></ul><p><strong>Counts create prestige → more creation (status loop)</strong>: Follower/like counts are visible social proof. Milestones (1k/10k/100k) reinforce creator identity and motivate more posting; for viewers, high counts act as a trust shortcut (“worth watching”), increasing follow conversion and accelerating the creator-audience flywheel.</p><h3>4) Core UX and walkthrough</h3><ol><li><strong>Activation</strong>: Time to value is almost instant. Login → Home Screen. The user can view a few generic posts and interests. Explore multiple interests from the Explore screen. Magic moment: — Content explored. <strong>Loop:</strong> Content explored → Viewed, Liked → Recommendation improved → More content explored. (Initial habit formation)</li><li><strong>Engagement</strong> (repeat usage loop): Activated user follows accounts and explores profiles. Sends and accepts requests. <strong>Loop 1:-</strong> Account followed → More accounts recommended → More accounts followed <strong>Loop 2:-</strong> Account followed → Follow back → View posts, story, highlights → Higher engagement (Like, Comment) → More accounts followed <strong>Loop 3:-</strong> Follow/Following → Increased conversation → Post or content shared (improved discovery &amp; higher engagement) → Improved recommendation → More follow and following</li><li><strong>Retention</strong> (what keeps them coming back): Notifications on new content posted or other actions drive re-engagement. A boost in follower and following counts supports repetitive content creation.</li><li><strong>Virality</strong>: Higher retention fuels virality via word of mouth and personal app recommendations.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qBqZ9cXka0_M0zS_0dEJCQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iPnDl51v-OvIoarVwj2lhA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*liRwjpH1A7pbgxW9c9klTQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*BBKanuA6ei7OLW4IqDdiwA.png" /></figure><h3>5) Metrics (what to measure)</h3><ul><li><strong>North Star Metric</strong>: Daily Active Users, Time Spent Per Daily Active User</li><li><strong>Activation metric</strong>: Time to first content interaction, Session Duration, Like or Comment Frequency</li><li><strong>Engagement metric</strong>: Weekly content posted, Suggested Profile Follow %, Weekly account followed, Conversation session duration, Average viewer count per content</li><li><strong>Retention metric</strong>: DAU, MAU, WAU, Weekly Creator Users</li></ul><h3>6) Retention</h3><p>Feature list (grouped)</p><p><strong>Must-have / table stakes</strong></p><ul><li>Stories (may lose over Snapchat)</li><li>Reels (may lose over TikTok and YouTube Shorts)</li><li>DMs or personal messaging (lose engagement, retention and content-sharing loops)</li><li>User Profile (Followers, following, grid, etc.) Social prestige and validation are a moat for Instagram.</li></ul><p><strong>Differentiators</strong></p><ul><li><strong>Social Identity:-</strong> While most other platforms focus on content consumption, Instagram stories, posts and reels allow users to create as a form of expression. The effort required to create content generates a feeling of accomplishment (self-satisfaction reward).</li></ul><p><strong>Power features</strong></p><ul><li><strong>Explore:-</strong> The perfect blend of <strong>“what you want to see”,</strong> <strong>“what you might see” &amp; “what you might not see”</strong> creates a perfect variable reward, encouraging users to hunt for preferences, leading to higher session time and increased engagement</li><li><strong>Recommendation:-</strong> The algorithm, which updates instantly based on where you are, what you like on other platforms, what you say, current trends and hundreds of other factors, creates an emotion of <strong>“product understands you”</strong></li></ul><p><strong>Integrations</strong></p><ul><li>Instagram’s affiliation with Facebook leads to seamless integration across platforms —WhatsApp, Instagram, and Facebook —enabling cross-functional sharing and higher activation and engagement.</li></ul><h3>7) Growth loops</h3><p>Not a single loop, but multiple loops fueling each other</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vl3FoM78CPnQorHGMW388Q.png" /></figure><h3>8) Monetization</h3><p>High engagement is a moat for Instagram; hence, it can ensure high footfall and viewership for brands and advertisements, becoming the key driver for monetization.</p><p><strong>Unique Value Proposition </strong>— Instagram does not monetize content created or shared, as this might hamper user retention, which is the key driver for monetization.</p><h3>9) Unique Behaviour</h3><p>One behaviour that intrigued me the most is time management on Instagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*_LXOvH7OxLKWxXAZoRFIRQ.png" /></figure><p>With North Star metrics being Time Spent Per Daily Active User, this feature alone can affect the metrics significantly</p><p><strong>Strategic Decision:-</strong> It provides users with autonomy to choose how much time they spend on the app instead of compelling them to do so, becoming a key driver of user trust, long-term retention, and healthier platform perception.</p><h3>10) Takeaways and Ideas</h3><ul><li>Growth loops are the key driver of high-growth products, reducing CAC and propelling product-led growth.</li><li>Simplicity significantly contributes towards higher adoption, often creating motivation to do more. (Steps, physical and cognitive load, cost, relevance with daily routine)</li><li>Variable rewards often beat monetary rewards. Monotony and predictability can reduce retention over time. Find the user’s drive and reward accordingly.</li></ul><h3>11) Product Suggestion</h3><p><strong>Problem Statement:</strong> Anna, a doom-scrolling addict, keeps uninstalling the app, not because of its performance but because it becomes extremely addictive. <strong>Goals:-</strong> Provide users with a guilt-free indulgence</p><p><strong>Task:-</strong> For users like this, we can have an option of groom scrolling (optional). <strong>Action Items: -</strong></p><ul><li>A user can limit the topics on which reels would be recommended</li><li>Polite nudges when the user is scrolling too frequently</li><li>Limit actions (specify the goal for the visit: checking friends’ reels, having a conversation, uploading a post and then avoid wandering)</li></ul><p><strong>Result:-</strong> Decrease in session duration but increase in fulfilment; avoid churn due to guilt.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc4202f260a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Sense Question]]></title>
            <link>https://medium.com/@badjatyatoshika91311/product-sense-question-d20c8dacf146?source=rss-9c008139d933------2</link>
            <guid isPermaLink="false">https://medium.com/p/d20c8dacf146</guid>
            <category><![CDATA[product-sense]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[spotify]]></category>
            <dc:creator><![CDATA[Toshika Badjatya]]></dc:creator>
            <pubDate>Tue, 26 May 2026 17:30:25 GMT</pubDate>
            <atom:updated>2026-05-26T17:30:25.397Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Question:- Design Netflix for Kids</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G8cSMaGQiabxnB5Wm_m6rw.png" /></figure><p><strong>Step1:- Clarifying Question<br>1. Are kids users or consumers? Do we have a secondary persona, like parents, operating it for kids?<br></strong>Assumption:- Kids can be both. Parents use the platform for younger kids.</p><p><strong>2. Is it for a specific age group? <br></strong>Assumption:-<strong> </strong>3–15 years</p><p><strong>3. Is it a separate product or an additional feature on Netflix?<br></strong>Assumption:-<strong> </strong>Additional feature within the product.</p><p><strong>4. What is the goal of acquisition, monetization, or increasing engagement?<br></strong>Assumption:-<strong> </strong>Increase engagement for existing users</p><p><strong>5. Is it based on a specific demography, like India, or can we consider worldwide users?<br></strong>Assumption:- Focus on India as of now</p><p><strong>Step 2:- Competitive Analysis:- Youtube Kids<br>Strengths:- </strong>Age-based personalization, parental control, time control<br><strong>Weakness (Compared to Netflix):- </strong>random and scattered content, ads, poor video quality, need for YouTube Premium</p><p><strong>Step 3:- User Persona</strong></p><p><strong>Young Kids(Age 3–5):- <br>- </strong>No specific preference developed<br>- Not too addicting<br>- Visuals are appealing and engaging<br>- Learn while you play<br>- Users (parents) and consumers (kids)</p><p><strong>Kids (Age 6–10):-<br>- </strong>Games/Superhero/Educational/Habit-centric/ Cartoons<br>- Specific preferences<br>- Influenced by friends&#39; preferences<br>- Parents are skeptical about access to content<br>- Users (kids) and supervisors (parents)</p><p><strong>Teenagers (10–15):- <br>- </strong>Educational and knowledge-driven<br>- Web series, dramas from different countries<br>- Social media influence is strong<br>- Changing preferences<br>- Inclination towards age-inappropriate content</p><p><strong>Specially Abled Kids:-</strong> In all categories</p><p><strong>Step 4: Prioritization for persona<br></strong>Framework:- Engagement Potential, Existing user base, Teenagers</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fs4kgbSHd8wLw_zGwLsFrg.png" /></figure><p>Based on the finding:- Toddlers (quick win) and Teenagers (big bet)</p><p><strong>Step 5:- Pain points and Desires via JTBD</strong></p><ol><li><strong>Toddlers:-</strong> I want my parents to believe it&#39;s useful and not another tool for distraction [Against Netflix&#39;s core business of engagement]</li><li><strong>Toddlers:- </strong>I want all my interests in one place and easy browsing</li><li><strong>Toddlers:-</strong> I want to know what my friend is watching and tell about mine.</li><li><strong>Teenager:- </strong>I have multiple interests and options, how is this better [Unpredictable]</li><li><strong>Teenager:-</strong> I need to buy a couple of courses to learn. Can it provide the same to me? [Netflix is not in the education business]</li><li><strong>Teenager: </strong>I want exclusive access to my interests and favourite celebrity or influencer that other people do not have.</li><li>AI looks cool to me. Can I have it as a feature?</li></ol><p><strong>Step 6:- Top solutions</strong></p><ol><li>An advanced dashboard for parents where the user can have the option to plan content and proof-read via AI to get potential unwanted content from video via sentiment analysis, and an option to eliminate all videos with X% unsuitable content (configurable).</li><li>Group watching, where you can invite a friend by sending a notification and sync playback. Ability to chat via watching videos with advanced reactions, GIFs, and voice chat. Existing feature, enhance and improve discovery.</li><li>Collaboration with a prominent influencer for exclusive updates from their lives in the form of a 20–30-minute video</li></ol><p><strong>Metrics and Evaluation</strong></p><ol><li><strong>Business Metrics:- </strong>Engagement (Weekly time spent by the cohort of children)</li><li><strong>Core Metrics:- </strong>Parent Engagement Rate With Dashboard, No. of group watching sessions per week, Average group session participants, Views on Influencer Content (1st hour, 1st day, 1st week)</li><li><strong>Supporting Metrics:- </strong>Efficacy of AI filter algorithm (precision, completeness, confidence, latency), Parent Satisfaction Score on AI filtering.</li><li><strong>Guardrail Metrics:-</strong> False negatives (filtering of relevant videos), engagement on other influencer content, cumulative watch time (solo + group), api costs</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d20c8dacf146" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding LLM:- In the language of a 10-year-old]]></title>
            <link>https://medium.com/@badjatyatoshika91311/understanding-llm-in-the-language-of-a-10-year-old-a3abf6005e3d?source=rss-9c008139d933------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3abf6005e3d</guid>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[tokenization]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Toshika Badjatya]]></dc:creator>
            <pubDate>Sun, 03 May 2026 19:24:03 GMT</pubDate>
            <atom:updated>2026-05-03T19:24:03.596Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d4_WQ3KwMp7M6r3Pd7jUXQ.png" /></figure><p>For this article, imagine you are Harry, a 10- year old boy<br>So, Harry, complete this sentence</p><p><strong>Apple a day keeps _______ away</strong></p><p>I believe your answer was doctor. How did you predict you could have answered a parrot, nurse, or police? <br>You understood the sentence, used your past knowledge, and predicted the best possible answer. You could have said parrot as well, because there are no accurate answers, only more correct and less correct answers.</p><p>Let’s see how AI does it and how it is similar to Harry’s approach</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TB6x-s7ZTfIF7JECntLMWg.png" /></figure><p><strong>Tokenization(Breaking down the sentence):- </strong>Breaking the input into smaller units so that the LLM can understand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G5LBY2PJadx5wduPRybmpw.png" /><figcaption>By default each word is a new token</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qlIxyZxi9tPgXuqtEzf1xw.png" /><figcaption>Often a word could be broken down into different tokens</figcaption></figure><p>Now, each token is assigned an ID and stored in the form of a vector or array, <br><strong> e.g.,- supercallifragilisticexpialidocious becomes [17789, 9925, 366, 17764, 311, 6207, 8067, 563, 315, 170661]. <br></strong><em>LLM is trained on billions of words or tokens, and each token has a unique ID</em></p><p><strong>Embedding(Deriving meaning of each word):-</strong> Break the token into coordinates to understand the meaning.<br>Let’s say x means a fruit and y means a liquid<br><strong>Mango:- (10,0)<br>Apple Juice:- (10,10)<br>Tomato Puree:- (6, 8)<br>Tea:- (0,10)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*hM_8C6sJr0Be4JtthnLT2g.png" /></figure><p>The relationship between words is determined by the distance between them in space.</p><p><strong>Prediction:-</strong>Use pattern recognition or semantic search from existing data and the token provided to predict the next word.</p><p>From the example, the prediction could be a doctor or a parrot; the same happens with AI.<br>Here comes the temperature, which controls the randomness of the prediction<br><strong>Low temperature = High precision <br>High temperature = Low precision (high randomness)</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3abf6005e3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Logging in ViewModel: Are you doing it right?]]></title>
            <link>https://medium.com/@badjatyatoshika91311/logging-in-viewmodel-are-you-doing-it-right-3e0d099093b2?source=rss-9c008139d933------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e0d099093b2</guid>
            <category><![CDATA[mockito]]></category>
            <category><![CDATA[unit-testing-tools]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[performance-optimization]]></category>
            <category><![CDATA[android-app-development]]></category>
            <dc:creator><![CDATA[Toshika Badjatya]]></dc:creator>
            <pubDate>Tue, 24 Mar 2026 06:48:46 GMT</pubDate>
            <atom:updated>2026-03-24T06:48:46.961Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1GYsSnQUudfQ20GGPxITwQ.png" /></figure><p>Before we move forward, take a moment to reflect — what’s wrong with this piece of code?</p><pre>class NewsViewModel: ViewModel(){<br>    init {<br>        Log.e(&quot;TAG&quot;,&quot;viewmodel initialized&quot;)<br>        fetchData()<br>    }<br>    <br>}</pre><p>Looks correct, right? It’s something we use almost every day.</p><p>But here’s the catch — this class isn’t suitable for local unit testing. Let’s break down why.</p><p><strong>What exactly is a Local Unit Test?</strong></p><p>A <strong>local unit test</strong> is a type of test where a piece of code is executed on your <strong>local machine (JVM)</strong>, without requiring a real Android device or emulator.</p><p><strong>Why use Local Unit Test instead of Instrumented Test?</strong></p><p>Simple answer!! As it does not require an emulator or a device, it is much faster.</p><p><strong>What’s the issue in the codebase?</strong></p><p>The init block uses <strong>Log.e (android.util.Log)</strong>. <br>Classes like Context, Resources, ConnectivityManager, Log etc belongs to the <strong>android.jar</strong> library. All these classes depend on the Android runtime and hence cannot run on the JVM; therefore, you’ll see an error like this when running the test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EVtQa1-lds47eOBCWjsvdQ.png" /></figure><p><strong>What should we do instead?</strong></p><p><strong>Simple answer</strong>: use an interface.</p><pre>interface Logger {<br>    fun log(tag: String,msg: String)<br>}</pre><ul><li>Create two implementations of the interface: one for app execution (production) and another for testing.</li></ul><pre>class AppLogger: Logger{<br>    override fun log(tag: String, msg: String) {<br>       Log.e(tag,msg)<br>    }<br><br>}<br>class TestLogger: Logger{<br>    override fun log(tag: String, msg: String) {<br>       //no test implementation<br>    }<br><br>}</pre><ul><li>Inject the logger within the ViewModel.</li></ul><pre>class NewsViewModel@Inject constructor(val logger:Logger): ViewModel(){<br>    init {<br>        Logger.log(&quot;TAG&quot;,&quot;viewmodel initialized&quot;)<br>        fetchData()<br>    }<br>    <br>}</pre><ul><li>Provide the appropriate implementation based on the use case, <br>Inject AppLogger via DI (or any preferred method) for app execution.</li></ul><pre>   @Provides<br>   @Singleton<br>   fun getLogger(): Logger{<br>       return AppLogger()<br>   }</pre><ul><li>Provide TestLogger in the viewModel for unit test.</li></ul><pre>    <br> @Test<br>fun testViewmodel(){<br>......<br>val viewModel = NewsViewModel(TestLogger())<br>......<br>}</pre><p><strong>Outcomes Achieved</strong></p><ul><li>Logs are captured during app runtime.</li><li>Unit tests run seamlessly on the JVM.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e0d099093b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GraphQL for Android Developers: What, Why, and How]]></title>
            <link>https://medium.com/@badjatyatoshika91311/graphql-for-android-developers-what-why-and-how-e0dd3243a2e7?source=rss-9c008139d933------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0dd3243a2e7</guid>
            <category><![CDATA[graphql-vs-rest]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[aws-amplify]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Toshika Badjatya]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 13:14:44 GMT</pubDate>
            <atom:updated>2026-03-02T13:14:44.202Z</atom:updated>
            <content:encoded><![CDATA[<p>If REST is a popular, widely used, and easy-to-adopt API framework, why should we consider GraphQL?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0f4dvSifVihCIgWtXuBXnQ.png" /></figure><p>Let’s understand this with an example.</p><p>Consider a case where you want some groceries for your household:</p><ul><li>You need <strong>apples</strong>, but the grocery store sells only fruit boxes containing <strong>apples, bananas, and oranges</strong>.<br> You end up buying the entire box even though you only needed apples — this is <strong>overfetching</strong>.</li><li>You want an <strong>apple</strong> and a <strong>battery</strong>.<br> You go to a grocery store to buy the apple and then to an electrical shop to buy the battery, instead of going to a supermarket where you could get both — this is <strong>underfetching</strong>.</li></ul><p>Now that the concepts are clear, let’s compare <strong>REST</strong> and <strong>GraphQL</strong> on the same ground.</p><p><strong>Case 1:- Get apples(Overfetching)</strong></p><p><strong>REST<br>API:- </strong>GET /api/fruits<strong><br>Response:-</strong></p><pre>{<br>  &quot;status&quot;: &quot;success&quot;,<br>  &quot;data&quot;: [<br>    {<br>      &quot;name&quot;: &quot;Apple&quot;,<br>      &quot;cost&quot;: 120,<br>    },<br>    {<br>      &quot;name&quot;: &quot;Banana&quot;,<br>      &quot;cost&quot;: 40,<br>    },<br>    {<br>      &quot;name&quot;: &quot;Orange&quot;,<br>      &quot;cost&quot;: 60,<br>    }<br>  ]<br>}</pre><p><strong>GraphQL<br>API:-</strong></p><pre>query GetApplePrice {<br>  fruits(name: &quot;Apple&quot;) {<br>    name<br>    cost<br>  }<br>}</pre><p><strong>Response:-</strong></p><pre>{<br>  &quot;status&quot;: &quot;success&quot;,<br>  &quot;data&quot;: {<br>      &quot;name&quot;: &quot;Apple&quot;,<br>      &quot;cost&quot;: 120,<br>   }<br>}</pre><p><strong>Case 2:- Get apples+ batteries (Underfetching)</strong></p><p><strong>REST<br>API:- </strong>GET /api/fruits &amp; GET /api/hardware<strong><br>Response:-</strong></p><pre>//Response 1<br>{<br>  &quot;status&quot;: &quot;success&quot;,<br>  &quot;data&quot;: [<br>    {<br>      &quot;name&quot;: &quot;Apple&quot;,<br>      &quot;cost&quot;: 120,<br>    },<br>    {<br>      &quot;name&quot;: &quot;Banana&quot;,<br>      &quot;cost&quot;: 40,<br>    },<br>    {<br>      &quot;name&quot;: &quot;Orange&quot;,<br>      &quot;cost&quot;: 60,<br>    }<br>  ]<br>}<br>//Response 2<br>{<br>  &quot;status&quot;: &quot;success&quot;,<br>  &quot;data&quot;: [<br>    {<br>      &quot;name&quot;: &quot;Keyboard&quot;,<br>      &quot;cost&quot;: 1500<br>    },<br>    {<br>      &quot;name&quot;: &quot;Battery&quot;,<br>      &quot;cost&quot;: 800<br>    },<br>    {<br>      &quot;name&quot;: &quot;Monitor&quot;,<br>      &quot;cost&quot;: 12000<br>    }<br>  ]<br>}</pre><p><strong>GraphQL<br>API:-</strong></p><pre>query GetAppleAndBatteryPrice {<br>  apple: fruits(name: &quot;Apple&quot;) {<br>    name<br>    cost<br>  }<br>  battery: hardware(name: &quot;Battery&quot;) {<br>    name<br>    cost<br>  }<br>}</pre><p><strong>Response:-</strong></p><pre>{<br>  &quot;status&quot;: &quot;success&quot;,<br>  &quot;data&quot;: [<br>    {<br>      &quot;name&quot;: &quot;Apple&quot;,<br>      &quot;cost&quot;: 120,<br>    },<br>   {<br>      &quot;name&quot;: &quot;Battery&quot;,<br>      &quot;cost&quot;: 800<br>    }<br>  ]<br>}</pre><p>Now, as the difference and utility of GraphQL are clear, let’s understand<br><strong>What </strong>is GraphQL (don’t worry, not a heavy definition)</p><p>It is a query-based language for your API.</p><p>Client:- Specify <strong>what</strong> is needed in the form of queries.</p><p>Server:- Validates if it <strong>can be</strong> provided, and if yes, <strong>provides</strong> the response</p><p><strong>Components of GraphQL</strong></p><ul><li><strong>Schema:- </strong>Specify the database structure. Equivalent to a <strong>database schema</strong>.</li></ul><pre>type User @model {<br>  accountId: String<br>  moduleId: String<br>  userId:String <br>  userName:String <br>}</pre><ul><li><strong>Query:- </strong>Used to fetch data. Equivalent to <strong>GET</strong>. Output is usually in the form of stringified JSON</li></ul><pre>query GetUser(<br>  $userId: ID!<br>) {<br>  getUser(<br>    userId: $userId<br>  ) {<br>    data {<br>      userId<br>      userName<br>    }<br>    success<br>    errors<br>  }<br>}  </pre><ul><li><strong>Mutation:- </strong>Used to make changes. Equivalent to POST, PUT, and PATCH. Specify the input and output parameters.</li></ul><pre>mutation CreateUser(<br>  $user: User!<br>) {<br>  createUser(<br>    user: $user<br>  ) {<br>    data {<br>      userId<br>      userName<br>    }<br>    success<br>    errors<br>  }<br>}</pre><ul><li><strong>Subscription:- </strong>Used for the <strong>publication-subscribe</strong> model to subscribe to a channel and act on an event trigger</li></ul><pre>subscription SubscribeToNewUser {<br>  subscribe2channel(channel:&quot;users&quot;) {<br>    userId<br>    userName<br>  }<br>}</pre><p>Now that we understand what GraphQL is, let’s look at how to use it. One such way to use GraphQL is through AWS.</p><p><strong>AWS</strong> offers a broad set of tools for iOS, Android, and web applications.</p><ul><li><strong>Amplify</strong>:<br>Amplify is a developer framework for using GraphQL. It provides features such as <strong>Auth</strong> for authentication and <strong>API</strong> for GraphQL API usage. Developers can write queries to specify both input and output.</li></ul><pre>//use mutation mentioned above as a string<br> Amplify.API.mutate(createUserRequest, { response -&gt;<br>   }<br> }</pre><ul><li><strong>Appsync</strong>:<br> AppSync is a managed GraphQL service by AWS where developers can define a schema and related rules. Based on this schema, it generates the required operations (classes &amp; functions) that can be invoked — similar to how Retrofit works for REST APIs.<br>AppSync also integrates with services like <strong>Cognito</strong> for authentication and <strong>DataStore</strong> for a managed, offline-first key-value database.</li></ul><pre>  fun createUser(user:User): UserResponse</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0dd3243a2e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ScreenTimeAnalytics]]></title>
            <link>https://medium.com/@badjatyatoshika91311/screentimeanalytics-5f6ca39cee37?source=rss-9c008139d933------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f6ca39cee37</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[system-design-interview]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[library-design]]></category>
            <dc:creator><![CDATA[Toshika Badjatya]]></dc:creator>
            <pubDate>Thu, 26 Feb 2026 06:35:16 GMT</pubDate>
            <atom:updated>2026-04-21T16:37:22.288Z</atom:updated>
            <content:encoded><![CDATA[<p>Analyzing user behaviour in Android — if this is your requirement, you’re in the right place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jUEAcLNZzyQFphhaeZEg1g.png" /></figure><p><strong>What is the need to analyze user screen time?</strong></p><ul><li><strong>More time spent in the payment flow</strong> — the journey may be complex or time-consuming for the user.</li><li><strong>More time spent on the feed</strong> — the user is engaged and enjoying the experience.</li><li><strong>Less time spent on the search screen</strong> — search is effective, and the user can easily find what they need.</li></ul><p>This, and much more. Analyzing screen time enables teams to understand user interaction patterns and supports data-driven decision-making for future product improvements.</p><p><strong>How to use the library??</strong></p><p>1&gt; Add the dependencies</p><pre>//build.gradle (app)<br>dependencies {<br>     implementation (&quot;com.github.ToshikaBadjatya:ScreenTimeAnalytics:1.0.0&quot;)<br>     kapt (&quot;com.github.ToshikaBadjatya.ScreenTimeAnalytics:annotation-processor:1.0.0&quot;)<br>}<br></pre><pre>//settings.gradle <br>dependencyResolutionManagement {<br>    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)<br>    repositories {<br>        google()<br>        mavenCentral()<br>        maven { url &#39;https://jitpack.io&#39; } // this one<br>    }<br>}</pre><p>2&gt; Create a custom analytics client</p><pre>class CustomAnalyticsClient: AnalyticsClient {  <br>    override suspend fun sendEvent(response: ScreenTimeResponse) {<br>       // specify where and how to sync data<br>    }<br>}</pre><p>3&gt; Configure ScreenTimeAnalytics in the Application class</p><pre><br>class MainApplication: Application() {<br>    override fun onCreate() {<br>        super.onCreate()<br>        val analyticsClient= CustomAnalyticsClient()<br>        val config =<br>            ScreenTimeConfig.Builder()<br>                .showTimes(true)<br>                .showPercentage(true)<br>                .timeUnit(TimeUnit.SECONDS)<br>                .analyticsClient(analyticsClient)<br>                .setLocale(Locale.getDefault())<br>                .setStorage(PersistentStorageType.DATABASE)<br>                .build()<br>        ScreenTimeAnalytics.init(this, config)<br>    }<br>}</pre><p>4&gt; Mark activities as trackable</p><pre>@TrackActivity<br>class MainActivity : ScreenTimeActivity() {<br>}</pre><p><strong>Library Architecture</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*34MTb0-3uH3fBipVmApY-g.png" /></figure><p>1&gt; In the application class, initialize the library by specifying a configuration suitable for your requirements.</p><p>2&gt; Mark the activities to be captured and analyzed as <strong>Trackable</strong> using the @TrackActivity annotation.</p><p>3&gt; When an activity resumes and becomes interactive, the event is started. When the activity stops, the event is stopped, and the entry is logged using the analytics library.</p><p>4&gt; To ensure persistence and reliable data syncing, events are temporarily logged in a user-selected storage option (Filesystem or Room)</p><p>5&gt; When the application is destroyed or killed due to a system event, data sync is initiated via <strong>WorkManager</strong>.</p><p>6&gt; If the data sync is not completed in the background, any unsynced events are synced during the next app usage.</p><p>7&gt; During data sync, the raw event data is processed and combined, and then made available to the user-defined analytics client.</p><p>8&gt; Users can specify how data should be synced — using Firebase, a personal backend, or any other preferred option in the analytics client.</p><p><strong>Sample sync JSON (JSON format and values can be modified based on ScreenTimeConfig)</strong></p><pre>{<br>  &quot;syncId&quot;: &quot;5c75743a-3b4e-4887-afc0-95d8ed16bca2&quot;,<br>  &quot;screenTimeObjects&quot;: [<br>    {<br>      &quot;screenName&quot;: &quot;MainActivity&quot;,<br>      &quot;totalTime&quot;: 0.014655000000000001,<br>      &quot;durations&quot;: [<br>        {<br>          &quot;startDate&quot;: &quot;2026-02-23&quot;,<br>          &quot;endDate&quot;: &quot;2026-02-23&quot;,<br>          &quot;startTime&quot;: &quot;19:45:10&quot;,<br>          &quot;endTime&quot;: &quot;19:46:02&quot;,<br>          &quot;duration&quot;: &quot;52s&quot;<br>        }<br>      ]<br>    },<br>    {<br>      &quot;screenName&quot;: &quot;SecondActivity&quot;,<br>      &quot;totalTime&quot;: 0.0028460000000000003,<br>      &quot;durations&quot;: [<br>        {<br>          &quot;startDate&quot;: &quot;2026-02-23&quot;,<br>          &quot;endDate&quot;: &quot;2026-02-23&quot;,<br>          &quot;startTime&quot;: &quot;19:46:10&quot;,<br>          &quot;endTime&quot;: &quot;19:46:27&quot;,<br>          &quot;duration&quot;: &quot;17s&quot;<br>        }<br>      ]<br>    }<br>  ],<br>  &quot;screenTimePercents&quot;: {<br>    &quot;MainActivity&quot;: 83.70937339349975,<br>    &quot;SecondActivity&quot;: 16.290626606500258<br>  }<br>}</pre><p><strong>Future Goals</strong></p><ul><li>As of now, tracking is limited to activities. This will be extended to support <strong>Fragments and Compose screens</strong>.</li><li>Support for lifecycle tracking will provide insights into the date and time of <strong>uninstall</strong>, along with a detailed summary of the last interaction date to help derive analytics related to uninstall behaviour.</li></ul><p><strong>Github<br></strong>Do check out the library here:- <a href="https://github.com/ToshikaBadjatya/ScreenTimeAnalytics">https://github.com/ToshikaBadjatya/ScreenTimeAnalytics</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f6ca39cee37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Machine Coding Round Guide For Android Developers]]></title>
            <link>https://medium.com/@badjatyatoshika91311/machine-coding-round-guide-for-android-developers-0483b3da3ecb?source=rss-9c008139d933------2</link>
            <guid isPermaLink="false">https://medium.com/p/0483b3da3ecb</guid>
            <dc:creator><![CDATA[Toshika Badjatya]]></dc:creator>
            <pubDate>Tue, 03 Feb 2026 07:01:59 GMT</pubDate>
            <atom:updated>2026-02-03T07:49:50.472Z</atom:updated>
            <content:encoded><![CDATA[<p>A quick checklist to save time and help you put your best foot forward in any machine coding round.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uc_IW-n_85qU52Vppy6_9w.jpeg" /></figure><p><strong>Add ./idea in gitignore<br></strong>The .idea folder contains files that are specific to a particular developer’s local machine and IDE configuration and therefore should not be pushed to GitHub.<br>Run the project to check for any configuration issues.</p><p><strong>Check Gradle and Kotlin version compatibility<br></strong>If an issue arises, it is likely due to a conflict between the Gradle and Kotlin versions. Configure the dependencies and plugins needed for the project.</p><p><strong>Configure the dependency and plugins needed for the project</strong></p><p>Sample configuration that can be referred to (jdk- 17)</p><pre>//gradle-wrapper.properties<br>distributionBase=GRADLE_USER_HOME<br>distributionPath=wrapper/dists<br>distributionUrl=https\://services.gradle.org/distributions/gradle-8.13-bin.zip<br>zipStoreBase=GRADLE_USER_HOME<br>zipStorePath=wrapper/dists</pre><pre>//build.gradle(project)<br>plugins {<br>    alias(libs.plugins.android.application) apply false<br>    alias(libs.plugins.kotlin.android) apply false<br>    alias(libs.plugins.kotlin.compose) apply false<br>    alias(libs.plugins.hilt) apply false<br>}</pre><pre>//build.gradle (app) essentials<br>plugins {<br>    alias(libs.plugins.android.application)<br>    alias(libs.plugins.kotlin.android)<br>    alias(libs.plugins.kotlin.compose)<br>    alias(libs.plugins.ksp)<br><br>}<br><br>// using XML <br> buildFeatures {<br>     viewBinding =true<br> }<br><br>dependencies{<br>...<br>   //Architectural Components<br>    implementation(libs.androidx.lifecycle.viewmodel.ktx)<br><br>    //Room<br>    implementation(libs.androidx.room.runtime)<br>    kapt(libs.room.compiler)<br>    implementation(libs.androidx.room.ktx)<br><br>    //Coroutines<br>    implementation(libs.kotlinx.coroutines.core)<br>    implementation(libs.kotlinx.coroutines.android)<br>    implementation(libs.androidx.lifecycle.runtime.ktx.v261)<br><br>    //Retrofit<br>    implementation(libs.retrofit)<br>    implementation(libs.converter.gson)<br>    implementation(libs.logging.interceptor)<br><br>    //Navigation Components<br>    implementation(libs.androidx.navigation.fragment.ktx)<br>    implementation(libs.androidx.navigation.ui.ktx)<br><br>    //or compose navigation <br>    implementation(libs.androidx.navigation.fragment.ktx)<br>    implementation(libs.androidx.navigation.ui.ktx)<br><br>    //Dagger(hilt)<br>    implementation(libs.hilt.android)<br>    ksp(libs.hilt.compiler)<br>    implementation(libs.androidx.hilt.common)<br><br>    //or just dagger2<br>    implementation(libs.google.dagger)<br>    ksp(libs.google.dagger.compiler)<br><br>    //paging 3<br>    implementation(libs.androidx.paging.runtime.ktx)<br>    implementation(libs.androidx.paging.compose)<br>}<br>  </pre><pre>[versions]<br>agp = &quot;8.12.3&quot;<br>dagger = &quot;2.57.1&quot;<br>daggerCompiler = &quot;2.57.1&quot;<br>hiltAndroid = &quot;2.57.1&quot;<br>hiltCompiler = &quot;2.57.1&quot;<br>kotlin = &quot;2.0.21&quot;<br>coreKtx = &quot;1.17.0&quot;<br>junit = &quot;4.13.2&quot;<br>junitVersion = &quot;1.3.0&quot;<br>espressoCore = &quot;3.7.0&quot;<br>lifecycleRuntimeKtx = &quot;2.10.0&quot;<br>activityCompose = &quot;1.12.2&quot;<br>composeBom = &quot;2024.09.00&quot;<br>kotlinxCoroutinesAndroid = &quot;1.6.4&quot;<br>kotlinxCoroutinesCore = &quot;1.10.2&quot;<br>lifecycleRuntimeKtxVersion = &quot;2.6.1&quot;<br>lifecycleViewmodelKtx = &quot;2.6.1&quot;<br>loggingInterceptor = &quot;4.5.0&quot;<br>navigationCompose = &quot;2.8.5&quot;<br>navigationFragmentKtx = &quot;2.6.0&quot;<br>pagingRuntimeKtx = &quot;3.3.6&quot;<br>retrofit = &quot;2.9.0&quot;<br>roomCompiler = &quot;2.5.2&quot;<br>roomKtx = &quot;2.5.2&quot;<br>roomRuntime = &quot;2.5.2&quot;<br>converterGson = &quot;2.9.0&quot;<br><br><br>[libraries]<br>androidx-core-ktx = { group = &quot;androidx.core&quot;, name = &quot;core-ktx&quot;, version.ref = &quot;coreKtx&quot; }<br>androidx-lifecycle-runtime-ktx-v261 = { module = &quot;androidx.lifecycle:lifecycle-runtime-ktx&quot;, version.ref = &quot;lifecycleRuntimeKtxVersion&quot; }<br>androidx-lifecycle-viewmodel-ktx = { module = &quot;androidx.lifecycle:lifecycle-viewmodel-ktx&quot;, version.ref = &quot;lifecycleViewmodelKtx&quot; }<br>androidx-navigation-compose = { module = &quot;androidx.navigation:navigation-compose&quot;, version.ref = &quot;navigationCompose&quot; }<br>androidx-navigation-fragment-ktx = { module = &quot;androidx.navigation:navigation-fragment-ktx&quot;, version.ref = &quot;navigationFragmentKtx&quot; }<br>androidx-navigation-ui-ktx = { module = &quot;androidx.navigation:navigation-ui-ktx&quot;, version.ref = &quot;navigationFragmentKtx&quot; }<br>androidx-paging-compose = { module = &quot;androidx.paging:paging-compose&quot;, version.ref = &quot;pagingRuntimeKtx&quot; }<br>androidx-paging-runtime-ktx = { module = &quot;androidx.paging:paging-runtime-ktx&quot;, version.ref = &quot;pagingRuntimeKtx&quot; }<br>androidx-room-ktx = { module = &quot;androidx.room:room-ktx&quot;, version.ref = &quot;roomKtx&quot; }<br>androidx-room-runtime = { module = &quot;androidx.room:room-runtime&quot;, version.ref = &quot;roomRuntime&quot; }<br>converter-gson = { module = &quot;com.squareup.retrofit2:converter-gson&quot;, version.ref = &quot;converterGson&quot; }<br>dagger-hilt-compiler = { module = &quot;com.google.dagger:hilt-compiler&quot;, version.ref = &quot;hiltCompiler&quot; }<br>hilt-android = { module = &quot;com.google.dagger:hilt-android&quot;, version.ref = &quot;hiltAndroid&quot; }<br>google-dagger = { module = &quot;com.google.dagger:dagger&quot;, version.ref = &quot;dagger&quot; }<br>google-dagger-compiler = { module = &quot;com.google.dagger:dagger-compiler&quot;, version.ref = &quot;daggerCompiler&quot; }<br>junit = { group = &quot;junit&quot;, name = &quot;junit&quot;, version.ref = &quot;junit&quot; }<br>androidx-junit = { group = &quot;androidx.test.ext&quot;, name = &quot;junit&quot;, version.ref = &quot;junitVersion&quot; }<br>androidx-espresso-core = { group = &quot;androidx.test.espresso&quot;, name = &quot;espresso-core&quot;, version.ref = &quot;espressoCore&quot; }<br>androidx-lifecycle-runtime-ktx = { group = &quot;androidx.lifecycle&quot;, name = &quot;lifecycle-runtime-ktx&quot;, version.ref = &quot;lifecycleRuntimeKtx&quot; }<br>androidx-activity-compose = { group = &quot;androidx.activity&quot;, name = &quot;activity-compose&quot;, version.ref = &quot;activityCompose&quot; }<br>androidx-compose-bom = { group = &quot;androidx.compose&quot;, name = &quot;compose-bom&quot;, version.ref = &quot;composeBom&quot; }<br>androidx-ui = { group = &quot;androidx.compose.ui&quot;, name = &quot;ui&quot; }<br>androidx-ui-graphics = { group = &quot;androidx.compose.ui&quot;, name = &quot;ui-graphics&quot; }<br>androidx-ui-tooling = { group = &quot;androidx.compose.ui&quot;, name = &quot;ui-tooling&quot; }<br>androidx-ui-tooling-preview = { group = &quot;androidx.compose.ui&quot;, name = &quot;ui-tooling-preview&quot; }<br>androidx-ui-test-manifest = { group = &quot;androidx.compose.ui&quot;, name = &quot;ui-test-manifest&quot; }<br>androidx-ui-test-junit4 = { group = &quot;androidx.compose.ui&quot;, name = &quot;ui-test-junit4&quot; }<br>androidx-material3 = { group = &quot;androidx.compose.material3&quot;, name = &quot;material3&quot; }<br>kotlinx-coroutines-android = { module = &quot;org.jetbrains.kotlinx:kotlinx-coroutines-android&quot;, version.ref = &quot;kotlinxCoroutinesAndroid&quot; }<br>kotlinx-coroutines-core = { module = &quot;org.jetbrains.kotlinx:kotlinx-coroutines-core&quot;, version.ref = &quot;kotlinxCoroutinesCore&quot; }<br>logging-interceptor = { module = &quot;com.squareup.okhttp3:logging-interceptor&quot;, version.ref = &quot;loggingInterceptor&quot; }<br>retrofit = { module = &quot;com.squareup.retrofit2:retrofit&quot;, version.ref = &quot;retrofit&quot; }<br>room-compiler = { module = &quot;androidx.room:room-compiler&quot;, version.ref = &quot;roomCompiler&quot; }<br><br>[plugins]<br>android-application = { id = &quot;com.android.application&quot;, version.ref = &quot;agp&quot; }<br>kotlin-android = { id = &quot;org.jetbrains.kotlin.android&quot;, version.ref = &quot;kotlin&quot; }<br>kotlin-compose = { id = &quot;org.jetbrains.kotlin.plugin.compose&quot;, version.ref = &quot;kotlin&quot; }<br>ksp = { id = &quot;com.google.devtools.ksp&quot;, version = &quot;2.0.21-1.0.25&quot; }</pre><p><strong>Avoiding Typical Duplicate Class Error</strong></p><pre>Duplicate class com.example.SomeClass found in modules<br>jetified-libraryA-1.2.0-runtime.jar (libraryA-1.2.0.jar)<br>jetified-libraryB-1.3.0-runtime.jar (libraryB-1.3.0.jar)</pre><pre>//gradle.properties<br>android.useAndroidX=true<br>android.enableJetifier=true</pre><p><strong>Add internet permission in advance<br></strong>Ahh!! The most common problem each of us has encountered is missing internet permissions, and when we start executing the api, we get a series of network-related errors. Better add it in advance….</p><pre>    &lt;uses-permission android:name=&quot;android.permission.INTERNET&quot; /&gt;</pre><p><strong>Create an application class and add it to the manifest<br></strong>Do this in advance to avoid any “Unable to instantiate application” or “Class not found” errors.</p><p><strong>Setup DI folder<br></strong>Define the folder structure, including folders such as module, component (using Dagger), and files for custom annotations if needed (optional). Initialize and test DI to ensure the application is working properly.</p><p><strong>Build Utilities folder for commonly used actions</strong></p><p>This helps with code reusability and extensibility. Also, leverage extension functions to extend existing classes.</p><p><strong>Build folders in sequence: data, viewmodels, and UI.</strong></p><p>This ensures that a major portion of the work is completed within the provided time frame.</p><p><strong>Github Uploading Guide</strong></p><p>1&gt; Make sure to commit code after each incremental step (e.g., complete setup di)</p><p>2&gt; Keep the commit message concise and crisp. Avoid sentences and use phrases.</p><p>3&gt; Mention what is done rather than how it is done</p><p>4&gt; Try to write a commit message in the format …</p><p>If commit is applied, it will <strong>[commit message].</strong></p><p>Ex:- setup DI, configure data layer, render profile page</p><p>If commit is applied, it will <strong>[configure data layer].</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0483b3da3ecb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scope Functions Through the Lens of an Android Developer]]></title>
            <link>https://medium.com/@badjatyatoshika91311/scope-functions-through-the-lens-of-an-android-developer-849fc18059bb?source=rss-9c008139d933------2</link>
            <guid isPermaLink="false">https://medium.com/p/849fc18059bb</guid>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[kotlin-scope-functions]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Toshika Badjatya]]></dc:creator>
            <pubDate>Sun, 21 Sep 2025 12:23:17 GMT</pubDate>
            <atom:updated>2025-09-21T12:39:04.111Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5_U_pKS7yeWgKJYttROHkQ.png" /></figure><p><strong>What are the different scope functions?</strong></p><p>Probably the most asked interview question and a scenario we encounter almost daily as Android developers.</p><p><em>By definition, Scoped functions are functions that execute a block of code within the context of an object.</em></p><p>Done with the definitions now, let&#39;s understand it practically with real use cases.</p><p><strong>Let<br></strong>Achieve null safety and simplify expression</p><pre>data class User(val name:String, val age:Int)<br><br>fun main(){<br>  val myUser=User(&quot;Henry&quot;,10)<br>  val name=myUser.let{<br>    it.name<br>  }<br>}</pre><p><strong>Java Equivalent of the setup</strong></p><pre>User myUser= new User(&quot;Henry&quot;,10);<br>String name=myUser.getName();</pre><p><strong>Understanding what happens under the hood</strong></p><pre>fun User.let(callback: (User) -&gt; String): String{<br>    return callback.invoke(this)<br>}</pre><p><strong>Key Points</strong></p><ul><li>Extension function to any object.</li><li>Scope input: callback with the current class instance as an input and variable output.</li><li>Scope output: return value of the callback.</li></ul><p><strong>Apply<br></strong>Apply additional properties to an object and return the updated object<br>Example: Adding multiple extras to the intent</p><pre>val intent = Intent(Intent.ACTION_PICK).apply {<br>    type = &quot;image/*&quot;<br>    action = Intent.ACTION_PICK<br>}</pre><p><strong>Java Equivalent of the setup</strong></p><pre>Intent intent = new Intent(Intent.ACTION_PICK);<br>intent.setType(&quot;image/*&quot;);<br>intent.setAction(Intent.ACTION_PICK);</pre><p><strong>Understanding what happens under the hood</strong></p><pre>fun Intent.apply(callback: Intent.() -&gt; Unit): T {<br>    this.callback.invoke()<br>    return this<br>}</pre><p><strong>Key Points</strong></p><ul><li>Scope input: extension function of the current class.</li><li>Scope output: return the same object.</li><li>Access the current instance within the callback using this keyword (due to extension function usage).</li><li>Usability: modify the property of the object.</li></ul><p><strong>Also<br></strong>Perform a logging or debugging operation on an object</p><pre> val user= User(&quot;alpha&quot;,2)<br> user.also {<br>    Log.e(&quot;sample&quot;,&quot;test is $it&quot;)<br> }</pre><p><strong>Java Equivalent of the setup</strong></p><pre> User user = new User(&quot;alpha&quot;, 2);<br> Log.e(&quot;sample&quot;, &quot;test is &quot; + user);</pre><p><strong>Understanding what happens under the hood</strong></p><pre>fun User.also(callback: (User) -&gt; Unit): User{<br>    callback.invoke(this)<br>    return this<br>}</pre><p><strong>Key Points</strong></p><ul><li>Scope input: callback with the current class instance as an input and unit output.</li><li>Scope output: return the same object.</li><li>Access the current instance within the callback using the it keyword.</li></ul><p><strong>With</strong></p><p>Working with an existing object to modify its property</p><pre>val user= User(&quot;alpha&quot;,2)<br>val name= with(user){<br>     this.name<br> }</pre><p><strong>Java Equivalent of the setup</strong></p><pre>User user = new User(&quot;alpha&quot;, 2);<br>String name = user.getName();</pre><p><strong>Understanding what happens under the hood</strong></p><pre>with(receiver: User, callback: User.() -&gt; String): String{<br>    return receiver.callback()<br>}</pre><p><strong>Key Points</strong></p><ul><li>Unlike others, instead of using a callback, it uses an object as an input<br>along with the object extension function.</li><li>Scope output: return value of the callback.</li><li>Access the current instance within the callback using this keyword (due to extension function usage).</li></ul><p><strong>Run<br></strong>Similar to the ‘with’ keyword, but used as an extension function of the current class</p><pre>val name= new User(&quot;alpha&quot;, 2).run{<br>     this.name<br> }</pre><p><strong>Understanding what happens under the hood</strong></p><pre> User.run(callback: User.() -&gt; String): String{<br>    return block()<br>}</pre><p><strong>Key Points</strong></p><ul><li>The only difference between with and run is that run can work well with nullable data types, but for the ‘with’ keyword, we need to perform an additional conditional check.</li></ul><pre>//let keyword<br>val name= user?.run{<br>     this.name<br> }<br><br>//with keyword<br>if(user!=null){<br>   val name= with(user){<br>     this.name<br> }<br>}<br><br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lXQelQ95pBTX1-Iz7CUTUg.png" /><figcaption>Tabular representation of scope function usage</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=849fc18059bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>