<?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 Pranav more on Medium]]></title>
        <description><![CDATA[Stories by Pranav more on Medium]]></description>
        <link>https://medium.com/@pranavmore?source=rss-c53c9c70483e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BpYr3DC86vjTL3zK_LhVEA.png</url>
            <title>Stories by Pranav more on Medium</title>
            <link>https://medium.com/@pranavmore?source=rss-c53c9c70483e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:28:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pranavmore/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Create Viral Instagram Reels With Claude]]></title>
            <link>https://medium.com/@pranavmore/how-to-create-viral-instagram-reels-with-claude-5915a92faa86?source=rss-c53c9c70483e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5915a92faa86</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[content-creation]]></category>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[ai-video-generator]]></category>
            <category><![CDATA[instagram-reels]]></category>
            <dc:creator><![CDATA[Pranav more]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 11:00:20 GMT</pubDate>
            <atom:updated>2026-11-13T11:00:20.067Z</atom:updated>
            <content:encoded><![CDATA[<h4>Type a topic, approve the script, pick a style. The AI Reels workflow I built after doing it by hand one too many times.</h4><figure><img alt="Cover: How to Create Viral Instagram Reels With Claude, with three phone frames from real WhatToUpload renders" src="https://cdn-images-1.medium.com/max/1024/1*Z-W2YVdwX0FiiOLljU6M0Q.png" /><figcaption>Frames from real renders: Kinetic type, Ink stickman and Diagram explainer.</figcaption></figure><p>Ok, confession first.</p><p>I kept seeing those clean explainer Reels people make with Claude. Big type that lands on every word, a stick figure that keeps its hands, a graph that draws itself while the voice talks.</p><p>And I kept thinking: I can do that.</p><p>I could. It was just painfully slow lol.</p><h3>Why I built a way to make Instagram Reels with Claude.</h3><p>The “made with Claude” video trick is real. Claude can’t output a video file, but it can write a web page where every frame is a function of time. Then you capture that page frame by frame and hand it to ffmpeg.</p><p>The catch is everything around it. Research the topic. Write the script. Get a voiceover. Time the captions. Find music. Render. Notice the caption overlaps a shape. Render again.</p><p>In our own measurements, an agentic Claude Code session costs about $7 to $13 in API tokens for one 60 second video, and most of that goes on rendering and reviewing, not writing.</p><p>Fine for one video. Not fine if you want to post every day.</p><p>So I built that whole loop into WhatToUpload.</p><h3>How WhatToUpload turns Claude into an AI Reels generator</h3><p>You type one sentence. That’s the input.</p><p><strong>Claude researches when the topic is news.</strong> I asked “What did Apple announce this week?” and it pulled web sources first, listed all of them, and even flagged where two sources disagreed.</p><p><strong>You get a script by scene.</strong> Hook first, then numbered scenes, with a word count and a voiced length. You approve it, regenerate it, or ask for a change in plain words (“make it punchier”, “use only official sources”). You get up to 8 drafts per video.</p><figure><img alt="The WhatToUpload Video Studio: a researched script draft about Apple’s November launches, with the hook, ten numbered scenes and eight listed sources" src="https://cdn-images-1.medium.com/max/1024/1*sB1mYjJhvW9H2a1O0nY41A.png" /><figcaption>A real draft from my account: the hook, the scenes and every source it used.</figcaption></figure><p><strong>You pick a style.</strong> There are 87 right now: kinetic type, systems explained with real logos, story reels where the characters stay the same from the first frame to the last, and art styles like painterly, noir and anime.</p><figure><img alt="The Pick a style modal showing 87 styles with filters for Faceless, Explainer, Data, Story and Art" src="https://cdn-images-1.medium.com/max/1024/1*RhAVH0Q8dl3vhaR7BmzJqw.png" /><figcaption>The style picker. Every preview is a real render.</figcaption></figure><p><strong>Then it renders.</strong> Voiceover by ElevenLabs, captions timed to the voice’s own word timings, music and sound effects. Vertical 9:16, in a few minutes (about 3 for a 30 second explainer).</p><p>The visuals are drawn as code from Claude’s storyboard, not dreamed up by a video model. So the type stays crisp and a chart is plotted from the actual numbers in the script.</p><figure><img alt="Six frames from real WhatToUpload renders: Kinetic type, Systems explained, Ink stickman, Diagram explainer, Avatar explainer and Case file" src="https://cdn-images-1.medium.com/max/1024/1*DyC9CcHl4f8yUem8TaRW_g.png" /><figcaption>Frames pulled straight from sample renders on the site, unedited.</figcaption></figure><h3>How to make a viral Reel with Claude in 5 steps</h3><p>Nobody can promise “viral”. Anyone who does is selling something lol.</p><p>What you can do is stack the odds. These five steps work with any tool, mine included.</p><figure><img alt="Diagram of the five steps: one idea and one hook, Claude writes the script, pick a style, voice captions and music, post on a rhythm" src="https://cdn-images-1.medium.com/max/1024/1*333ezMfQfrKvsE7HuuTraw.png" /><figcaption>The whole method on one page.</figcaption></figure><h4>1. One idea, and a hook in the first 1 to 2 seconds</h4><p>One Reel, one idea. If you need “and also”, that’s a second Reel.</p><p>Put the payoff on screen at frame zero. “$440 million gone in 45 minutes” beats “In this video, we’ll look at…” every single time.</p><p>Say it out loud in the first line too, so the spoken hook and the on-screen hook match.</p><h4>2. Let Claude write the script (and check the facts)</h4><p>Ask for the hook first, then one beat per scene. Short sentences read better as captions.</p><p>If the topic is news, research comes before writing. Ask for sources, then actually open one or two. A Reel that’s wrong gets corrected in the comments, and not the fun kind of engagement.</p><h4>3. Pick one style per niche and keep it</h4><p>Your grid is a promise of what the next Reel looks like. Finance page? Charts. History page? Stick figures or a case file. Tech? Systems explained.</p><p>Same look on episode one and episode fifty, and people start recognising you before they read a word.</p><h4>4. Voice, captions, music, and keep it 20 to 45 seconds</h4><p>Captions are not optional. Many people watch with the sound off, so the words on screen have to tell the story on their own.</p><p>20 to 45 seconds is the sweet spot for most explainers: long enough to say one thing well, short enough to rewatch.</p><h4>5. Post consistently, in one niche</h4><p>The algorithm can’t figure out who to show you to if Monday is crypto and Tuesday is cats.</p><p>Pick a niche, pick a cadence you can actually keep, and schedule ahead so posting doesn’t depend on your mood that day.</p><h3>From finished video to posted Reel</h3><p>When the render’s done you get the video, a post caption and hashtags, and a download button.</p><figure><img alt="A finished 3D cartoon video, The $14 Dinner, with its post caption, hashtags and the Post it panel" src="https://cdn-images-1.medium.com/max/1024/1*6PYDeDt_9MByU9tF1zcvzw.png" /><figcaption>A finished story reel from my account, with caption and hashtags written for it.</figcaption></figure><p>Posting and scheduling to YouTube works today: pick the channel, set the visibility, post now or pick a time.</p><p>Instagram and TikTok connections are coming once the platforms approve the app. Until then, download the MP4 and post it from your phone. Takes ten seconds, ik ik.</p><figure><img alt="The scheduling panel with YouTube selected, Instagram and TikTok marked not set up yet, and a date and time picker" src="https://cdn-images-1.medium.com/max/1024/1*3gQgIeiCE1dZ1hOvsSxFDw.png" /><figcaption>Scheduling to YouTube. Instagram and TikTok show as not set up yet, because they aren’t.</figcaption></figure><h3>The DIY route: making Reels with Claude Code yourself</h3><p>You can absolutely do all of this yourself, and honestly it’s a fun weekend.</p><p>You need Claude Code, Chrome, Node with playwright-core, ffmpeg, and ideally a text to speech API that returns word timings so captions land on the right word.</p><p>Then Claude writes a page where render(t) draws exactly what&#39;s on screen at time t. Playwright steps through the frames, ffmpeg encodes them, and you mix in the voice and music.</p><p>It’s powerful. You control every pixel.</p><p>It’s also slow. Every render you review is another round trip, and that’s where the time and the tokens go. If you love tinkering, go for it. If you want to post every day, that’s the bit I automated.</p><h3>FAQs about making Reels with AI</h3><h4>Can Claude make videos?</h4><p>Not directly. Claude is a language model, so it doesn’t output video pixels. It writes the script, the storyboard and the code, and a renderer turns that into frames. That’s how WhatToUpload works too.</p><h4>How do I make faceless Instagram Reels with AI?</h4><p>Pick a faceless style (79 of the 87 styles are faceless), let a voiceover carry the story, and burn the captions in. No camera, no face, no presenter.</p><h4>How long should a Reel be?</h4><p>For explainers and story Reels, aim for 20 to 45 seconds. Shorter if the idea is a single fact; longer only if every second earns its place.</p><h4>Can I post straight to Instagram from WhatToUpload?</h4><p>Not yet. YouTube posting and scheduling work today. Instagram and TikTok are coming once the platforms approve the app. For now, download the MP4 and post it.</p><h4>Is there a free AI Reels generator?</h4><p>WhatToUpload is paid only, from $19 a month on the launch price (regular $25) with no trial. The sample videos on the homepage are untouched renders, so you can judge the output before paying.</p><h4>Is short-form video still worth it?</h4><p>YouTube says Shorts now average 200 billion daily views (<a href="https://blog.youtube/inside-youtube/the-future-of-youtube-2026/">Neal Mohan’s 2026 letter</a>, 21 January 2026). The same 9:16 file works as a Short, a Reel and a TikTok, so one video can travel.</p><h3>Try it on your next idea</h3><p>If you’ve got a topic sitting in your notes app, that’s your first Reel.</p><p>Type it into WhatToUpload, approve the script, pick a style, and see what comes out: <a href="https://www.whattoupload.com/?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=viral-reels-with-claude">whattoupload.com</a></p><p>And if you build it yourself with Claude Code instead, the five steps above still apply.</p><p>WhatToUpload is an independent product built on Claude. It isn’t affiliated with or endorsed by Anthropic.</p><p>Lemme know your thoughts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5915a92faa86" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Make a Real Estate Video From Your Listing Photos]]></title>
            <link>https://medium.com/@pranavmore/how-to-make-a-real-estate-video-from-your-listing-photos-81d4c95bcd3d?source=rss-c53c9c70483e------2</link>
            <guid isPermaLink="false">https://medium.com/p/81d4c95bcd3d</guid>
            <category><![CDATA[realtor]]></category>
            <category><![CDATA[real-estate-marketing]]></category>
            <category><![CDATA[real-estate]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[video-marketing]]></category>
            <dc:creator><![CDATA[Pranav more]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 15:18:36 GMT</pubDate>
            <atom:updated>2026-11-11T15:18:36.322Z</atom:updated>
            <content:encoded><![CDATA[<h4>The step by step version I wish I had: no camera, no shoot, just the photos you already paid for.</h4><figure><img alt="Cover: &quot;How to make a real estate video from your listing photos&quot; next to a phone showing a vertical listing video frame" src="https://cdn-images-1.medium.com/max/1024/1*8o4m9JcnYcr8Mkn6ixTQpg.png" /></figure><p>Most listings already come with a full set of professional photos. They end up in an MLS gallery that people swipe through, while Instagram and TikTok quietly reward anyone who posts a video.</p><h3>Why I built this</h3><p>I’m Pranav, and I build small software products. When I started looking at how homes get marketed online, I kept seeing the same thing: a beautiful listing, a full set of professional photos, and no video.</p><p>It wasn’t that agents didn’t want one. A video meant booking a videographer for a few hundred dollars, or losing an evening to an editing app, and doing that for every single listing just doesn’t happen.</p><p>But everything a good listing video needs was already sitting in that photo gallery: the shot to open on, the order to walk through the house, the rooms worth lingering on. It only needed someone to do the editing.</p><p>That’s why I built Property Video Generator: so the photos you’ve already paid for can become a video without a shoot and without an editor. Below is the method behind it, step by step. It works with any tool, mine included.</p><h3>Why a real estate listing video beats a photo carousel</h3><p>Feeds push video. A Reel, a TikTok or a YouTube Short can reach people who don’t follow you yet; a carousel mostly reaches the ones who do.</p><p>A real estate listing video also does something photos can’t: it walks the buyer through the house in an order. Outside, then the door, then the kitchen. That order is the story.</p><p>The catch used to be cost. You either booked a videographer or spent an evening in an editing app. Neither happens for every listing.</p><h3>Real estate slideshow maker or real estate video?</h3><p>This is the most common thing people search before they make one (it’s the top query that finds my site), so let’s sort it out first.</p><p>A <strong>slideshow</strong> plays your photos in upload order, the same two or three seconds each, maybe with a zoom. It’s fine. It also looks like every other slideshow, and buyers scroll past.</p><p>A <strong>real estate video</strong> makes editing decisions. It opens on the best shot, skips the third photo of the same bedroom, holds the kitchen longer than the laundry room and cuts on the music. Same photos, very different result.</p><p>Everything below is about making the second kind.</p><h3>How to make a real estate video from photos in 5 steps</h3><figure><img alt="A five step diagram: pick 10 to 25 photos, open on the best shot, walk the house in order, add voice, captions and music, export 9:16 and post" src="https://cdn-images-1.medium.com/max/1024/1*0SAxZKknt0LgV6mXt43_6w.png" /></figure><h4>1. Pick 10 to 25 photos</h4><p>Send the whole shoot, then cut. Drop near duplicates, dark frames and anything blurry. A 45 second video doesn’t need 40 photos.</p><h4>2. Open on the best shot (your hook)</h4><p>You get roughly two seconds before someone scrolls. Don’t spend them on the front door. Lead with the pool, the view, the kitchen island: whatever made you say “oh nice” when the photos came in.</p><h4>3. Walk the house in order</h4><p>Outside, entry, living, kitchen, bedrooms, the yard. Give the rooms that sell the house 4 to 5 seconds and the small ones under 2. Even timing is exactly what makes a video feel like a slideshow.</p><h4>4. Add voice, captions and music</h4><p>Plenty of people watch with the sound off, so captions have to tell the story on their own. Keep the narration short: about 55 to 60 words for a 30 second video. Pick music that matches the house; a driving beat on a quiet $3M estate feels wrong.</p><h4>5. Export vertical 9:16 and post</h4><p>Vertical 9:16 for Reels, TikTok and Shorts. Aim for 30 to 45 seconds. Keep text away from the bottom and right edges, where the app puts its buttons. Post it from your own account the day the listing goes live, and use the square or widescreen version for email, YouTube and your website.</p><h3>Making one with a property video maker (what I actually did)</h3><p>This is where <a href="https://www.propertyvideogenerator.com/?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=how-to-make-real-estate-video">Property Video Generator</a> comes in: it does those five steps for you, so nobody has to sit in an editor. Here is a real run, using a demo listing (licensed stock photos of a real house; the address and price are made up).</p><p><strong>Upload the photos.</strong> I dropped in 23 photos and typed the address. Price, beds, baths and a short description are optional, but the narration is written from them, so more detail means a better script. You can add up to 40 photos, or paste a Redfin, Realtor.com or brokerage listing link to pull them in (Zillow links don’t work).</p><p><strong>Pick the look.</strong> Three vibes (Calm luxury, Bright family, Bold modern), a pacing setting, a music mood, and a narrator: 10 voices, each speaking 10 languages. I went with Bright family and the default voice.</p><figure><img alt="The upload screen with 23 listing photos and Smart order on, next to the Look and pace and Sound options" src="https://cdn-images-1.medium.com/max/1024/1*s5x2e7vsxNUBIGEcCOF4qQ.jpeg" /><figcaption>Left: 23 photos in, Smart order picks the hook and the walkthrough. Right: vibe, pacing and music.</figcaption></figure><p><strong>Press create and wait.</strong> The progress screen shows each real stage: analysing photos, planning the story, camera moves, voice and music, then rendering every cut. Mine was ready about 17 minutes after I pressed create, a minute or so of that waiting in the queue. You can close the tab; it emails you.</p><figure><img alt="The render progress screen: analysing photos, planning the story and camera moves done, rendering every cut in progress" src="https://cdn-images-1.medium.com/max/1024/1*3IL8kLzq4MELmm1z5TX5Aw.jpeg" /><figcaption>The progress screen, a minute before it finished.</figcaption></figure><p><strong>Check the film.</strong> It picked 16 shots for a 56 second film and opened on the pool with the line “A pool that mirrors the manor.” I would not have opened there myself, and it was the right call. You get five cuts from the same edit: vertical 9:16, portrait 4:5, square 1:1, widescreen 16:9 and an unbranded MLS cut.</p><figure><img alt="The finished film page with the vertical cut playing, the hook line and buttons to download, edit and share" src="https://cdn-images-1.medium.com/max/1024/1*WWQkwB9j8OZt9B7_HIXptA.jpeg" /><figcaption>The finished film page. It also writes post copy for each platform.</figcaption></figure><figure><img alt="Four frames from the vertical cut: the front of the house with the address and price, the kitchen, the sunroom and the marble bathtub, each with word by word captions" src="https://cdn-images-1.medium.com/max/1024/1*32ie1zdW5pTdpSwZsCCmVg.jpeg" /><figcaption>Frames from the vertical cut. The camera moves are built from depth in each still photo.</figcaption></figure><p>If something’s off, you change it: drag shots, rewrite a line, or tell the AI Director in plain words like “make it under 30 seconds”. Edits don’t use up another listing.</p><h3>Real estate video pricing: your four options compared</h3><figure><img alt="Comparison of filming yourself, hiring a videographer, editing apps and AI photo to video tools by cost, time, what you need and what each is best for" src="https://cdn-images-1.medium.com/max/1024/1*IzCfB2uI62vTNf8ziSZejQ.png" /></figure><p><strong>Film it yourself.</strong> Cheapest if you already own a phone, and the only option that puts <em>you</em> on camera. It costs a shoot and an evening of editing, and handheld footage shows it.</p><p><strong>Hire a videographer.</strong> Real motion, drone footage, a pro edit. Published US price lists start around $195 for a short walkthrough, and $300 to $1,000 is typical; delivery is usually next day to three business days after the shoot. Worth it for a flagship listing.</p><p><strong>Editing apps (Canva, CapCut, iMovie).</strong> Free tiers exist and you control everything. You also do everything: every slide, every caption, every cut, by hand.</p><p><strong>AI photo to video tools.</strong> Fast and cheap per listing: from $4.90 (Tourly’s published price for a reel) to $9.75 a listing (Property Video Generator on Starter; its free plan covers 2 listings a month at 720p with a watermark). The honest limit: they work from stills, so there’s no drone footage and no real walkthrough motion.</p><p>My take: hire the videographer for the one listing that needs drone and real motion, and use photos for the rest. Nothing stops you doing both.</p><h3>FAQs about real estate videos</h3><h4>How long should a real estate video be?</h4><p>For Reels, TikTok and Shorts, 30 to 45 seconds is a good target for a listing. A coming soon teaser can be 8 to 12 seconds; a luxury tour on YouTube can run longer.</p><h4>Do AI real estate videos look fake?</h4><p>They can. Tools that generate new video can add windows or bend a staircase. Moves built from the actual photo hold up much better. Either way, watch every shot before you post. In my test one vertical shot had an odd strip at the top of the sky, and swapping the photo or regenerating that shot is done from the editor.</p><h4>Can I make real estate videos without being on camera?</h4><p>Yes. A video made from listing photos with narration and captions never needs your face. If you want your voice, record your own narration or (on some plans) clone your voice with consent.</p><h4>Is there a free real estate slideshow maker?</h4><p>Canva, CapCut and iMovie all have free options for a basic slideshow. Property Video Generator gives you 2 listings a month free, no card, with a small watermark and 720p.</p><h4>What are the MLS video requirements?</h4><p>They vary by MLS, but most want an unbranded video: no agent name, logo, phone or contact details. That’s why the MLS cut leaves all branding off. Check your own MLS rules before you upload.</p><h3>Try it on your next listing</h3><p>If you have a listing going live this week, the photos are already sitting in your downloads folder. Make the video from those.</p><p>You can <a href="https://www.propertyvideogenerator.com/?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=how-to-make-real-estate-video">make your first two films free at propertyvideogenerator.com</a>, no card needed. And if you use another tool, the five steps above still apply.</p><p>Lemme know how your first one turns out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81d4c95bcd3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Made a Desktop Pet for People Who Miss Their Cat or Dog]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@pranavmore/i-made-a-desktop-pet-for-people-who-miss-their-cat-or-dog-2a2f206fcfc3?source=rss-c53c9c70483e------2"><img src="https://cdn-images-1.medium.com/max/1672/1*0y4gmuA5s0a_W0cGCwXpeQ.png" width="1672"></a></p><p class="medium-feed-snippet">A little companion for your Mac, inspired by something I wanted for myself.</p><p class="medium-feed-link"><a href="https://medium.com/@pranavmore/i-made-a-desktop-pet-for-people-who-miss-their-cat-or-dog-2a2f206fcfc3?source=rss-c53c9c70483e------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@pranavmore/i-made-a-desktop-pet-for-people-who-miss-their-cat-or-dog-2a2f206fcfc3?source=rss-c53c9c70483e------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a2f206fcfc3</guid>
            <category><![CDATA[desktop-pet]]></category>
            <category><![CDATA[pets]]></category>
            <category><![CDATA[pet-gifts]]></category>
            <category><![CDATA[best-mac-app]]></category>
            <dc:creator><![CDATA[Pranav more]]></dc:creator>
            <pubDate>Thu, 29 Oct 2026 17:31:22 GMT</pubDate>
            <atom:updated>2026-10-29T17:31:22.937Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Don’t Launch a Website Until These Boring Things Are Done]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@pranavmore/i-dont-launch-a-website-until-these-boring-things-are-done-fb03491a17f7?source=rss-c53c9c70483e------2"><img src="https://cdn-images-1.medium.com/max/1672/1*9231z_vb7sYBiSn-3dsULA.png" width="1672"></a></p><p class="medium-feed-snippet">The boring things I set up before I start asking why nobody is visiting my new project.</p><p class="medium-feed-link"><a href="https://medium.com/@pranavmore/i-dont-launch-a-website-until-these-boring-things-are-done-fb03491a17f7?source=rss-c53c9c70483e------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@pranavmore/i-dont-launch-a-website-until-these-boring-things-are-done-fb03491a17f7?source=rss-c53c9c70483e------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb03491a17f7</guid>
            <category><![CDATA[website-traffic-tips]]></category>
            <category><![CDATA[seo-tips]]></category>
            <category><![CDATA[google-search-console]]></category>
            <category><![CDATA[utm]]></category>
            <dc:creator><![CDATA[Pranav more]]></dc:creator>
            <pubDate>Sun, 20 Sep 2026 10:03:36 GMT</pubDate>
            <atom:updated>2026-09-20T10:03:36.252Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Your AI-Built Website Is Probably Broken and You Don’t Know It]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@pranavmore/your-ai-built-website-is-probably-broken-and-you-dont-know-it-93f758e96089?source=rss-c53c9c70483e------2"><img src="https://cdn-images-1.medium.com/max/1672/1*IeQR0pOFfQUJ_xQ538IqEw.png" width="1672"></a></p><p class="medium-feed-snippet">Claude, ChatGPT, Grok, Gemini or any open source model or Lovable, Bolt and v0 can ship a beautiful site in minutes. The scary part is&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@pranavmore/your-ai-built-website-is-probably-broken-and-you-dont-know-it-93f758e96089?source=rss-c53c9c70483e------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@pranavmore/your-ai-built-website-is-probably-broken-and-you-dont-know-it-93f758e96089?source=rss-c53c9c70483e------2</link>
            <guid isPermaLink="false">https://medium.com/p/93f758e96089</guid>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[bug-fixes]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[seo-tips]]></category>
            <dc:creator><![CDATA[Pranav more]]></dc:creator>
            <pubDate>Sat, 19 Sep 2026 19:02:47 GMT</pubDate>
            <atom:updated>2026-09-19T19:02:47.807Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I built a tiny photo aapp for myself and strangers started paying me]]></title>
            <link>https://medium.com/@pranavmore/i-built-a-tiny-photo-aapp-for-myself-and-strangers-started-paying-me-87728ddcffc9?source=rss-c53c9c70483e------2</link>
            <guid isPermaLink="false">https://medium.com/p/87728ddcffc9</guid>
            <category><![CDATA[gemini]]></category>
            <category><![CDATA[photography]]></category>
            <category><![CDATA[claude-code]]></category>
            <category><![CDATA[photo-editing]]></category>
            <dc:creator><![CDATA[Pranav more]]></dc:creator>
            <pubDate>Thu, 06 Aug 2026 17:53:36 GMT</pubDate>
            <atom:updated>2026-08-06T17:53:36.533Z</atom:updated>
            <content:encoded><![CDATA[<p>How a small photography side project, basic SEO, and a surprisingly good domain brought real users to AddGrains.</p><h4>I want to start by making one thing clear:</h4><p>AddGrains is not making a huge amount of money.</p><p>This is not one of those stories where a weekend project suddenly became a $10,000-per-month business. So dont get excited lol 😅.</p><p>The amounts are small.<br>Some people have paid me $5. Some have paid me $10 through Buy Me a Coffee.<br>But the interesting part is that I never asked them to pay to unlock anything.<br><strong>The tool is free.</strong></p><p>People are voluntarily paying because they used it, loved it, and wanted to support the person who created it.<br>For a small project that I originally built for myself and almost forgot about, that means a lot.<br>Those few dollars keep me going.</p><h4>It Started With My Photography Hobby</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ddVQ-eNYBT1VHj2nUes0AQ.png" /></figure><p>Photography has always been one of my hobbies.<br>I take a lot of photos, edit them, and regularly post them on my Instagram stories.</p><p>One effect I particularly like is film grain.</p><p>Adding grain can make an ordinary digital photo feel warmer, more textured, and slightly imperfect. It can give a photo that film-like character that clean digital images sometimes lack.</p><p>Whenever I wanted to add grain to a photo, I had to open a larger editing application, find the correct effect, adjust multiple settings, and export the image.<br>It wasn’t an enormous problem. (for me)<br>It was just mildly annoying. (because I hated opening snapseed or lightroom apps)<br>And many useful products begin with exactly that kind of annoyance.</p><p>Sooooooo I thought……</p><p>&gt; Why not create a simple tool where I can upload a photo, add grain, adjust it, and download the result?<br>I wasn’t conducting market research.<br>I wasn’t trying to identify a startup opportunity.<br>I just wanted a tool that would make my own photography workflow easier.</p><p>That became <strong>AddGrains</strong>.</p><h4>I Built It Entirely With Claude and Gemini CLI</h4><p>Another interesting part of this project is how it was built.</p><p>AddGrains was created entirely using Claude code and Gemini CLI as my development tools. Also I did not write single piece of code by hand 😬 ik ik</p><p>There was no large engineering team.<br>It was just me, an idea based on my own photography habits, and vibe coding.<br>This is what I find most exciting about building products today.<br>An idea no longer has to remain in your notes for months. (which I do have lots n lots of them)<br>You can think of something useful or stupid or fun, just go ahead and built it man… I mean really whats stopping you?<br>The barrier between having an idea and publishing a real product is becoming much smaller.</p><h4>The Product Was Intentionally Simple</h4><p>I did not want <strong>AddGrains</strong> to become another complicated photo editor.<br>There are already many powerful editing applications available. Competing with them feature by feature would not make sense.<br>I wanted <strong>AddGrains</strong> to do one specific job well.</p><p>You upload an image.<br>then adjust the grain -&gt; preview the result -&gt; download the edited photo.<br>That is the product.<br>No mandatory account.<br>No complicated dashboard.<br>You don’t need to understand professional editing terminology.<br>You don’t need to install anything.<br>You simply open the website and use the tool.<br>The photos can be processed directly in the browser, which also keeps the experience fast and private.</p><p>It was created for the same reason I wanted it myself: sometimes you do not need a complete editing suite. You just want to add grain to a photo.</p><h4>Then I Published It and Forgot About It</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6A-zSPAafLUQTF8NC2HNOA.png" /><figcaption>Seo for addgrains</figcaption></figure><p>Once the tool was working, I published it on AddGrains.com.<br>I did some basic SEO work. (with the help of claude code ofcourse)<br>Nothing extremely advanced.<br>I made sure the pages had understandable titles, descriptions, keywords, headings, and content that explained exactly what the tool did.<br>I targeted straightforward searches around adding grain, noise, film texture, and vintage effects to photos.<br><strong>Then I moved on to other things.<br></strong>I wasn’t constantly checking the analytics. (But I added analytics)<br>I wasn’t posting about it every day.<br>I had built the tool I wanted, made it publicly available, and more or less forgot about it.<br>After some time, I decided to check the analytics.<br>That was when I realised people were actually finding it.</p><h4>Then Someone Paid Me $5</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CcFItdrJSCbszzQ1fb3B2A.png" /><figcaption>Domain ka kharcha nikal gaya</figcaption></figure><p>I had placed a Buy Me a Coffee option on the website.<br>The entire tool was still free. No locked export button. No paid resolution.<br>No watermark that users had to pay to remove.<br><br>Then someone paid me $5.<br>Later, someone else paid $10.<br>Then a few more people contributed.<br>Again, this is not a big amount of money.<br>It is not enough to call AddGrains a major business.<br>But the amount is not the important part.<br>What matters is that these people had no obligation to pay.<br>They could use the product, download their image, close the website, and never return.<br>Instead, they chose to support it because they loved what I had built.</p><p><em>That feeling is difficult to describe.</em></p><p>A stranger somewhere in the world used a small tool I had created for my own Instagram photos and thought:</p><p>This was useful. I want to thank the person who made it.<br>That $5 means more than the number suggests.<br>It tells me that the product created genuine value.</p><h4>Build things you personally want</h4><p>I love this book — rework by (Book by David Heinemeier Hansson and Jason Fried)</p><p>There is a chapter in that<br>- Scratch your own itch.</p><p>There ^ that was my motivation.</p><p>The reason for writing this article is: Many of my friends And random people on Twitter I noticed a pattern, people just talk about things, and they don’t build the product they want, just because it will not be that big, and they won’t get the dopamine hit of many users using their product or decent revenue.</p><p>I mean, you can create it for fun, right?</p><p>You don’t need to be an expert at anything. Just have a landing page ready, do some basic SEO if you want to, do some basic marketing, go on Reddit, go on Twitter, talk about your product. And you will learn hell lot of things in these processes.</p><p>Nowadays, all I do is build stupid products for myself, and it’s really fun. Each time I learn something new. So dont think much just build and push.</p><blockquote>Build the Tool You Wish Existed</blockquote><p>Tool link: <a href="https://addgrains.com/">https://addgrains.com/</a><br>The three images in this article are created by claude design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gX9m5gozLcwl2FBhc8hHsg.png" /><figcaption>Not huge but keeps me going!!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87728ddcffc9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why/How I Created BulkAudit in few hours(bulkaudits.com)]]></title>
            <link>https://medium.com/@pranavmore/why-how-i-created-bulkaudit-in-few-hours-bulkaudits-com-1fdb818293af?source=rss-c53c9c70483e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fdb818293af</guid>
            <category><![CDATA[side-hustle]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[web-performance]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Pranav more]]></dc:creator>
            <pubDate>Sun, 04 Jan 2026 17:48:11 GMT</pubDate>
            <atom:updated>2026-01-04T17:48:11.431Z</atom:updated>
            <content:encoded><![CDATA[<h3>The problem I kept running into</h3><p><em>Before starting I would like to mention that I built this in just few hours using claude code and gemini pro, and while I am writing this I dont know if I will add any more features to it or keep it as is (depends on repsonse though)</em></p><p>I use PageSpeed Insights and Lighthouse a lot.<br> For SEO checks, performance reviews, competitor analysis, and even quick sanity checks before shipping a page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NK8AZmrjxv90A29ddVT3wg.png" /><figcaption>Bulk Audit landing page (might update)</figcaption></figure><p>The problem is simple but persistent:</p><p><strong>PageSpeed Insights audits only one URL at a time.</strong></p><p>That’s fine when you’re checking a single page.<br> But the moment you need to compare multiple pages, the workflow completely breaks down.</p><h3>What “one URL at a time” actually means in practice</h3><p>If you’ve ever tried to compare pages using PageSpeed Insights, you know the drill:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x8XbOPB9xelRG8nQV6fg4A.png" /><figcaption>Chrome Lighthouse for PageSpeed</figcaption></figure><ul><li>Open PageSpeed Insights</li><li>Paste Url#1</li><li>Wait for the report</li><li>Open a new tab</li><li>Paste URL #2</li><li>Repeat… again and again</li><li>Manually compare scores across tabs</li></ul><p><strong>Now imagine doing this for:</strong></p><ul><li>Multiple landing pages</li><li>Competitor pages</li><li>Blog posts</li><li>Category pages</li><li>SEO experiments</li></ul><p>What should be a <strong>quick comparison</strong> turns into a <strong>slow, repetitive task</strong>.</p><p>There’s no side-by-side view.<br> No sorting.<br> No quick way to see which page is actually the worst.</p><h3>Existing solutions didn’t fit the problem</h3><p>Yes, there <em>are</em> tools that do bulk audits.</p><p>But they usually fall into one of these categories:</p><h3>1. Enterprise SEO tools</h3><ul><li>Expensive</li><li>Heavy dashboards</li><li>Overkill when you just want Lighthouse scores</li><li>Often locked behind subscriptions or credits</li></ul><h3>2. CLI / scripts</h3><p>How non tech folks are supposed to do this???</p><ul><li>Requires setup</li><li>Not accessible to non-technical users</li><li>Not something you can quickly share with a teammate or client</li></ul><h3>3. DIY spreadsheets</h3><ul><li>Copy-paste scores manually</li><li>Error-prone</li><li>No automation</li></ul><p>There was a clear gap:</p><blockquote><strong><em>A simple, no-setup way to audit and compare multiple URLs using Lighthouse.</em></strong></blockquote><h3>What I actually wanted</h3><p>I didn’t want a crawler.<br> I didn’t want a full SEO suite.<br> I didn’t want another subscription.</p><p>I just wanted to:</p><ul><li>Paste multiple URLs</li><li>Run Lighthouse on all of them</li><li>Compare SEO, performance, and accessibility scores</li><li>Quickly see which pages need attention</li></ul><p>That’s it.</p><h3>That gap is why I built BulkAudit</h3><p><strong>BulkAudit</strong> does one thing well:</p><blockquote><em>It lets you run Lighthouse audits across multiple URLs at once and compare the results side-by-side.</em></blockquote><p>Under the hood, it uses the <strong>same PageSpeed Insights API</strong> everyone trusts — just without the one-URL limitation.</p><p>What you get:</p><ul><li>Multi-URL audits in one run</li><li>SEO, performance, accessibility, and best practices scores</li><li>A comparison view instead of tab-hopping</li><li>Clear top issues per page</li><li>No signup, no setup</li></ul><p>It’s intentionally simple.</p><h3>Why it’s free (for now)</h3><p>BulkAudit started as a tool I built for myself.</p><p>Making it free:</p><ul><li>Keeps the barrier low</li><li>Encourages feedback</li><li>Helps validate whether this problem resonates with others</li></ul><p>If it’s useful, great.<br> If not, at least the problem is solved for me.</p><h3>What BulkAudit is not</h3><p>This is important.</p><p>BulkAudit is <strong>not</strong>:</p><ul><li>A full site crawler</li><li>A replacement for enterprise SEO tools</li><li>A magic SEO fix</li></ul><p>It’s a <strong>comparison and decision tool</strong>.</p><p>It answers questions like:</p><ul><li>Which page is slower?</li><li>Which competitor page has worse SEO fundamentals?</li><li>Where should I focus first?</li></ul><h3>What’s next</h3><p>Right now, BulkAudit focuses on:</p><ul><li>Speed</li><li>Clarity</li><li>Minimal friction</li></ul><p>If people find it useful, there’s room to go deeper:</p><ul><li>Sitemap-based page discovery</li><li>Core Web Vitals comparisons</li><li>Better issue breakdowns</li><li>Historical comparisons</li></ul><p>But the core idea will stay the same:<br><strong>make Lighthouse comparisons simple.</strong></p><h3>Final thought</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y7cVeoGGkNkmIjDKV16nNQ.png" /><figcaption>Result</figcaption></figure><p>Sometimes the best tools come from small frustrations you hit repeatedly.</p><p>BulkAudit exists because:</p><ul><li>The problem was real</li><li>The solution didn’t exist in a simple form</li><li>And building it was faster than tolerating the workflow</li></ul><p>If you’ve ever been annoyed by auditing one URL at a time,<br>you’ll probably understand why this exists.</p><p>👉 <a href="https://www.bulkaudits.com/"><strong>https://www.bulkaudits.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fdb818293af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bridging the Gap: Communication Between React Native Apps and Web Applications]]></title>
            <link>https://medium.com/@pranavmore/bridging-the-gap-communication-between-react-native-apps-and-web-applications-26a6e06b978c?source=rss-c53c9c70483e------2</link>
            <guid isPermaLink="false">https://medium.com/p/26a6e06b978c</guid>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Pranav more]]></dc:creator>
            <pubDate>Tue, 13 May 2025 10:39:26 GMT</pubDate>
            <atom:updated>2025-05-13T14:07:42.441Z</atom:updated>
            <content:encoded><![CDATA[<p><em>AKA: “How I Stopped Worrying and Learned to Love the WebView”</em></p><p>While developing a dual-platform for <a href="https://datingai.pro/">DatingAI</a>, I faced a critical challenge: how to maintain feature parity between our web application and native mobile app without duplicating code. Our solution? Embedding our web application in a React Native wrapper using WebView.</p><p>The real challenge emerged when we needed the web app to trigger native functionality like Apple login and in-app purchases. After several frustrating late nights (and too much redbull), I discovered an elegant solution using the WebView’s postMessage API. This guide shares the exact implementation that saved our project and my sanity.</p><h3>Understanding the WebView Bridge Architecture</h3><p>When you embed a web application inside a React Native app using WebView, you essentially have two separate JavaScript environments:</p><ol><li><strong>React Native JavaScript Environment</strong>: Running in the native app context</li><li><strong>Web Application JavaScript Environment</strong>: Running inside the WebView</li></ol><p>These environments can’t directly access each other’s variables or functions due to security boundaries. Instead, they communicate through a message-passing mechanism provided by the WebView component.</p><p>Think of it as two people in separate rooms trying to communicate by passing notes under the door. They can’t see each other directly, but as long as they agree on a format for their notes, they can work together quite effectively.</p><h3>Setting Up the Communication Channel</h3><h4>The React Native Side</h4><p>In your React Native application, you’ll use the react-native-webview package to embed your web application. The key to enabling communication is setting up an event listener using the onMessage prop:</p><pre>// In your React Native component<br>import { WebView } from &#39;react-native-webview&#39;;<br><br>const MyWebViewComponent = ({ navigation }) =&gt; {<br>  const handleWebViewMessage = (event) =&gt; {<br>    try {<br>      const message = JSON.parse(event.nativeEvent.data);<br>      <br>      switch (message.action) {<br>        case &#39;SOME_LOGIN&#39;:<br>          if (!authSessionActive) handleAppleLogin();<br>          break;<br>        case &#39;OPEN_SUBSCRIPTION_PAGE&#39;:<br>          navigation.navigate(&quot;Subscription&quot;, {<br>            offeringIdentifier: message.offering,<br>            source: &quot;webview&quot;,<br>          });<br>          break;<br>        case &#39;LOGOUT&#39;:<br>          handleLogout();<br>          break;<br>        default:<br>          console.warn(&quot;Unknown message action: &quot;, message.action);<br>          break;<br>      }<br>    } catch (error) {<br>      console.error(&quot;Error handling message from WebView:&quot;, error);<br>    }<br>  };<br><br>  return (<br>    &lt;WebView<br>      source={{ uri: &#39;https://your-web-app.com&#39; }}<br>      onMessage={handleWebViewMessage}<br>      // other WebView props...<br>    /&gt;<br>  );<br>};</pre><p>In this code, we:</p><ol><li>Define a handler function handleWebViewMessage that parses incoming messages</li><li>Use a switch statement to handle different types of actions based on the action field</li><li>Execute relevant native functionality based on the message content</li></ol><h4>The Web Application Side</h4><p>In your web application, you need to detect whether it’s running inside a WebView and send messages accordingly:</p><pre>// In your web application<br>const sendMessageToNative = (messageObject) =&gt; {<br>  // Check if running in React Native WebView<br>  if (window.ReactNativeWebView) {<br>    window.ReactNativeWebView.postMessage(JSON.stringify(messageObject));<br>    return true;<br>  }<br>  return false; // Not running in WebView<br>};<br><br>// Example usage: Opening subscription page<br>const openNativeSubscription = () =&gt; {<br>  if (sendMessageToNative({<br>    action: &#39;DISPLAY_PAYWALL&#39;,<br>    offering: &#39;OFFERING&#39;,<br>  })) {<br>    // Message was sent to native app<br>    return; // Don&#39;t proceed with normal web flow<br>  }<br>  <br>  // Fallback for web-only execution<br>  // Navigate to web subscription page<br>  window.location.href = &#39;/subscription&#39;;<br>};</pre><p>The key aspects of the web implementation:</p><ol><li>We check for the existence of window.ReactNativeWebView to detect if we&#39;re running inside a React Native WebView</li><li>We use window.ReactNativeWebView.postMessage() to send a JSON string to the native application</li><li>We include an action identifier and any necessary payload data</li><li>We provide a fallback for when the application is running in a regular browser</li></ol><h3>Practical Use Cases and Implementation</h3><p>Let’s explore some real-world use cases for WebView bridge communication:</p><h4>1. Authentication Flows</h4><p>One of the most common uses for this bridge is handling authentication:</p><pre>// In your web app<br>const handleLoginRequest = () =&gt; {<br>  if (window.ReactNativeWebView) {<br>    window.ReactNativeWebView.postMessage(JSON.stringify({<br>      action: &#39;SOME_LOGIN&#39;<br>    }));<br>    return; // Don&#39;t proceed with web login flow<br>  }<br>  <br>  // Fallback to web-based some login<br>  initiateWebLogin();<br>};<br><br>// Add this to your login button<br>document.getElementById(&#39;some-login-button&#39;).addEventListener(&#39;click&#39;, handleLoginRequest);</pre><p>When the user clicks the login button, the web app first checks if it’s running in a WebView. If it is, it delegates the login process to the native app, which can use the native authentication APIs for a smoother experience.</p><h4>2. In-App Purchases and Subscriptions</h4><p>Another powerful application is handling in-app purchases:</p><pre>// In your web app<br>const handleSubscription = (offeringId) =&gt; {<br>  if (window.ReactNativeWebView) {<br>    window.ReactNativeWebView.postMessage(JSON.stringify({<br>      action: &#39;DISPLAY_PAYWALL&#39;,<br>      offering: offeringId<br>    }));<br>    return; // Use native purchase flow<br>  }<br>  <br>  // Fallback to web payment processor<br>  window.location.href = `/checkout?offering=${offeringId}`;<br>};</pre><p>This approach allows you to use native in-app purchase APIs (like RevenueCat) when running inside the app, while falling back to web-based payment processors when running in a browser.</p><h4>3. Session Management</h4><p>You can also synchronize logout actions:</p><pre>// In your web app<br>const logoutUser = () =&gt; {<br>  // Clear local session data<br>  localStorage.removeItem(&#39;session_token&#39;);<br>  <br>  // If in WebView, tell the native app to clear its session too<br>  if (window.ReactNativeWebView) {<br>    window.ReactNativeWebView.postMessage(JSON.stringify({<br>      action: &#39;LOGOUT&#39;<br>    }));<br>  }<br>  <br>  // Redirect to login page<br>  window.location.href = &#39;/login&#39;;<br>};</pre><h3>Communication from Native to Web</h3><p>The communication isn’t just one-way. The React Native app can also send messages to the WebView:</p><pre>// In your React Native component<br>const webViewRef = useRef(null);<br><br>const sendMessageToWeb = (messageObject) =&gt; {<br>  if (webViewRef.current) {<br>    const messageString = JSON.stringify(messageObject);<br>    webViewRef.current.injectJavaScript(`<br>      window.postMessage(${JSON.stringify(messageString)}, &#39;*&#39;);<br>      true;<br>    `);<br>  }<br>};<br><br>// Example: Notify web app about successful purchase<br>const notifyWebOfPurchase = (purchaseDetails) =&gt; {<br>  sendMessageToWeb({<br>    type: &#39;PURCHASE_COMPLETED&#39;,<br>    details: purchaseDetails<br>  });<br>};</pre><p>On the web side, you would listen for these messages:</p><pre>// In your web application<br>window.addEventListener(&#39;message&#39;, (event) =&gt; {<br>  // Validate origin for security<br>  if (event.origin !== window.location.origin &amp;&amp; event.origin !== &#39;&#39;) {<br>    return;<br>  }<br>  <br>  try {<br>    const message = typeof event.data === &#39;string&#39; <br>      ? JSON.parse(event.data)<br>      : event.data;<br>    <br>    switch (message.type) {<br>      case &#39;PURCHASE_COMPLETED&#39;:<br>        handlePurchaseCompleted(message.details);<br>        break;<br>      // Handle other message types<br>    }<br>  } catch (error) {<br>    console.error(&#39;Error processing message from native app:&#39;, error);<br>  }<br>});</pre><h3>Best Practices for WebView Bridge Communication</h3><p>Based on my experience implementing these systems (and the scars to prove it), here are some best practices:</p><h4>1. Define a Clear Message Protocol</h4><p>Create a consistent structure for all messages passing through the bridge:</p><pre>{<br>  // Required fields<br>  action: &#39;ACTION_IDENTIFIER&#39;,  // What action to perform<br>  <br>  // Optional fields<br>  payload: {},                  // Data related to the action<br>  messageId: &#39;unique-id&#39;,       // For tracking responses<br>  timestamp: 1620000000000,     // When the message was sent<br>  debugMessage: &#39;Please work!&#39;  // Your increasingly desperate pleas<br>}</pre><p>Having a well-defined protocol doesn’t just make your code more maintainable — it makes debugging much easier when things inevitably go wrong at 2 AM the night before a release.</p><h4>2. Error Handling and Validation</h4><p>Always wrap your message handling in try/catch blocks and validate message structure:</p><pre>// In React Native<br>const handleWebViewMessage = (event) =&gt; {<br>  try {<br>    const message = JSON.parse(event.nativeEvent.data);<br>    <br>    // Validate message format<br>    if (!message.action || typeof message.action !== &#39;string&#39;) {<br>      console.warn(&#39;Invalid message format:&#39;, message);<br>      return;<br>    }<br>    <br>    // Process message...<br>  } catch (error) {<br>    console.error(&quot;Error handling message from WebView:&quot;, error);<br>  }<br>};</pre><h4>3. Platform Detection</h4><p>In your web app, create a utility for detecting the environment:</p><pre>// platform.js<br>export const isRunningInReactNative = () =&gt; {<br>  return !!window.ReactNativeWebView;<br>};<br><br>export const isIOS = () =&gt; {<br>  return isRunningInReactNative() &amp;&amp; <br>    window.mobileAppPlatform === &#39;ios&#39;;<br>};<br><br>export const isAndroid = () =&gt; {<br>  return isRunningInReactNative() &amp;&amp; <br>    window.mobileAppPlatform === &#39;android&#39;;<br>};</pre><p>This makes your conditional logic cleaner:</p><pre>import { isRunningInReactNative, isIOS } from &#39;./platform&#39;;<br><br>const handlePayment = () =&gt; {<br>  if (isRunningInReactNative()) {<br>    // Use native payment flow<br>  } else {<br>    // Use web payment flow<br>  }<br>  <br>  if (isIOS()) {<br>    // iOS-specific logic<br>  }<br>};</pre><h4>4. Handling Navigation</h4><p>When running inside a WebView, you often want to intercept certain navigation actions:</p><pre>// In React Native<br>const handleNavigationRequest = (request) =&gt; {<br>  const { url } = request;<br><br>  // Define URLs to intercept<br>  const paymentLinks = [<br>    &quot;https://payment-processor.com/checkout&quot;,<br>    &quot;https://subscription.service.com/plan&quot;<br>  ];<br><br>  // Check if URL should be intercepted<br>  if (paymentLinks.some(link =&gt; url.startsWith(link))) {<br>    // Handle with native UI<br>    navigation.navigate(&quot;NativePaymentScreen&quot;);<br>    return false; // Prevent WebView from loading the URL<br>  }<br><br>  return true; // Allow WebView to handle the navigation<br>};<br><br>// Add to WebView props<br>&lt;WebView<br>  onShouldStartLoadWithRequest={handleNavigationRequest}<br>  // other props...<br>/&gt;</pre><h3>Security Considerations</h3><p>When implementing WebView communication, keep these security considerations in mind:</p><ol><li><strong>Validate message origins</strong>: When receiving postMessage events in your web app, always check the origin</li><li><strong>Sanitize inputs</strong>: Never assume messages are well-formed or trustworthy (much like that “gluten-free” label on the office donuts)</li><li><strong>Limit exposed functionality</strong>: Only expose the minimum functionality needed (the principle of least privilege, or as I call it, “the mushroom approach” — keep ’em in the dark and feed ‘em… well, you know)</li><li><strong>HTTPS only</strong>: Ensure your web content is loaded over HTTPS (it’s 2025, folks!)</li><li><strong>Content Security Policy</strong>: Implement a strict CSP for your web content</li></ol><p>Remember: Security is like underwear. It’s not exciting to talk about, nobody wants to see the holes in yours, and you really shouldn’t share it with strangers on the internet.</p><h3>Conclusion</h3><p>The WebView bridge provides a powerful mechanism for creating hybrid applications that combine the best of native and web technologies. By establishing a clear communication protocol between your React Native app and web application, you can create seamless experiences that leverage native capabilities when available while maintaining a <strong>single core codebase </strong>which is what we did in <a href="https://datingai.pro/"><strong>datingai</strong></a><strong>.</strong></p><p>This approach is particularly valuable for teams that:</p><ul><li>Already have an existing web application they want to wrap in a native container</li><li>Need to maintain both web and native experiences with limited resources.</li><li>Want to gradually transition from web to native by incrementally adding native features</li><li>Have developers who value their weekends and want to sleep occasionally</li></ul><p>With the techniques outlined in this guide, you can create robust, maintainable hybrid applications that provide excellent user experiences across platforms. Your users won’t know the difference, your project manager will think you’re a wizard, and you’ll have saved countless hours that would have otherwise been spent duplicating business logic across codebases.</p><p>Remember: Good developers solve problems. Great developers avoid them entirely. By bridging your web and native apps, you’re doing a bit of both.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26a6e06b978c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting Up In-App Purchases with RevenueCat in iOS (React Native)]]></title>
            <link>https://medium.com/@pranavmore/setting-up-in-app-purchases-with-revenuecat-in-ios-react-native-ad8c259ee779?source=rss-c53c9c70483e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad8c259ee779</guid>
            <category><![CDATA[revenuecat]]></category>
            <category><![CDATA[in-app-purchase]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[iap]]></category>
            <category><![CDATA[react-native-development]]></category>
            <dc:creator><![CDATA[Pranav more]]></dc:creator>
            <pubDate>Thu, 24 Apr 2025 15:41:04 GMT</pubDate>
            <atom:updated>2025-04-24T15:41:04.391Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello fellow Devs 🫡</p><p>So I just spent the past couple weeks diving into the world of in-app purchases for our iOS app, and let me tell you what a ride it’s been.I finally had to tackle IAPs for the first time for . I figured I’d document my entire process to hopefully save someone else the headaches I went through.</p><h3><strong>Why I Chose RevenueCat</strong></h3><p>Let’s be real Apple’s StoreKit is powerful but feels like it was designed to make developers cry. I started looking into it and immediately saw a rabbit hole of receipt validation, subscription management, and server-side verification that I did NOT want to build from scratch.</p><p>After some research and a few recommendations from dev friends, I landed on RevenueCat. Their pitch was basically “we handle all the complicated IAP stuff so you don’t have to,” and that sounded perfect to me.</p><h3>Getting Started: The App Store Connect Puzzle</h3><p>Before even touching RevenueCat, I had to set up everything in App Store Connect, which was… an experience.</p><h4><strong>Setting Up App ID and IAP Capability</strong></h4><p>First things first, I had to make sure our app had the IAP capability enabled:</p><ol><li>Logged into Apple Developer Portal.</li><li>Found our app identifier under “Certificates, IDs &amp; Profiles”</li><li>Enabled the In-App Purchase capability (which was weirdly buried in the UI)</li></ol><h4><strong>Creating Products in App Store Connect</strong></h4><p>This part was tedious but straightforward:</p><ol><li>Logged into App Store Connect</li><li>Navigated to our app</li><li>Went to “Features” tab → “In-App Purchases”</li><li>Hit the “+” button to add our subscription tiers</li></ol><p>We decided to go with three subscription tiers <em>(for example)</em>:</p><ul><li>Monthly ($4.99)</li><li>Yearly ($39.99 which gives users ~2 months free)</li><li>Lifetime ($99.99)</li></ul><p>For each one, I had to fill out:</p><ul><li>Product ID (com.ourcompany.appname.monthly, etc.)</li><li>Name and description that users will see</li><li>Price tier</li><li>Review information (screenshots showing where the IAP appears in our app)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*o9RhYmi4sMeNwc8C5Jc4mw.png" /></figure><p>The subscription setup required creating a subscription group first, then adding the subscription products to it. The whole process took about an hour, and I definitely had to Google a few things along the way.</p><p>Pro tip: The language fields are required for EVERY localization you have enabled for your app. I missed this at first and kept getting cryptic error messages.</p><h3><strong>RevenueCat Setup: Much Smoother</strong></h3><p>After the App Store Connect marathon, setting up RevenueCat felt like a breath of fresh air.</p><p><strong>Creating My RevenueCat Account</strong></p><ol><li>Signed up at <a href="https://www.revenuecat.com/">revenuecat.com</a> (they have a free tier that’s perfect for getting started)</li><li>Created a new project for our app</li><li>Added our iOS app to the project (just needed our bundle ID)</li></ol><p><strong>Connecting to App Store Connect</strong></p><p>This is where RevenueCat really impressed me. They have two options:</p><ol><li>Using the app-specific shared secret (easier but less secure)</li><li>Using an App Store Connect API key (more secure, works across multiple apps)</li></ol><p>I went with option 2 since we have multiple apps. Setting up the API key in App Store Connect was a bit fiddly:</p><ol><li>In App Store Connect → “Users and Access” → “Keys”</li><li>Created a new key called “RevenueCat”</li><li>Downloaded the .p8 file (note: you can only download this ONCE, so don’t lose it!)</li><li>Uploaded it to RevenueCat along with the Key ID and Issuer ID</li></ol><p>And boom — RevenueCat was connected to our App Store products like magic! ✨</p><p><strong>Setting Up Products in RevenueCat</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/1*HbA2A7zOCK2it1Bt3YRhJQ.png" /></figure><p>Next, I had to create what RevenueCat calls “entitlements” and “offerings”:</p><ol><li>Created an entitlement called “premium_access” (this represents what users get access to)</li><li>Created an offering called “standard” (this is how you group products)</li><li>Added my App Store products to the offering as packages</li></ol><p>The mental model took me a minute to grasp:</p><ul><li>Entitlements = What features users get access to</li><li>Offerings = How you present purchase options to users</li><li>Packages = The actual products (monthly, yearly, etc.)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1y9HlfMzTv3QBqK7VIlFoA.png" /><figcaption>from actual setup</figcaption></figure><h3>Adding RevenueCat to Our React Native App</h3><p>Alright, now for the coding part! Time to integrate this into our React Native app.</p><pre># I used npm, but yarn works too<br>npm install react-native-purchases --save</pre><p>For iOS I had to:</p><pre>cd ios<br>pod install<br>cd ..</pre><h4><strong>Basic Implementation</strong></h4><p>First, I initialized the SDK in our app’s entry point:</p><pre>// I actually ended up creating a dedicated context provider for RevenueCat<br>// that I could wrap around my app. This worked WAY better than my first approach!<br><br>import React, { createContext, useContext, useEffect, useState } from &quot;react&quot;;<br>import { Platform } from &quot;react-native&quot;;<br>import Purchases from &quot;react-native-purchases&quot;;<br><br>// Use your RevenueCat API keys - REMEMBER TO CHANGE THESE!<br>const APIKeys = {<br>  apple: &quot;YOUR_IOS_API_KEY_HERE&quot;, <br>  google: &quot;YOUR_ANDROID_API_KEY_HERE&quot;,<br>};<br><br>const RevenueCatContext = createContext(null);<br><br>// Custom hook to use the context<br>export const useRevenueCat = () =&gt; {<br>  return useContext(RevenueCatContext);<br>};<br><br>export const RevenueCatProvider = ({ children }) =&gt; {<br>  const [user, setUser] = useState({ cookies: 0, items: [], pro: false });<br>  const [packages, setPackages] = useState([]);<br>  const [customerInfo, setCustomerInfo] = useState(null);<br>  const [offerings, setOfferings] = useState(null);<br>  <br>  useEffect(() =&gt; {<br>    // Configure RevenueCat Purchases based on the platform<br>    const setupPurchases = async () =&gt; {<br>      if (Platform.OS === &quot;ios&quot;) {<br>        Purchases.configure({ apiKey: APIKeys.apple });<br>      } else if (Platform.OS === &quot;android&quot;) {<br>        Purchases.configure({ apiKey: APIKeys.google });<br>      }<br><br>      // Enable debug logs for development<br>      Purchases.setDebugLogsEnabled(true);<br><br>      // Fetch offerings and set packages<br>      try {<br>        const offerings = await Purchases.getOfferings();<br>        setOfferings(offerings);<br>        <br>        // Get all packages from all offerings<br>        const allPackages = [];<br>        Object.values(offerings.all).forEach((offering) =&gt; {<br>          if (offering.availablePackages) {<br>            allPackages.push(...offering.availablePackages);<br>          }<br>        });<br>        setPackages(allPackages);<br>      } catch (error) {<br>        console.error(&quot;Error fetching offerings:&quot;, error);<br>      }<br><br>      // Fetch user info<br>      try {<br>        const customerInfo = await Purchases.getCustomerInfo();<br>        setCustomerInfo(customerInfo);<br>        updateUserState(customerInfo);<br>      } catch (error) {<br>        console.error(&quot;Error fetching customer info:&quot;, error);<br>      }<br>    };<br><br>    setupPurchases();<br>  }, []);<br>  <br>  // More implementation below...</pre><blockquote>Pro tip: make sure you keep restore purchase option else app will get reject.</blockquote><h4>Creating a Paywall Screen</h4><p>For the paywall screen, I decided to use our RevenueCat context provider to make things cleaner. Here’s how I implemented it:</p><pre>// PaywallScreen.js<br>import React, { useState } from &#39;react&#39;;<br>import { View, Text, TouchableOpacity, ActivityIndicator, StyleSheet, Alert } from &#39;react-native&#39;;<br>import { useRevenueCat } from &#39;../context/RevenueCatProvider&#39;;<br><br>const PaywallScreen = ({ navigation }) =&gt; {<br>  const [loading, setLoading] = useState(false);<br>  const { packages, purchasePackage, restorePermissions, user } = useRevenueCat();<br>  <br>  // Get the pro packages (I filtered for the specific packages I wanted)<br>  const proPackages = packages.filter(pkg =&gt; <br>    pkg.product.identifier.includes(&#39;pro&#39;) || <br>    pkg.product.identifier.includes(&#39;premium&#39;)<br>  );<br>  <br>  const handlePurchase = async (pkg) =&gt; {<br>    try {<br>      setLoading(true);<br>      const result = await purchasePackage(pkg);<br>      <br>      if (result.success) {<br>        Alert.alert(&#39;Success&#39;, &#39;Thank you for subscribing!&#39;);<br>        navigation.goBack(); // Go back to previous screen<br>      } else {<br>        Alert.alert(&#39;Error&#39;, result.error || &#39;Failed to complete purchase&#39;);<br>      }<br>    } finally {<br>      setLoading(false);<br>    }<br>  };<br>  <br>  const handleRestore = async () =&gt; {<br>    try {<br>      setLoading(true);<br>      const customerInfo = await restorePermissions();<br>      <br>      if (customerInfo.entitlements.active.pro) {<br>        Alert.alert(&#39;Success&#39;, &#39;Your purchase has been restored!&#39;);<br>        navigation.goBack(); // Go back to previous screen<br>      } else {<br>        Alert.alert(&#39;No Purchases Found&#39;, &#39;No previous purchases were found.&#39;);<br>      }<br>    } catch (e) {<br>      Alert.alert(&#39;Error&#39;, &#39;Failed to restore purchases&#39;);<br>    } finally {<br>      setLoading(false);<br>    }<br>  };<br>  <br>  if (loading) {<br>    return (<br>      &lt;View style={styles.container}&gt;<br>        &lt;ActivityIndicator size=&quot;large&quot; color=&quot;#0066cc&quot; /&gt;<br>      &lt;/View&gt;<br>    );<br>  }<br>  <br>  // If no packages are available, show an error<br>  if (!proPackages || proPackages.length === 0) {<br>    return (<br>      &lt;View style={styles.container}&gt;<br>        &lt;Text&gt;No subscription options available right now. Please try again later.&lt;/Text&gt;<br>      &lt;/View&gt;<br>    );<br>  }<br>  <br>  return (<br>    &lt;View style={styles.container}&gt;<br>      &lt;Text style={styles.title}&gt;Upgrade to Pro&lt;/Text&gt;<br>      &lt;Text style={styles.subtitle}&gt;Get unlimited access to all features&lt;/Text&gt;<br>      <br>      {/* Benefits list */}<br>      &lt;View style={styles.benefitsContainer}&gt;<br>        &lt;Text style={styles.benefitsTitle}&gt;Pro Benefits:&lt;/Text&gt;<br>        &lt;Text style={styles.benefitItem}&gt;✓ Unlimited cookies (currently: {user.cookies})&lt;/Text&gt;<br>        &lt;Text style={styles.benefitItem}&gt;✓ No ads or interruptions&lt;/Text&gt;<br>        &lt;Text style={styles.benefitItem}&gt;✓ Priority customer support&lt;/Text&gt;<br>        &lt;Text style={styles.benefitItem}&gt;✓ Early access to new features&lt;/Text&gt;<br>      &lt;/View&gt;<br>      <br>      {/* Packages */}<br>      {proPackages.map((pkg) =&gt; (<br>        &lt;TouchableOpacity<br>          key={pkg.identifier}<br>          style={styles.packageButton}<br>          onPress={() =&gt; handlePurchase(pkg)}<br>        &gt;<br>          &lt;Text style={styles.packageTitle}&gt;{pkg.product.title}&lt;/Text&gt;<br>          &lt;Text style={styles.packagePrice}&gt;{pkg.product.priceString}&lt;/Text&gt;<br>          &lt;Text style={styles.packageDescription}&gt;{pkg.product.description}&lt;/Text&gt;<br>        &lt;/TouchableOpacity&gt;<br>      ))}<br>      <br>      &lt;TouchableOpacity style={styles.restoreButton} onPress={handleRestore}&gt;<br>        &lt;Text style={styles.restoreText}&gt;Restore Purchases&lt;/Text&gt;<br>      &lt;/TouchableOpacity&gt;<br>    &lt;/View&gt;<br>  );<br>};<br><br>const styles = StyleSheet.create({<br>  //add your styles<br>});<br><br>export default PaywallScreen;</pre><h4>Let’s Complete Our RevenueCat Provider</h4><p>Now let me show you how I finished implementing the RevenueCat provider — the cool part is that once you have this all set up, you can just use it anywhere in your app:</p><pre>// Continuing from our RevenueCatProvider.js code...<br><br>  // Update user state based on RevenueCat info<br>  const updateUserState = (customerInfo) =&gt; {<br>    // Check if user has the &quot;pro&quot; entitlement<br>    const pro = customerInfo.entitlements.active[&quot;pro&quot;] !== undefined;<br>    <br>    // Give extra cookies to pro users (just an example feature)<br>    const cookies = pro ? 100 : 10;<br>    setUser({ ...user, pro, cookies });<br>  };<br><br>  // Purchase a package<br>  const purchasePackage = async (pack) =&gt; {<br>    try {<br>      const purchaseInfo = await Purchases.purchasePackage(pack);<br>      setCustomerInfo(purchaseInfo.customerInfo); // Update customer info after purchase<br>      updateUserState(purchaseInfo.customerInfo);<br>      return { success: true };<br>    } catch (error) {<br>      if (error.userCancelled) {<br>        return {<br>          success: false,<br>          error: &quot;Purchase was cancelled&quot;,<br>        };<br>      }<br><br>      // Handle specific error cases<br>      if (error.code === &quot;InvalidReceiptError&quot;) {<br>        return {<br>          success: false,<br>          error: &quot;There was a problem with the App Store. Please try again.&quot;,<br>        };<br>      }<br><br>      // Log the full error for debugging<br>      console.error(&quot;Purchase failed with error:&quot;, {<br>        code: error.code,<br>        message: error.message,<br>        underlyingError: error.underlyingErrorMessage,<br>      });<br><br>      return {<br>        success: false,<br>        error: &quot;Unable to complete purchase. Please try again later.&quot;,<br>      };<br>    }<br>  };<br><br>  // Restore purchases<br>  const restorePermissions = async () =&gt; {<br>    try {<br>      const customerInfo = await Purchases.restoreTransactions();<br>      setCustomerInfo(customerInfo); // Update customer info after restore<br>      updateUserState(customerInfo);<br>      return customerInfo;<br>    } catch (error) {<br>      console.error(&quot;Error restoring transactions:&quot;, error);<br>      throw error;<br>    }<br>  };<br><br>  return (<br>    &lt;RevenueCatContext.Provider<br>      value={{<br>        purchasePackage,<br>        restorePermissions,<br>        user,<br>        packages,<br>        customerInfo,<br>        offerings,<br>      }}<br>    &gt;<br>      {children}<br>    &lt;/RevenueCatContext.Provider&gt;<br>  );<br>};</pre><h4>Using the Provider in Our App</h4><p>Now I just needed to wrap my app with this provider and use it in my screens:</p><pre>// App.js<br>import React from &#39;react&#39;;<br>import { NavigationContainer } from &#39;@react-navigation/native&#39;;<br>import { createStackNavigator } from &#39;@react-navigation/stack&#39;;<br>import { RevenueCatProvider } from &#39;./context/RevenueCatProvider&#39;;<br>import HomeScreen from &#39;./screens/HomeScreen&#39;;<br>import PaywallScreen from &#39;./screens/PaywallScreen&#39;;<br><br>const Stack = createStackNavigator();<br><br>const App = () =&gt; {<br>  return (<br>    &lt;RevenueCatProvider&gt;<br>      &lt;NavigationContainer&gt;<br>        &lt;Stack.Navigator&gt;<br>          &lt;Stack.Screen name=&quot;Home&quot; component={HomeScreen} /&gt;<br>          &lt;Stack.Screen name=&quot;Paywall&quot; component={PaywallScreen} /&gt;<br>        &lt;/Stack.Navigator&gt;<br>      &lt;/NavigationContainer&gt;<br>    &lt;/RevenueCatProvider&gt;<br>  );<br>};<br><br>export default App;</pre><p>And in my HomeScreen, I can now use the context to check the user’s subscription status:</p><pre>// HomeScreen.js<br>import React from &#39;react&#39;;<br>import { View, Text, Button, StyleSheet } from &#39;react-native&#39;;<br>import { useRevenueCat } from &#39;../context/RevenueCatProvider&#39;;<br><br>const HomeScreen = ({ navigation }) =&gt; {<br>  const { user } = useRevenueCat();<br>  <br>  return (<br>    &lt;View style={styles.container}&gt;<br>      &lt;Text style={styles.title}&gt;Welcome to My App&lt;/Text&gt;<br>      <br>      &lt;View style={styles.cookieContainer}&gt;<br>        &lt;Text style={styles.cookieText}&gt;<br>          You have {user.cookies} cookies available!<br>        &lt;/Text&gt;<br>      &lt;/View&gt;<br>      <br>      {user.pro ? (<br>        &lt;View style={styles.proContainer}&gt;<br>          &lt;Text style={styles.proText}&gt;<br>            You are a PRO user! Enjoy unlimited features.<br>          &lt;/Text&gt;<br>          {/* Pro-only features here */}<br>        &lt;/View&gt;<br>      ) : (<br>        &lt;View style={styles.upgradeContainer}&gt;<br>          &lt;Text style={styles.upgradeText}&gt;<br>            Upgrade to PRO to get unlimited cookies and more features!<br>          &lt;/Text&gt;<br>          &lt;Button<br>            title=&quot;See PRO Options&quot;<br>            onPress={() =&gt; navigation.navigate(&#39;Paywall&#39;)}<br>            color=&quot;#0066cc&quot;<br>          /&gt;<br>        &lt;/View&gt;<br>      )}<br>    &lt;/View&gt;<br>  );<br>};<br><br>const styles = StyleSheet.create({<br> // styles here<br>});<br><br>export default HomeScreen;</pre><h3>Testing My Implementation</h3><p>Testing in-app purchases is always a bit tricky since you need to use Apple’s sandbox environment. Here’s how I set it up:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VHMHTSJDp3DZmd03Ut6CgA.png" /><figcaption>Revenuecat gives you option to check sandbox data</figcaption></figure><p><strong>Created a sandbox tester account in App Store Connect:</strong></p><ul><li>Under “Users and Access” → “Sandbox” → “Testers”</li><li>Added a new tester with a unique email address</li></ul><p><strong>On my test device:</strong></p><ul><li>Signed out of my personal Apple ID</li><li>When prompted during testing, signed in with the sandbox account</li></ul><p><strong>For testing subscription lifecycles, I found that Apple accelerates renewals in sandbox mode:</strong></p><ul><li>Monthly subscriptions renew in 5 minutes</li><li>Annual subscriptions renew in 1 hour</li></ul><p>This made it much easier to test renewal flows without waiting for an actual month to pass!</p><h3>Issues I Ran Into (And How I Fixed Them)</h3><h4><strong>Problem #1: “Cannot connect to iTunes Store”</strong></h4><p>This one had me pulling my hair out. After several attempts, I realized it was because I was trying to test on the iOS simulator, which doesn’t support IAP testing. Switched to a <strong>physical device </strong>and it worked fine.</p><h4>Problem #2: Purchases weren’t being recognized</h4><p>After making a purchase, my app wasn’t updating to show premium access. Turned out I had a typo in my entitlement identifier check.</p><blockquote>The entitlement name has to match EXACTLY what you set up in RevenueCat dashboard. In my case, I called my entitlement “pro” but was trying to check for “premiumAccess” in the code. Rookie mistake! 🤦‍♂️</blockquote><p>👆🏻But revenuecat now gives you option to import products</p><h4>Problem #3: Products not showing up</h4><p>This was a timing issue. It takes a while for products to propagate through App Store systems. After creating the products, I had to wait about <strong>few hours</strong> before they showed up in RevenueCat.</p><h3>Moving to Production</h3><p>Before releasing to production, I had to:</p><ol><li>Check the necessary things: api keys, offerings coming in right.</li><li>Make sure all products were <strong>“Ready to Submit”</strong> in App Store Connect</li><li>Add a section to our privacy policy about subscription data handling</li></ol><p>I also made sure to thoroughly test the “Restore Purchases” functionality since I’ve been burned by that in the past.</p><h3>Things I Wish I Knew Before Starting</h3><ol><li><strong>App Store Connect is slow</strong> — Changes can take hours to propagate. Don’t panic if things don’t show up immediately. You may panic because you did everything correct and nothing is working (give it a time)</li><li><strong>Test on real devices</strong> — The simulator doesn’t support in-app purchases. Save yourself the headache and test on a physical device from the start.</li></ol><blockquote>👆🏻 Install development build on physical device to test IAP</blockquote><ol><li><strong>Log everything during development</strong> — RevenueCat’s logs were super helpful for debugging. Setting Purchases.setDebugLogsEnabled(true) showed me exactly what was happening behind the scenes.</li><li><strong>The mental model matters</strong> — Understanding RevenueCat’s concepts of offerings, packages, and entitlements made implementation much smoother once it clicked. ( again it’s a choice, may vary with usecase)</li><li><strong>Use React Context for cleaner code</strong> — Creating a dedicated provider for RevenueCat made everything so much easier to manage across the app. Way better than calling the RevenueCat methods directly in each component. ( my preference)</li><li><strong>Keep your API keys separate</strong> — I set up platform-specific keys so the code automatically uses the right one:</li></ol><pre>// Platform-specific API keys<br>const APIKeys = {<br>  apple: &quot;YOUR_IOS_API_KEY_HERE&quot;,<br>  google: &quot;YOUR_ANDROID_API_KEY_HERE&quot;, <br>};<br><br>// Then in the code:<br>if (Platform.OS === &quot;ios&quot;) {<br>  Purchases.configure({ apiKey: APIKeys.apple });<br>} else if (Platform.OS === &quot;android&quot;) {<br>  Purchases.configure({ apiKey: APIKeys.google });<br>}</pre><h3>Final Thoughts</h3><p>Setting up in-app purchases with RevenueCat was WAY easier than I expected. Once I got past the App Store Connect hurdles, the actual implementation was pretty straightforward. The RevenueCat dashboard gives us great analytics on conversions and subscription retention, which i like.</p><p>If I had to do it all over again, I would definitely still use RevenueCat. The time saved on server-side receipt validation and handling all the edge cases alone was worth it.</p><p>Hope this helps someone else diving into IAPs for the first time! Feel free to reach out if you have any questions or run into issues I didn’t cover here.</p><p>Happy coding! 🚀</p><p>P.S. If you’re reading this and thinking about implementing IAPs yourself, definitely check out RevenueCat’s docs. They have specific guides for React Native that are really helpful.</p><blockquote>Again, use physical device to test and use development build</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad8c259ee779" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best Free Illustration Websites for Your Projects]]></title>
            <link>https://medium.com/@pranavmore/best-free-illustration-websites-for-your-projects-a9c48a5f11ca?source=rss-c53c9c70483e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9c48a5f11ca</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[free-illustrations]]></category>
            <category><![CDATA[illustration]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[free-resources]]></category>
            <dc:creator><![CDATA[Pranav more]]></dc:creator>
            <pubDate>Tue, 04 Feb 2025 06:52:47 GMT</pubDate>
            <atom:updated>2025-02-04T06:52:47.878Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s digital world, visuals play a major role in making websites, apps, and social media posts look attractive. But not everyone is a designer, and premium illustrations can be expensive. Luckily, there are many websites where you can find <strong>free illustrations</strong> that are both high-quality and easy to use.</p><p>Whether you are a developer, content creator, or someone running a startup, these resources will save you time and money. Here’s a list of the <strong>best free illustration websites</strong> you should check out.</p><h3>1. Undraw</h3><p><a href="https://undraw.co/">unDraw - Open source illustrations for any idea</a></p><p>Undraw is one of the most popular sites for free illustrations. The best part? You can <strong>customize the color</strong> of the illustrations to match your brand or theme. The collection is vast, and all illustrations are available in <strong>SVG format</strong>, making them perfect for websites and apps.</p><p><strong>Best for:</strong> Websites, UI design, and marketing content.</p><h3>2. Storyset</h3><p><a href="https://storyset.com/">Storyset: Customize, animate and download illustration for free</a></p><p>If you want fully editable illustrations, Storyset is a great choice. You can customize the <strong>style, colors, and even add animations</strong>. Whether you need illustrations for blogs, presentations, or social media, this platform gives you a lot of flexibility.</p><p><strong>Best for:</strong> Animated illustrations, presentations, and blogs.</p><h3>3. DrawKit</h3><p><a href="https://www.drawkit.com/">DrawKit - Beautiful 2D &amp; 3D Illustrations and Icons</a></p><p>DrawKit offers a collection of <strong>hand-drawn and vector-style illustrations</strong>. Their free section is quite extensive and covers various themes like business, travel, and technology. These illustrations come in <strong>PNG and SVG formats</strong>, making them easy to use in any design tool.</p><p><strong>Best for:</strong> Hand-drawn and sketch-style illustrations.</p><h3>4. ManyPixels</h3><p><a href="https://www.manypixels.co/gallery">Free to Use Clip Art Images &amp; Vector Illustrations | ManyPixels</a></p><p>ManyPixels provides <strong>modern, flat-style illustrations</strong> for free. They keep updating their gallery with new designs, and you can find a variety of themes like healthcare, remote work, education, and more.</p><p><strong>Best for:</strong> Flat illustrations for landing pages and UI design.</p><h3>5. Open Doodles</h3><p><a href="https://www.opendoodles.com/">Open Doodles</a></p><p>If you like quirky and fun illustrations, Open Doodles is the perfect site. The illustrations are <strong>completely free to use</strong> without any restrictions. They work great for storytelling, blog posts, and casual designs.</p><p><strong>Best for:</strong> Fun and playful designs.</p><h3>6. Icons8 Ouch!</h3><p><a href="https://icons8.com/illustrations">Free Vector Graphics, Clipart Images and Illustrations</a></p><p>Icons8 Ouch! provides high-quality <strong>3D and vector-style illustrations</strong>. They have a mix of free and premium illustrations. The free ones require attribution, but they are great for websites and mobile apps.</p><p><strong>Best for:</strong> 3D illustrations and UI/UX design.</p><h3>7. Isometric</h3><p><a href="https://isometric.online/">isometric.online</a></p><p>For those who love isometric designs, this website is a goldmine. It provides <strong>fully editable isometric illustrations</strong> that are easy to modify in tools like Figma and Illustrator.</p><p><strong>Best for:</strong> Isometric-style website and app designs.</p><h3>8. Blush</h3><p><a href="https://blush.design/">Blush: Illustrations for everyone</a></p><p>Blush is a unique platform that allows you to <strong>customize illustrations</strong> created by professional artists. The free version gives access to many illustrations, but some premium options require payment.</p><p><strong>Best for:</strong> Customizable vector illustrations.</p><h3>9. Black Illustrations</h3><p><a href="https://www.blackillustrations.com/">Illustrations of Black People for Your Next Digital Project | Black Illustrations</a></p><p>This website focuses on <strong>diverse and inclusive illustrations</strong> featuring Black characters in different scenarios. It’s an excellent resource for adding representation to your projects.</p><p><strong>Best for:</strong> Diversity and inclusion in design.</p><h3>10. Humaaans</h3><p><a href="https://www.humaaans.com/">Humaaans: Mix-&amp;-Match illustration library</a></p><p>Humaaans lets you <strong>mix and match illustration components</strong>, so you can create unique characters and scenes. It’s a great tool if you want to create something original without starting from scratch.</p><p><strong>Best for:</strong> Custom character illustrations for storytelling.</p><h3>Conclusion</h3><p>Gone are the days when you needed to hire a designer for every small project. With these free illustration websites, you can easily enhance your websites, blogs, apps, and presentations without spending a rupee.</p><p>If you found this useful, do share it with your fellow creators! And let me know in the comments which site is your favorite. 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9c48a5f11ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>