<?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 Basavaraja V on Medium]]></title>
        <description><![CDATA[Stories by Basavaraja V on Medium]]></description>
        <link>https://medium.com/@basavaraja-dev?source=rss-1516ae19b56------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NmWgkZwbvbnTrs6Zq1I2EQ.png</url>
            <title>Stories by Basavaraja V on Medium</title>
            <link>https://medium.com/@basavaraja-dev?source=rss-1516ae19b56------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 06:16:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@basavaraja-dev/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[I Made $132 From My Indie Apps. It’s Not Much, But It Means Everything.]]></title>
            <link>https://medium.com/@basavaraja-dev/i-made-132-from-my-indie-apps-its-not-much-but-it-means-everything-4ae5a8c56acb?source=rss-1516ae19b56------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ae5a8c56acb</guid>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios-development]]></category>
            <dc:creator><![CDATA[Basavaraja V]]></dc:creator>
            <pubDate>Sun, 15 Nov 2026 04:52:43 GMT</pubDate>
            <atom:updated>2026-11-15T04:52:43.443Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oeOR-1qb9VMbKS-xXYzdYg.png" /></figure><p><em>14 paid units. Multiple apps. One solo founder. And a reminder that building something people pay for is harder — and more rewarding — than it looks.</em></p><p>There was a time when I wondered whether anyone would ever pay for something I built.</p><p>I’d spend days, sometimes weeks, building an app. Polishing the UI. Fixing bugs. Shipping updates. Publishing it to the App Store.</p><p>Then came the hardest part.</p><p>Getting someone to actually pay for it.</p><p>I’m still figuring that out.</p><p>But October brought a small milestone worth sharing.</p><p><strong>My indie apps generated ₹11,551.17 (approximately $132) in estimated App Store proceeds.</strong></p><p>That’s 14 paid units.</p><p>Not thousands of dollars. Not a viral launch. Not a life-changing success story.</p><p>Just $132 from products I built.</p><p>And honestly? I’m excited.</p><h3>The reality of being a solo indie founder</h3><p>I build and experiment with multiple products.</p><p>Some ideas work. Some don’t get traction. Some get downloads but struggle to convert users into paying customers.</p><p>I’ve learned that building software is only one part of running a product business.</p><p>Distribution is hard.</p><p>Monetization is hard.</p><p>Getting users to care enough to pay is even harder.</p><p>You can build a beautiful product and still struggle to get your first customer.</p><p>That’s the reality nobody should ignore.</p><h3>Why $132 matters to me</h3><p>Because these aren’t just numbers on a dashboard.</p><p>Behind them are:</p><ul><li>Hours spent learning and building.</li><li>Products that made it into the hands of real users.</li><li>People who found enough value to spend money.</li><li>Experiments that taught me what to do differently next time.</li></ul><p>Every purchase is a little validation.</p><p>It tells me that somewhere, someone found something I built useful enough to pay for.</p><p>That’s worth celebrating.</p><h3>What’s next?</h3><p>I’m not trying to stop at $132.</p><p>My next milestones:</p><ul><li>$500/month</li><li>$1,000/month</li><li>$3,000/month</li></ul><p>The long-term goal is to build a sustainable portfolio of indie products that generates revenue without depending entirely on client work.</p><p>I know there’s a long way to go.</p><p>But I’d rather build, ship, fail, learn and repeat than spend another year wondering what might have happened.</p><h3>A question for indie hackers</h3><p>If you’re building your own products, I’d genuinely love to know:</p><p><strong>What’s harder for you: building a product people love, or getting those people to pay for it?</strong></p><p>And if you’re still waiting for your first dollar, keep shipping.</p><p>I’m sharing the journey — the wins, the failures and everything in between.</p><p>This is just the beginning. 🚀</p><p><em>Solo founder. Multiple experiments. One goal: build a sustainable indie product business.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ae5a8c56acb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Built an AI Relationship App as a Solo Founder. Here’s What the First 28 Days Taught Me.]]></title>
            <link>https://medium.com/@basavaraja-dev/i-built-an-ai-relationship-app-as-a-solo-founder-heres-what-the-first-28-days-taught-me-b9d7f8eaa51f?source=rss-1516ae19b56------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9d7f8eaa51f</guid>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[solopreneur]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Basavaraja V]]></dc:creator>
            <pubDate>Sun, 01 Nov 2026 05:57:02 GMT</pubDate>
            <atom:updated>2026-11-01T05:57:02.836Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fJaCY81xfmPA2_mylSjTZQ.png" /></figure><h3><em>No investors. No team. Just an idea, countless experiments, and the challenge of turning a small app into a sustainable business.</em></h3><p>There is something special about seeing someone pay for a product you built yourself.</p><p>It might not be a huge amount of money. It might not be enough to quit your job or change your life. But it is proof that something you imagined, designed, developed, and launched has real value to another person.</p><p>That&#39;s what makes building software as an independent developer exciting.</p><p>Recently, I reached a small milestone with my app, <strong>We2</strong>.</p><p>Here are the numbers from the last 28 days:</p><ul><li><strong>$156</strong> in revenue</li><li><strong>$103</strong> in monthly recurring revenue (MRR)</li><li><strong>566</strong> new customers</li><li><strong>15</strong> active subscriptions</li><li><strong>1</strong> active trial</li></ul><p>These numbers might look modest compared with the impressive revenue screenshots we regularly see on X.</p><p>But for a solo founder building independently, every one of these numbers represents something worth learning from.</p><p>I want to share how I got here, what I&#39;m learning, and what I plan to do next.</p><h3>The idea behind We2</h3><p>Relationships are important, but meaningful conversations don&#39;t always happen naturally.</p><p>Think about couples who have been together for years. They care about each other, spend time together, and share everyday responsibilities. Yet sometimes, they run out of things to talk about beyond work, daily routines, and responsibilities.</p><p>Long-distance couples face another challenge. When physical distance separates two people, meaningful communication becomes even more important.</p><p>I started thinking about a simple question:</p><p><em>What if an app could help couples understand each other better through meaningful questions?</em></p><p>That idea became We2.</p><p>We2 is an AI-powered relationship questions app designed to help couples discover new things about each other, explore interesting topics, and build deeper connections.</p><p>Instead of another social networking app or messaging platform, I wanted to create something focused on conversations.</p><p>The concept was simple, but building a product around it was not.</p><h3>Building everything as a solo founder</h3><p>I&#39;m a software engineer with several years of development experience, primarily working with Flutter and Firebase.</p><p>Being a developer gives me one significant advantage: I can take an idea and turn it into a working product without hiring an engineering team.</p><p>But being a solo founder also means wearing several different hats.</p><p>I have to think about:</p><ul><li>Product development and architecture.</li><li>UI/UX design.</li><li>App Store and Google Play submissions.</li><li>Subscription integration and payments.</li><li>Customer acquisition and marketing.</li><li>User feedback and product improvements.</li><li>Revenue, infrastructure, and API costs.</li></ul><p>There is no separate marketing department waiting to promote the product.</p><p>There is no product manager deciding what should be built next.</p><p>And there is no team to take over when something breaks.</p><p>You build it, launch it, monitor it, and figure things out along the way.</p><p>Sometimes that&#39;s exciting. Sometimes it&#39;s exhausting.</p><p>But I enjoy having the freedom to experiment.</p><h3>Getting users is only half the challenge</h3><p>One of the biggest lessons I&#39;ve learned while building apps is that launching a product and getting people to use it are two completely different problems.</p><p>Developers often spend months building features, polishing interfaces, and fixing bugs.</p><p>We assume that once the app is available on the App Store or Google Play, users will discover it.</p><p>That rarely happens automatically.</p><p>People have thousands of apps competing for their attention. Even a useful product needs distribution.</p><p>With We2, I&#39;ve been experimenting with organic marketing, social media content, positioning, and ways to communicate the product&#39;s value.</p><p>The goal is not simply to get downloads.</p><p>It&#39;s to reach people who genuinely have the problem We2 is trying to solve.</p><p>A download is an opportunity. A returning user is a stronger signal. A paying subscriber is evidence that someone sees enough value to pay for the experience.</p><p>These are very different milestones.</p><h3>Looking at the numbers honestly</h3><p>Let&#39;s look at the current performance.</p><p><strong>1. Revenue: $156</strong></p><p>This represents the revenue shown in RevenueCat for the last 28 days.</p><p>It&#39;s encouraging to see people paying for something I built independently.</p><p>But revenue alone doesn&#39;t tell the whole story. API expenses, platform commissions, infrastructure, and other operating costs matter when evaluating the actual profitability of a product.</p><p><strong>2. Monthly recurring revenue: $103</strong></p><p>This is the metric I&#39;m particularly interested in.</p><p>One-time purchases can create short-term revenue spikes, but recurring revenue gives a product the opportunity to build a more predictable business.</p><p>Reaching $103 MRR is a small milestone.</p><p>The next target is $1,000 MRR.</p><p>That&#39;s not going to happen just by adding more features. It will require better positioning, stronger retention, and a repeatable acquisition strategy.</p><p><strong>3. New customers: 566</strong></p><p>This is another encouraging signal.</p><p>Getting 566 new customers in 28 days suggests that people are discovering the product.</p><p>Now the important question is what happens after they arrive.</p><p>Do they understand the product?</p><p>Do they complete their first meaningful interaction?</p><p>Do they come back?</p><p>Do they invite their partner?</p><p>Do they eventually become subscribers?</p><p>These questions matter much more than simply celebrating download numbers.</p><p><strong>4. Active subscriptions: 15</strong></p><p>Fifteen active subscriptions are a starting point.</p><p>But they also reveal an opportunity.</p><p>There is a gap between people discovering the product and people deciding to pay for it.</p><p>Understanding that gap is one of my biggest priorities.</p><h3>What I&#39;m learning about building indie products</h3><p>After building and launching multiple products, I&#39;ve started changing how I approach development.</p><p>Here are three lessons that stand out.</p><h3>1. Distribution deserves as much attention as development</h3><p>I used to spend a lot of time thinking about what features to build next.</p><p>But a great product without distribution can remain invisible.</p><p>You need to understand where your audience spends time, what problems they discuss, and how your product can naturally become part of that conversation.</p><p>Building is important.</p><p>Getting the right people to discover what you&#39;ve built is equally important.</p><h3>2. Don&#39;t confuse downloads with product-market fit</h3><p>A product can receive hundreds or even thousands of downloads without becoming a sustainable business.</p><p>People might download it out of curiosity and never open it again.</p><p>That&#39;s why I&#39;m paying more attention to subscriptions, retention, engagement, and conversion.</p><p>I want We2 to become something couples genuinely want to use, not just another app they install and forget.</p><h3>3. Small milestones matter</h3><p>It&#39;s easy to become discouraged when comparing your progress with founders announcing $10K, $50K, or $100K months.</p><p>But everyone has a different starting point.</p><p>For someone building independently, the first paying customer can be more meaningful than a large number on someone else&#39;s revenue dashboard.</p><p>The important thing is to keep learning and improving.</p><h3>What&#39;s next for We2?</h3><p>My immediate goal is to take We2 from $103 MRR to $1,000 MRR.</p><p>I&#39;m focusing on a few areas:</p><ul><li><strong>Better onboarding:</strong> Help new users understand the value of We2 immediately.</li><li><strong>User retention:</strong> Give couples compelling reasons to return.</li><li><strong>Organic acquisition:</strong> Build a consistent content and distribution engine.</li><li><strong>Subscription conversion:</strong> Understand why users don&#39;t upgrade and improve the experience.</li><li><strong>Product experience:</strong> Make the app genuinely useful for couples rather than simply adding more AI features.</li></ul><p>I don&#39;t want to chase growth at any cost.</p><p>I want to build a product that people enjoy using and that can generate sustainable recurring revenue.</p><h3>The bigger goal</h3><p>We2 is one of several product experiments I&#39;ve worked on as an independent developer.</p><p>My long-term ambition is to build a portfolio of profitable products.</p><p>I don&#39;t necessarily want to build one massive company with hundreds of employees.</p><p>I enjoy creating products, solving problems, experimenting with business models, and seeing small ideas become real businesses.</p><p>But I&#39;m also learning that creating products is only one part of the journey.</p><p>The real challenge is building something people want, finding a reliable way to reach them, and creating a business that can sustain itself.</p><p>For now, I&#39;m happy with this milestone.</p><p><strong>$103 MRR. 566 new customers. 15 active subscriptions.</strong></p><p>It&#39;s not a massive success story.</p><p>It&#39;s a work in progress.</p><p>And that&#39;s exactly why I wanted to share it.</p><p>I&#39;m still building. Still experimenting. Still figuring things out.</p><p><strong>Next stop: $1,000 MRR.</strong></p><p>Let&#39;s see how far this little experiment can go.</p><p><em>I&#39;m documenting my journey as a solo founder, sharing lessons from building mobile apps, experimenting with AI products, and learning distribution along the way.</em></p><p><strong>If you&#39;re building something independently too, I&#39;d love to hear what you&#39;re working on.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9d7f8eaa51f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Refind: A Better Way to Save and Rediscover the social media and web]]></title>
            <link>https://medium.com/@basavaraja-dev/refind-a-better-way-to-save-and-rediscover-the-social-media-and-web-0d2f0dc16fbf?source=rss-1516ae19b56------2</link>
            <guid isPermaLink="false">https://medium.com/p/0d2f0dc16fbf</guid>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Basavaraja V]]></dc:creator>
            <pubDate>Sat, 24 Oct 2026 06:01:55 GMT</pubDate>
            <atom:updated>2026-10-24T06:01:55.077Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aSXdMibIT-0Qsa_fppMPEw.png" /></figure><p><em>We save hundreds of things online. But how often do we find them again when we actually need them?</em></p><p>Every day, we discover things worth keeping.</p><p>An article explains a problem we’ve been trying to solve. A video teaches us something new. A developer shares a useful tool. Someone posts a recipe we want to try. We find a resource that could be valuable for a project we’re working on.</p><p>So we save it.</p><p>We bookmark the page, like the post, add it to a collection, copy the URL into our notes, or send it to ourselves in a messaging app.</p><p>At that moment, saving feels like the right decision. We don’t have time to explore the resource, but we don’t want to lose it either.</p><p>The problem appears later.</p><p>When we finally need that article, video, or tool, we can’t remember where we saved it. We search our browser history, scroll through social media collections, open old notes, and sometimes search the internet again for something we’ve already found.</p><p>It’s a surprisingly common problem: <strong>saving information is easy, but building a useful personal library of information is much harder.</strong></p><p>That problem is what inspired Refind.</p><h3>The internet is full of useful information. Our systems for keeping it aren’t always useful.</h3><p>The internet has become an enormous library of ideas, knowledge, tutorials, entertainment, and practical resources.</p><p>We discover content through search engines, social networks, newsletters, blogs, online communities, and conversations with other people. Every platform introduces something new that we might want to revisit.</p><p>But our saved content often ends up scattered across different places.</p><p>A tutorial might be bookmarked in a browser. A video might be saved on Instagram. An article might sit in a reading list. A useful website might be buried in a message to ourselves.</p><p>Each individual action makes sense. Collectively, however, these habits create a fragmented personal archive.</p><p>Over time, the collection grows, and the original reason for saving each item becomes harder to remember.</p><p>We accumulate bookmarks without building a reliable way to return to them.</p><p>The result is digital clutter: information we wanted to preserve but can no longer easily use.</p><p>And the frustrating part is that we often rediscover the same information through another search, even though we already saved it somewhere.</p><h3>Introducing Refind</h3><p><a href="https://heyidb.com/refind">Refind</a> is a fast, minimalist, privacy-focused bookmark manager designed to help people save and rediscover useful web content.</p><p>The idea behind it is straightforward: make it easier to keep track of the things you find online, so you can return to them when you need them.</p><p>Rather than treating every interesting link as something that must be consumed immediately, Refind supports a more natural habit.</p><p>Discover something useful. Save it. Return to it later.</p><p>Whether you’re collecting articles for research, keeping track of tools for your next project, saving recipes, or building a personal library of interesting websites, Refind is designed around that simple workflow.</p><p>The goal isn’t to make managing bookmarks another complicated productivity project.</p><p>It’s to make the act of saving useful information feel more intentional.</p><h3>1. Save links from wherever you discover them</h3><p>Useful content doesn’t live in one place.</p><p>You might discover an article while browsing Safari, find a resource on a social platform, or come across a website while using another app.</p><p>Having to copy a URL, switch applications, and manually organize it creates friction. When saving becomes inconvenient, we either abandon the process or accumulate links in places that are difficult to manage.</p><p>Refind supports a share extension, allowing you to save links directly from Safari, social platforms, and other apps through the system sharing workflow.</p><p>This makes saving part of the natural browsing experience.</p><p>You don’t have to interrupt what you’re doing to build a complicated record of every useful thing you discover.</p><p>You can save the link and get back to what matters at that moment.</p><h3>2. Build a personal library instead of scattering bookmarks everywhere</h3><p>A bookmark should be more than a reminder that something once caught your attention.</p><p>Ideally, it should be an entry point back to something useful.</p><p>Over time, the links we save can represent our interests, ongoing projects, research, learning goals, and future plans. A collection of articles might help us understand a subject. A collection of tools might support our work. A list of resources might help us prepare for a project we haven’t started yet.</p><p>Refind is designed to help bring these links into a more intentional personal collection.</p><p>Instead of relying entirely on scattered browser bookmarks, social media saves, and notes, you can use a dedicated bookmark organizer for the web content you want to keep.</p><p>The value isn’t simply in having more saved links.</p><p>It’s in making those links useful when the moment comes to revisit them.</p><h3>3. Make room for reading later</h3><p>One of the biggest reasons we save content is that we don’t have time to consume it immediately.</p><p>We discover an interesting article during work, find a tutorial while doing something else, or come across a resource while scrolling through our feeds.</p><p>We don’t want to lose it, but we also don’t want to stop what we’re doing.</p><p>Saving for later creates a useful separation between discovery and consumption.</p><p>You can collect what interests you now and return to it when you have the time and attention to explore it properly.</p><p>Refind’s positioning as an offline link saver and reader reflects this desire for a more flexible relationship with online content.</p><p>Instead of expecting yourself to read everything immediately, you can preserve the links that matter and revisit them as your schedule allows.</p><p><em>The point of saving something for later is to make later easier.</em></p><h3>4. Keep your digital life simple and private</h3><p>Productivity tools can become surprisingly demanding.</p><p>An app designed to organize information can introduce its own categories, workflows, notifications, and maintenance tasks. Before long, managing the system becomes another job.</p><p>Refind takes a minimalist approach.</p><p>Its purpose is clear: help you save and rediscover web content without making bookmark management more complicated than it needs to be.</p><p>Privacy is another important part of the product’s positioning. Your personal collection of links should be treated as something valuable, not as an excuse to add unnecessary complexity to your digital life.</p><p>Refind is designed around a fast, private, focused experience.</p><p>The broader philosophy is simple: useful software should help you accomplish something without demanding more attention than necessary.</p><h3>5. Who is Refind for?</h3><p>Refind is useful for anyone who regularly discovers information they want to revisit.</p><p><strong>Developers and designers</strong></p><p>Keep track of documentation, technical articles, design inspiration, libraries, tools, and tutorials you might need for future projects.</p><p><strong>Students and researchers</strong></p><p>Collect useful reading material and online references while exploring a subject. Instead of relying on browser history alone, maintain a dedicated collection of links worth revisiting.</p><p><strong>Writers and content creators</strong></p><p>Save ideas, references, articles, and resources that might inform future content or creative projects.</p><p><strong>People who love discovering things online</strong></p><p>Keep interesting websites, recipes, videos, articles, and other useful resources together rather than leaving them scattered across different platforms.</p><p><strong>Anyone overwhelmed by bookmarks</strong></p><p>If you’ve ever searched for a link you know you’ve saved somewhere, you already understand the problem Refind is trying to solve.</p><p>You don’t need to be a productivity enthusiast to benefit from a better way to save things.</p><p>You just need to find things online that you don’t want to lose.</p><h3>Why I decided to build Refind</h3><p>Refind is an independent product built around a small but meaningful problem.</p><p>It’s easy to build software that adds more features, more options, and more complexity. It’s harder to identify a recurring frustration and create a focused tool that addresses it without introducing unnecessary work.</p><p>The challenge with bookmarks isn’t that people don’t know how to save a link.</p><p>They already do it every day.</p><p>The challenge is that saving is often disconnected from rediscovery. We collect information with good intentions, but the collection doesn’t always help us when we need it.</p><p>I wanted Refind to focus on that gap.</p><p>A bookmark manager doesn’t need to become an entire productivity platform. It needs to make an everyday task easier and help people get more value from the things they discover.</p><p>As an independent developer, building Refind also means making deliberate decisions about what belongs in the product and what doesn’t.</p><p>A feature should serve the central experience, not simply make the feature list longer.</p><p>The aim is to build something people can understand quickly, incorporate into their daily habits, and return to because it genuinely helps.</p><h3>A note about Refind Pro</h3><p>Refind is a premium product, and <strong>all Refind Pro features require a separate purchase through the App Store</strong>.</p><p>The purchase model is an intentional part of how the product is presented: users should understand what requires payment before deciding whether Refind fits their workflow.</p><p>If you’re considering a new bookmark manager, review the available features and purchase details to determine whether it meets your needs.</p><p>The most important measure of value isn’t how many features an app advertises. It’s whether the app solves a problem you experience often enough to justify using it.</p><h3>The bigger idea: save less time searching, spend more time using what you find</h3><p>Think about the links you’ve saved over the last month.</p><p>Some might help you solve a technical problem. Others might teach you something new, inspire a project, help you make a decision, or simply make your day more enjoyable.</p><p>Those links have value because of what they can help you do.</p><p>But that value is difficult to realize if you can’t find them again.</p><p>A useful personal collection shouldn’t be a digital graveyard of things you once intended to read. It should be a resource you can return to when curiosity, work, or life calls for it.</p><p>That’s the problem Refind is built to address.</p><p>Discover something useful. Save it for later. Find your way back when it matters.</p><p>The web will keep giving us more things worth remembering. We need better ways to keep track of the ones that matter to us.</p><p><strong>Refind is my attempt to make that a little easier.</strong></p><p>If you’ve ever lost a useful link in a sea of bookmarks, I’d love to hear about your experience.</p><p>What do you save most often: articles, videos, recipes, developer tools, or something else?</p><p>And more importantly, how do you find those things again?</p><p><a href="https://heyidb.com/refind"><em>Refind</em></a><em> Bookmark Organizer &amp; Offline Link Saver.</em></p><p>Explore Refind and see whether it fits your workflow. Review the available features and purchase details before getting started.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0d2f0dc16fbf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We2 Reached 502 New Customers and 786 Active Users With $0 in Ad Spend]]></title>
            <link>https://medium.com/@basavaraja-dev/we2-reached-502-new-customers-and-786-active-users-with-0-in-ad-spend-22d39b2da918?source=rss-1516ae19b56------2</link>
            <guid isPermaLink="false">https://medium.com/p/22d39b2da918</guid>
            <category><![CDATA[relationships-love-dating]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Basavaraja V]]></dc:creator>
            <pubDate>Sat, 03 Oct 2026 13:01:03 GMT</pubDate>
            <atom:updated>2026-10-03T13:01:03.459Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mk36ZBUooox3FNlvXhQQ1g.png" /><figcaption>credit chatgpt</figcaption></figure><p>Building a consumer app is one thing.</p><p>Getting people to discover it <strong>without paying for ads</strong> is a completely different challenge.</p><p>Over the last 28 days, <strong>We2</strong> reached:</p><ul><li><strong>502 new customers</strong></li><li><strong>786 active users</strong></li><li><strong>$0 spent on advertising</strong></li></ul><p>And honestly, this is one of the most encouraging milestones we’ve had so far.</p><h3>We2 is built around one simple idea</h3><p>Relationships can become repetitive.</p><p>You love someone, but sometimes you run out of things to talk about.</p><p>“What’s your favorite memory?”</p><p>“How was your day?”</p><p>“What do you want to do this weekend?”</p><p>The conversations are important, but they can become predictable.</p><p>That’s why we built <strong>We2</strong> — an app designed to help couples have more meaningful conversations through questions, quizzes, and conversation prompts.</p><p>The goal isn’t to replace real conversations.</p><p>It’s to <strong>start better ones</strong>.</p><h3>The interesting part: $0 in ad spend</h3><p>The numbers above aren’t the result of a large advertising campaign.</p><p>There wasn’t a huge paid acquisition budget behind them.</p><p>We’ve been experimenting with organic distribution:</p><ul><li>Sharing useful relationship content</li><li>Creating short-form videos</li><li>Posting conversation questions</li><li>Participating in relevant communities</li><li>Learning what couples actually respond to</li><li>Improving the product based on user behavior</li></ul><p>Some posts work.</p><p>Some completely flop.</p><p>And occasionally, something connects.</p><p>That’s the part of building a product that I find fascinating.</p><p>You can spend days building a feature that nobody notices.</p><p>Then a simple post can suddenly bring hundreds of people to your product.</p><h3>502 new customers</h3><p>Seeing <strong>502 new customers in 28 days</strong> is exciting.</p><p>But the number I care about even more is the relationship between acquisition and engagement.</p><p>We had <strong>786 active users over the same 28-day period</strong>.</p><p>That tells us people aren’t only discovering We2 — there is activity happening inside the product as well.</p><p>There is still a huge amount to improve.</p><p>Acquisition is only the beginning.</p><p>The real challenge is getting someone to come back tomorrow, next week, and next month.</p><h3>We’re still very early</h3><p>We2 isn’t a massive company.</p><p>There isn’t a huge marketing team behind it.</p><p>It’s being built and grown with a very small team — which means every new user teaches us something.</p><p>Which question gets opened?</p><p>Which screen makes people continue?</p><p>Where do people drop off?</p><p>What makes someone share the app with their partner?</p><p>What makes a couple come back?</p><p>Those questions are becoming more important than vanity metrics.</p><h3>What we’re learning about organic growth</h3><p>One lesson is becoming increasingly clear:</p><p><strong>You don’t always need a huge marketing budget to start growing a product.</strong></p><p>You need something people can understand quickly.</p><p>For We2, the message is simple:</p><blockquote><strong><em>Give couples something meaningful to talk about.</em></strong></blockquote><p>That makes the product naturally suited to content.</p><p>A single question can become a post.</p><p>A post can become a Reel.</p><p>A Reel can start a conversation.</p><p>And that conversation can introduce someone to We2.</p><p>That’s the loop we’re trying to build.</p><h3>What’s next?</h3><p>502 new customers is not the destination.</p><p>786 active users isn’t either.</p><p>We’re going to keep working on:</p><p><strong>Better questions → better conversations → better retention → more organic sharing.</strong></p><p>The goal is to turn We2 from an app people discover into an app couples <strong>come back to regularly</strong>.</p><p>For now, we’re just happy to see the graph moving in the right direction.</p><p>And the fact that we’ve done it with <strong>$0 in ad spend</strong> makes this milestone especially meaningful.</p><p><strong>502 new customers.<br>786 active users.<br>$0 in ads.</strong></p><p>Just getting started. ❤️</p><p><strong>Try We2:</strong> <a href="https://heyidb.com/we2">https://heyidb.com/we2</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22d39b2da918" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Built Refind Because My Bookmarks Became a Graveyard]]></title>
            <link>https://medium.com/@basavaraja-dev/i-built-refind-because-my-bookmarks-became-a-graveyard-16d73f98b412?source=rss-1516ae19b56------2</link>
            <guid isPermaLink="false">https://medium.com/p/16d73f98b412</guid>
            <category><![CDATA[productivity-apps]]></category>
            <category><![CDATA[android-apps]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Basavaraja V]]></dc:creator>
            <pubDate>Fri, 02 Oct 2026 16:14:27 GMT</pubDate>
            <atom:updated>2026-10-02T16:14:27.555Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e52KnHgoOkyknu7xUK9ltw.png" /><figcaption>credit chatgpt</figcaption></figure><p><a href="https://heyidb.com/refind"><strong>Refind</strong></a><strong> is finally live on Google Play. 🚀</strong></p><p>For years, I saved links with the best intentions.</p><p>An interesting article.</p><p>A useful tutorial.</p><p>A YouTube video I wanted to watch later.</p><p>A recipe.</p><p>A product I wanted to buy.</p><p>A programming solution I knew I would need again.</p><p>A post I didn’t have time to read.</p><p>The problem wasn’t saving them.</p><p>The problem was <strong>finding them again</strong>.</p><h3>The bookmark graveyard</h3><p>My browser bookmarks slowly turned into a huge collection of links.</p><p>Some were carefully organized.</p><p>Most weren’t.</p><p>After a while, the pattern became predictable:</p><blockquote><em>“I know I saved that link somewhere…”</em></blockquote><p>Then I’d search through bookmarks.</p><p>Nothing.</p><p>I’d search my browser history.</p><p>Still nothing.</p><p>Then I’d search Google again.</p><p>Sometimes I&#39;d find the original page faster than I could find it in my own bookmarks.</p><p>I also tried other approaches.</p><p>Google Keep.</p><p>Notion.</p><p>A private Telegram chat.</p><p>Dedicated bookmark and read-later apps.</p><p>They all solved parts of the problem, but I kept feeling the same friction.</p><p>Some felt too much like reading apps.</p><p>Others required too much organization.</p><p>Others became another system I had to maintain.</p><p>I wanted something much simpler.</p><h3>What if saving a link was actually the easy part?</h3><p>That became the idea behind <strong>Refind</strong>.</p><p>The goal isn&#39;t to create another complicated productivity system.</p><p>It&#39;s simply:</p><p><strong>Save it now. Find it later.</strong></p><p>You can save links that matter to you and organize them so they&#39;re easier to find when you actually need them.</p><p>Articles.</p><p>Videos.</p><p>Recipes.</p><p>Tutorials.</p><p>Research.</p><p>Products.</p><p>Websites.</p><p>Anything you want to come back to.</p><h3>Built around a simple principle</h3><p>I wanted Refind to feel closer to a personal shelf than another productivity dashboard.</p><p>You shouldn&#39;t need to spend five minutes deciding where a link belongs before saving it.</p><p>You shouldn&#39;t need to build a complicated database.</p><p>And you shouldn&#39;t have to remember exactly where you saved something months ago.</p><p>The product is intentionally focused around the basic workflow:</p><p><strong>Save → Organize → Find</strong></p><p>That&#39;s it.</p><h3>Why I built it</h3><p>I&#39;m a solo developer, so every product I build forces me to make choices about what actually matters.</p><p>It&#39;s very easy to keep adding features.</p><p>Sync.</p><p>AI.</p><p>Dashboards.</p><p>Automation.</p><p>Integrations.</p><p>Social features.</p><p>Complex categorization.</p><p>But sometimes the better product is the one that removes complexity instead of adding it.</p><p>With Refind, I wanted to start with the fundamental problem first:</p><blockquote><strong><em>How can I help someone save something today and actually find it again later?</em></strong></blockquote><p>Everything else comes after that.</p><h3>Finally live on Google Play</h3><p>After building, testing, fixing bugs, preparing the store listing, and waiting for Google&#39;s review, Refind finally passed review and is now publicly available on Google Play.</p><p>That moment felt surprisingly different from simply finishing the code.</p><p>Because when you&#39;re building alone, the app can spend months existing mostly on your computer.</p><p>Then suddenly:</p><p><strong>It&#39;s public.</strong></p><p>Real people can install it.</p><p>Real people can use it.</p><p>And, perhaps most importantly, real people can tell you whether the idea actually makes sense.</p><h3>Now the real work begins</h3><p>Launching isn&#39;t the finish line.</p><p>It&#39;s the beginning of the experiment.</p><p>I want to learn:</p><ul><li>Do people actually have this bookmark problem?</li><li>What kinds of links do they save most?</li><li>Do they come back to their saved links?</li><li>What makes them organize something?</li><li>Where does the experience feel unnecessary?</li><li>What would make them use Refind every day?</li></ul><p>Those answers will be much more valuable than anything I can predict while sitting in front of my editor.</p><p>So I&#39;m starting small.</p><p>Build something useful.</p><p>Put it in people&#39;s hands.</p><p>Listen.</p><p>Improve.</p><p>Repeat.</p><h3>What&#39;s next?</h3><p>I&#39;m going to focus on making Refind genuinely useful before trying to turn it into a giant productivity platform.</p><p>The long-term vision is simple:</p><p><strong>Your personal place for the things you find on the internet and don&#39;t want to lose.</strong></p><p>If you&#39;ve ever saved hundreds of links and later wondered <em>“Where the hell did I save that?”</em> you already understand why I built this.</p><p><a href="https://heyidb.com/refind"><strong>Refind</strong></a><strong> is now live on Google Play. 🚀</strong></p><p>And this is just the beginning.</p><p><em>I&#39;m a solo developer building Refind and documenting what happens along the way from the first users to the first paying customers and everything I learn in between.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16d73f98b412" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Built Awwly From Scratch: From a Simple Idea to a Real App]]></title>
            <link>https://medium.com/@basavaraja-dev/i-built-awwly-from-scratch-from-a-simple-idea-to-a-real-app-d669176a67aa?source=rss-1516ae19b56------2</link>
            <guid isPermaLink="false">https://medium.com/p/d669176a67aa</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[awwly]]></category>
            <category><![CDATA[shipaton]]></category>
            <category><![CDATA[indiehackers]]></category>
            <category><![CDATA[build-in-public]]></category>
            <dc:creator><![CDATA[Basavaraja V]]></dc:creator>
            <pubDate>Sat, 29 Aug 2026 15:31:01 GMT</pubDate>
            <atom:updated>2026-08-29T15:31:01.356Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U0SV7-N0Kbef7SPn9YFECQ.png" /></figure><p><em>What started as a tiny idea about making meaningful moments turned into a journey through product design, AI, monetization, App Store review, security, and finally shipping.</em></p><p>There is something strangely satisfying about seeing an app you built yourself sitting on a real app store.</p><p>Not a prototype.</p><p>Not a Figma file.</p><p>Not a localhost URL.</p><p>A <strong>real app that someone can download and use.</strong></p><p>That feeling is exactly why I started building <strong>Awwly</strong>. ❤️</p><p>And this is the story of how I got there.</p><h3>It started with a simple question</h3><p>I kept thinking about something very human:</p><p><strong>What if creating something meaningful for someone didn’t have to be difficult?</strong></p><p>We send messages every day.</p><p>“Happy Birthday ❤️”</p><p>“Happy Anniversary.”</p><p>“Thank you.”</p><p>“Miss you.”</p><p>“Thinking of you.”</p><p>But sometimes a simple text doesn’t feel like enough.</p><p>You want to give someone something that feels a little more personal.</p><p>Something they might save.</p><p>Something they might look back at.</p><p>Something that says:</p><blockquote>I actually put thought into this.</blockquote><p>That became the idea behind Awwly.</p><p><strong>Turn feelings into beautiful moments.</strong></p><h3>From idea to product</h3><p>The first version of Awwly was nowhere near what it is today.</p><p>Like most products, the idea became clearer only after I started building it.</p><p>I had to figure out:</p><ul><li>What should Awwly actually create?</li><li>Who is it for?</li><li>What makes someone want to use it?</li><li>What should be free?</li><li>What should people pay for?</li><li>How should the experience feel?</li><li>How do I make the product feel emotional rather than technical?</li></ul><p>And perhaps the biggest question:</p><p><strong>Would anyone actually care?</strong></p><p>That’s something you can’t answer in a spreadsheet.</p><p>You have to ship.</p><h3>Designing for emotion instead of features</h3><p>One of the biggest decisions I made was to avoid making Awwly feel like another generic AI utility.</p><p>I didn’t want the experience to scream:</p><p><strong>“AI-powered image generator.”</strong></p><p>That’s a feature.</p><p>The outcome is much more interesting:</p><p><strong>“I made something beautiful for someone I love.”</strong></p><p>That’s what I wanted people to feel.</p><p>So the design direction became much more emotional.</p><p>Soft gradients.</p><p>Warm colors.</p><p>Hearts.</p><p>Beautiful imagery.</p><p>Simple language.</p><p>Very little technical terminology.</p><p>The product should feel like you’re creating a little gift — not operating a piece of software.</p><h3>The four-second test</h3><p>I started thinking about the product from the perspective of someone seeing it for the first time.</p><p>They shouldn’t need a tutorial to understand the value.</p><p>They should immediately understand:</p><p><strong>I can create something meaningful for someone.</strong></p><p>That thinking also influenced the App Store screenshots.</p><p>Instead of filling screenshots with feature lists, I wanted to communicate outcomes.</p><p>For example:</p><h3>Make moments unforgettable</h3><h3>Made just for them</h3><h3>From your words to their smile</h3><h3>For every special moment</h3><p>The goal wasn’t to explain the technology.</p><p>The goal was to make someone imagine the person they’re going to create it for.</p><h3>Then came monetization</h3><p>This was one of the more interesting parts of the journey.</p><p>Awwly needed a business model.</p><p>I experimented with the idea of subscriptions and eventually moved toward something that made more sense for the product:</p><p><strong>credits.</strong></p><p>The concept is simple.</p><p>Users can create moments using credits.</p><p>Instead of forcing someone into a recurring subscription just to make something special for someone, they can purchase credits when they need them.</p><p>That felt much more natural for this particular product.</p><h3>Building the credit system securely</h3><p>This is where the project became much more serious technically.</p><p>Once real money is involved, you can’t simply trust the client.</p><p>You have to assume that someone will eventually try to manipulate it.</p><p>So the mindset became:</p><blockquote><strong><em>Never trust the app running on the user’s device.</em></strong></blockquote><p>The client can request a purchase.</p><p>The backend needs to determine what actually happened.</p><p>Credits need to be handled carefully.</p><p>Purchase validation needs to happen through trusted systems.</p><p>And the app shouldn’t simply say:</p><blockquote><em>“I have 100 credits now.”</em></blockquote><p>and blindly believe itself.</p><p>This led me to spend considerably more time thinking about:</p><ul><li>Purchase verification</li><li>Server-side credit handling</li><li>Replay/tampering protection</li><li>Idempotency</li><li>User identity</li><li>Secure APIs</li><li>Abuse prevention</li><li>Free-credit limits</li><li>RevenueCat integration</li></ul><p>It wasn’t the most glamorous part of building Awwly.</p><p>But it was one of the most important.</p><h3>RevenueCat became part of the puzzle</h3><p>I integrated <strong>RevenueCat</strong> to make the purchase infrastructure manageable across platforms.</p><p>The goal was to have a consistent product catalog across:</p><p>🍎 iOS<br>🤖 Android</p><p>That meant setting up products, packages, offerings, and eventually the paywall.</p><p>I also wanted the purchase flow to be flexible enough that I could improve the pricing and presentation without having to completely rebuild the app every time.</p><p>This is one of those things you appreciate much more after you’ve built a few products.</p><p><strong>Infrastructure decisions matter.</strong></p><h3>Designing the paywall</h3><p>The first paywall was functional.</p><p>But functional isn’t enough.</p><p>A user needs to understand:</p><p><strong>“What do I get if I buy this?”</strong></p><p>So I redesigned the paywall around outcomes rather than technical explanations.</p><p>Instead of:</p><blockquote><em>Buy credits.</em></blockquote><p>The experience should communicate:</p><blockquote><strong><em>Make more moments ❤️</em></strong></blockquote><p>And then make the value of each option obvious.</p><p>10 credits.</p><p>30 credits.</p><p>100 credits.</p><p>Simple.</p><p>Visual.</p><p>Easy to understand.</p><p>No complicated pricing explanation.</p><p>The paywall should feel like part of Awwly — not a payment screen that was bolted onto it later.</p><h3>Giving people a chance to experience Awwly</h3><p>I also wanted users to experience the product before asking them to pay.</p><p>So Awwly includes free creations.</p><p>That’s important because there’s a big difference between telling someone:</p><blockquote><em>“This app is great.”</em></blockquote><p>and letting them experience it themselves.</p><p>The second one is much more powerful.</p><p>The user can create something, see the result, and then decide whether Awwly is worth paying for.</p><h3>Then came the App Store and Play Store</h3><p>This part is surprisingly time-consuming.</p><p>You build the app.</p><p>You think you’re almost finished.</p><p>Then you discover there’s another mountain waiting for you. 😅</p><p>App Store Connect.</p><p>Google Play Console.</p><p>Privacy declarations.</p><p>Data safety.</p><p>Product metadata.</p><p>In-app purchases.</p><p>Screenshots.</p><p>Feature graphics.</p><p>Store descriptions.</p><p>Categories.</p><p>Keywords.</p><p>App privacy.</p><p>TestFlight.</p><p>Open testing.</p><p>Review requirements.</p><p>There are dozens of small things that have nothing to do with writing code but are absolutely necessary to launch a real product.</p><h3>Learning App Store SEO</h3><p>I also spent a lot of time thinking about how someone would actually discover Awwly.</p><p>The app name became:</p><p><strong>Awwly: Love &amp; Gift Cards</strong></p><p>And the positioning focused around things people might actually search for:</p><p>Love.</p><p>Gifts.</p><p>Cards.</p><p>Moments.</p><p>Greetings.</p><p>Celebrations.</p><p>Messages.</p><p>The challenge is finding the balance between:</p><p><strong>What sounds beautiful</strong></p><p>and</p><p><strong>What people actually search for.</strong></p><p>That’s a completely different problem from designing the product itself.</p><h3>The security audit</h3><p>Before launch, I didn’t want to simply assume everything was safe.</p><p>So I went through the app with a different mindset:</p><p><strong>“If I wanted to break this, how would I do it?”</strong></p><p>That changed the questions I was asking.</p><p>Can someone modify the client?</p><p>Can someone fake credits?</p><p>Can someone replay a purchase?</p><p>Can someone call an API directly?</p><p>Can someone bypass a free limit?</p><p>Can someone manipulate an identifier?</p><p>Can someone repeatedly trigger an expensive operation?</p><p>Thinking like an attacker is uncomfortable.</p><p>But it’s incredibly useful.</p><p>Especially when your app has a credit system attached to real money.</p><h3>And then came the moment…</h3><p>After all of that:</p><p><strong>Awwly shipped.</strong> 🚀</p><p>Android is now live on Google Play.</p><p><a href="https://play.google.com/store/apps/details?id=com.heyidb.awwly&amp;utm_source=chatgpt.com">Try Awwly on Google Play</a></p><p>The iOS version is currently waiting for App Store review, and the TestFlight build is available for testing.</p><p><a href="https://testflight.apple.com/join/PGNrj2b5?utm_source=chatgpt.com">Join Awwly on TestFlight</a></p><p>Seeing those links exist is honestly a strange feeling.</p><p>Because behind those links are weeks of decisions.</p><p>Thousands of lines of code.</p><p>Design iterations.</p><p>Bugs.</p><p>Build failures.</p><p>Pricing decisions.</p><p>Security concerns.</p><p>Store requirements.</p><p>And plenty of:</p><p><strong>“Why isn’t this working?”</strong> 😅</p><h3>I’m building Awwly as part of Shipaton</h3><p>I’m also participating in <strong>Shipaton</strong>, which gave me an extra reason to stop endlessly tweaking and actually ship.</p><p>That’s something I’ve learned repeatedly as an indie developer:</p><blockquote><strong><em>A finished imperfect product teaches you more than a perfect product that never ships.</em></strong></blockquote><p>Before launching, you can predict.</p><p>After launching, you can observe.</p><p>And observation wins.</p><p>Now I get to see what real users do.</p><p>Where they get confused.</p><p>What they love.</p><p>What they ignore.</p><p>What they create.</p><p>What they’re willing to pay for.</p><p>And, perhaps most importantly:</p><p><strong>whether the original idea actually resonates.</strong></p><h3>What I learned building Awwly</h3><h3>1. Building is the easy part</h3><p>Writing code is often the most straightforward part.</p><p>The harder questions are:</p><p><strong>What should I build?</strong></p><p><strong>Who is it for?</strong></p><p><strong>Why would they care?</strong></p><p><strong>Why would they pay?</strong></p><h3>2. Features don’t sell outcomes do</h3><p>People don’t necessarily want “AI generation.”</p><p>They want:</p><p><strong>“I made something special for my partner.”</strong></p><p>They don’t want “credit management.”</p><p>They want:</p><p><strong>“I can keep creating beautiful moments.”</strong></p><p>The technology enables the outcome.</p><p>The outcome is what matters.</p><h3>3. Shipping changes everything</h3><p>When an app is private, every decision feels theoretical.</p><p>Once it’s public, reality starts giving you answers.</p><p>That’s why I’m excited about the next phase of Awwly.</p><p>Not because it’s finished.</p><p>But because <strong>now the real learning begins.</strong></p><h3>What’s next?</h3><p>Honestly?</p><p>I don’t know everything yet.</p><p>And that’s exciting.</p><p>The next stage is going to be about listening.</p><p>Watching user behavior.</p><p>Collecting feedback.</p><p>Improving the creation experience.</p><p>Improving conversion.</p><p>Improving the quality of the moments people create.</p><p>And figuring out whether Awwly can become more than just another app sitting on someone’s phone.</p><p>I want it to become something people think of when they want to say:</p><p><strong>“I want to make this moment special.”</strong></p><h3>From a blank screen to a real product</h3><p>When I started Awwly, there was no app.</p><p>Just an idea.</p><p>Then there was a folder.</p><p>Then some code.</p><p>Then a prototype.</p><p>Then designs.</p><p>Then bugs.</p><p>Then payments.</p><p>Then security.</p><p>Then store listings.</p><p>Then testing.</p><p>And eventually…</p><p><strong>a real app.</strong></p><p>That’s the part of building that I love.</p><p>You start with something that exists only in your head.</p><p>And little by little, you make it real.</p><p>Awwly is still very early.</p><p>There is a long way to go.</p><p>But today, I can finally say:</p><p><strong>I shipped it. ❤️</strong></p><p>And now the next chapter begins.</p><h3>Try Awwly</h3><p>🤖 <strong>Android:</strong> <a href="https://play.google.com/store/apps/details?id=com.heyidb.awwly&amp;utm_source=chatgpt.com">Awwly on Google Play</a></p><p>🍎 <strong>iOS:</strong> <a href="https://testflight.apple.com/join/PGNrj2b5?utm_source=chatgpt.com">Awwly on TestFlight</a></p><p>If you try it, I’d genuinely love to hear what you think — especially <strong>what feels magical, what feels confusing, and what you’d change.</strong></p><p>That’s how Awwly will get better.</p><p><strong>Tags:</strong> #BuildInPublic #Shipaton #IndieHackers #IndieDev #MobileApp #Startup #Solopreneur #AppDevelopment #Awwly #ProductDevelopment</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d669176a67aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Thought Launching My App Would Feel Like the End. It Felt Like the Beginning Instead.]]></title>
            <link>https://medium.com/@basavaraja-dev/i-thought-launching-my-app-would-feel-like-the-end-it-felt-like-the-beginning-instead-c6ea978f755a?source=rss-1516ae19b56------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6ea978f755a</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[productivity-hacks]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Basavaraja V]]></dc:creator>
            <pubDate>Wed, 05 Aug 2026 06:30:36 GMT</pubDate>
            <atom:updated>2026-08-05T06:30:36.245Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ou5VUTkcHPvC4JiM3o0jfA.png" /></figure><p>When I started building <strong>Leo: 21 Day Habit Builder</strong>, I thought the hardest part would be the code.</p><p>I was wrong.</p><p>The hardest part turned out to be creating <strong>App Store screenshots</strong> that made someone stop scrolling and think:</p><blockquote>“I want this app.”</blockquote><h3>My First Attempt</h3><p>Like many solo developers, I started with screenshots that simply showed the app.</p><p>A screenshot.<br> A headline.<br> Done.</p><p>Technically, they looked fine.</p><p>But they didn’t tell a story.</p><p>They didn’t answer the most important question:</p><p><strong>Why should someone download Leo instead of another habit app?</strong></p><p>So I started over.</p><h3>Back to the Drawing Board</h3><p>I redesigned every screenshot.</p><p>Then redesigned them again.</p><p>And again.</p><p>Sometimes I changed just one headline.</p><p>Sometimes I spent an hour moving a phone mockup a few pixels because it didn’t feel balanced.</p><p>It sounds ridiculous.</p><p>But tiny details completely change the first impression.</p><h3>Listening Instead of Guessing</h3><p>One of the best decisions I made was sharing every version publicly.</p><p>People pointed out things I never noticed.</p><p>Some said:</p><blockquote><em>“Lead with what makes your app unique.”</em></blockquote><p>Others said:</p><blockquote><em>“These screenshots look nice, but they feel generic.”</em></blockquote><p>That feedback completely changed my approach.</p><p>Instead of talking about features, I started telling a story.</p><h3>The Story I Wanted to Tell</h3><p>Leo isn’t another productivity app with dozens of habits.</p><p>It’s built around one simple idea:</p><p><strong>One goal. One focus. 21 days.</strong></p><p>So the screenshots had to reflect that.</p><p>Instead of overwhelming people with every feature, each screen focused on one message:</p><ul><li>Build habits that stick.</li><li>Focus on one goal.</li><li>Celebrate every milestone.</li><li>See your progress.</li><li>Finish what you start.</li></ul><p>Simple.</p><p>Clear.</p><p>Focused.</p><p>Exactly like the app.</p><h3>Hundreds of Tiny Decisions</h3><p>Creating screenshots wasn’t just about Photoshop.</p><p>It meant thinking about things users might never consciously notice.</p><p>Should reminders all be at 8:00 AM?</p><p>No.</p><p>Real people have different routines.</p><p>Should every challenge be completed?</p><p>No.</p><p>A realistic mix of completed and ongoing goals feels more authentic.</p><p>Should the calendar look perfect?</p><p>Again, no.</p><p>Real progress isn’t perfect.</p><p>Ironically, making the screenshots feel <strong>less perfect</strong> made them feel much more believable.</p><h3>Leo Grew Too</h3><p>Even Leo, the little lion mascot, changed throughout the process.</p><p>His expressions.</p><p>His poses.</p><p>His size.</p><p>Where he appeared.</p><p>He slowly became more than just a character.</p><p>He became part of the product’s personality.</p><h3>The Best Part</h3><p>When I finally uploaded the new screenshots, people immediately noticed the difference.</p><p>Comments shifted from talking about the UI to talking about the <strong>idea</strong>.</p><p>That’s when I realized good screenshots don’t just show an app.</p><p>They communicate its value in a few seconds.</p><h3>My Biggest Lesson</h3><p>As developers, we often spend weeks polishing code that users will never see.</p><p>Meanwhile, we spend only an hour on the thing every potential user sees first.</p><p>If you’re launching an app, don’t treat App Store screenshots as a final task.</p><p>Treat them as part of your product.</p><p>Because for most users…</p><p><strong>The screenshots are the product until they decide to download it.</strong></p><p>I’m still learning, still iterating, and still improving Leo every week.</p><p>If you’re building your own app, I’d love to hear:</p><p><strong>How many times did you redesign your App Store screenshots before you were finally happy with them?</strong> 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6ea978f755a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Launched My First Paid iOS App. Here’s How I’m Marketing It Without Spending $1 on Ads.]]></title>
            <link>https://medium.com/@basavaraja-dev/i-launched-my-first-paid-ios-app-heres-how-i-m-marketing-it-without-spending-1-on-ads-9129b09e697a?source=rss-1516ae19b56------2</link>
            <guid isPermaLink="false">https://medium.com/p/9129b09e697a</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[indie-hacking]]></category>
            <category><![CDATA[app-marketing]]></category>
            <category><![CDATA[productivity-hacks]]></category>
            <category><![CDATA[ios-development]]></category>
            <dc:creator><![CDATA[Basavaraja V]]></dc:creator>
            <pubDate>Mon, 03 Aug 2026 08:37:25 GMT</pubDate>
            <atom:updated>2026-08-03T08:37:25.758Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p5HFbMRiY5ok79TkY0IBJw.png" /><figcaption>This illustration is created using chatgpt</figcaption></figure><h3><strong>Building the app turned out to be the easy part.</strong></h3><p>Getting people to discover it has been the real challenge.</p><p>A few weeks ago, I launched <strong>Leo: 21 Day Habit Builder</strong>, a paid iOS app I built as a solo developer. Like many indie makers, I don’t have a marketing budget, an audience of 100k followers, or a team running campaigns.</p><p>So I asked myself a simple question:</p><blockquote><strong><em>How can one person consistently get downloads without paying for ads?</em></strong></blockquote><p>After a lot of experimenting, here’s the marketing stack I’m committing to.</p><h3>1. Build a Product People Can Explain in One Sentence</h3><p>I’ve realized that marketing becomes much easier when people understand your product instantly.</p><p>Instead of saying:</p><blockquote><em>“Leo is a habit tracker.”</em></blockquote><p>I say:</p><blockquote><strong><em>One goal. One focus. 21 days.</em></strong></blockquote><p>That’s it.</p><p>People immediately understand the difference.</p><p>The simpler your positioning, the easier every tweet, Reddit post, and conversation becomes.</p><h3>2. Market the Problem, Not the App</h3><p>Nobody wakes up thinking:</p><blockquote><em>“I need another habit tracker.”</em></blockquote><p>People wake up thinking:</p><ul><li>I keep procrastinating.</li><li>I can’t stay consistent.</li><li>I always quit after a week.</li><li>I wish I had more discipline.</li></ul><p>That’s what I write about.</p><p>Instead of posting:</p><blockquote><em>“Download Leo.”</em></blockquote><p>I write:</p><ul><li>Why I kept quitting habit apps.</li><li>Why trying to build ten habits never worked.</li><li>Why focusing on one goal changed everything.</li></ul><p>The app becomes part of the story not the story itself.</p><h3>3. Reddit Is Better Than Chasing Viral Tweets</h3><p>The most valuable traffic I’ve received hasn’t come from social media algorithms.</p><p>It has come from communities.</p><p>People ask thoughtful questions.</p><p>They challenge assumptions.</p><p>They share their own experiences.</p><p>One discussion about habit psychology often leads to more meaningful users than thousands of random impressions.</p><p>The biggest lesson:</p><p><strong>Participate first. Promote second.</strong></p><h3>4. Build in Public</h3><p>As a solo developer, I don’t have a marketing team.</p><p>My development process <em>is</em> my marketing.</p><p>I share:</p><ul><li>UI redesigns</li><li>App Store screenshots</li><li>Product decisions</li><li>Mistakes</li><li>User feedback</li><li>Launch milestones</li></ul><p>People enjoy following the journey as much as the product itself.</p><h3>5. Create Something People Want to Share</h3><p>Downloads are great.</p><p>Recommendations are even better.</p><p>Every product should answer one question:</p><blockquote><strong><em>What makes someone tell a friend about this?</em></strong></blockquote><p>For Leo, I’m working toward making every completed challenge feel share-worthy.</p><p>When someone reaches Day 21, I want them to feel proud enough to share it.</p><p>Word of mouth has always been the cheapest marketing.</p><h3>6. Don’t Build for Everyone</h3><p>One of my biggest mistakes in previous projects was trying to appeal to everyone.</p><p>Leo has one clear promise:</p><p><strong>One goal. One focus. 21 days.</strong></p><p>That won’t appeal to every productivity enthusiast.</p><p>And that’s okay.</p><p>Clear positioning beats broad positioning.</p><h3>7. Launch Before You’re Comfortable</h3><p>I kept finding things to improve.</p><p>One more animation.</p><p>One more setting.</p><p>One more screen.</p><p>Eventually I realized something:</p><p>Users give better feedback than assumptions.</p><p>So I launched.</p><p>The first Reddit comments changed my roadmap more than weeks of planning.</p><h3>8. Reviews Matter More Than I Expected</h3><p>After launch, I discovered that getting the first 25–50 App Store reviews is surprisingly difficult.</p><p>Building the app took months.</p><p>Convincing someone to spend 30 seconds writing a review is another challenge entirely.</p><p>It’s reminded me that shipping isn’t the finish line.</p><p>It’s the beginning.</p><h3>9. Consistency Beats Big Launches</h3><p>One Product Hunt launch is exciting.</p><p>One viral Reddit post is exciting.</p><p>But neither builds a business.</p><p>Showing up every day does.</p><p>I’d rather publish:</p><ul><li>one useful article</li><li>one thoughtful Reddit discussion</li><li>one small product improvement</li></ul><p>every day than hope for a single viral moment.</p><h3>What I’m Focusing on Next</h3><p>My goals over the next few months are simple:</p><ul><li>Earn my first 50 App Store reviews.</li><li>Keep improving retention.</li><li>Publish consistently.</li><li>Listen to users.</li><li>Build a product people genuinely recommend.</li></ul><p>I’m still learning.</p><p>Some ideas will fail.</p><p>Some experiments won’t move the needle.</p><p>But that’s part of being a solo founder.</p><h3>Final Thoughts</h3><p>I’ve stopped thinking of marketing as convincing people to download my app.</p><p>Instead, I think of it as <strong>joining conversations about problems I genuinely care about.</strong></p><p>If the product solves those problems well, people will naturally become interested.</p><p>That’s a much more sustainable strategy than chasing hacks or spending money I don’t have.</p><p>If you’re a solo developer, I’d love to hear from you:</p><p><strong>What’s one marketing channel that’s actually worked for your product?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9129b09e697a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Spent Weeks Obsessing Over App Store Conversion. The Real Problem Was Somewhere Else.]]></title>
            <link>https://medium.com/@basavaraja-dev/i-spent-weeks-obsessing-over-app-store-conversion-the-real-problem-was-somewhere-else-d7a9c547a91b?source=rss-1516ae19b56------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7a9c547a91b</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[app-store-optimization]]></category>
            <category><![CDATA[indie-hacking]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Basavaraja V]]></dc:creator>
            <pubDate>Mon, 01 Jun 2026 07:26:34 GMT</pubDate>
            <atom:updated>2026-06-01T07:26:34.358Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1mj2PH6DFRB4Nv1qxDwcDg.png" /></figure><p>A few weeks ago, I was convinced I had broken my app.</p><p>Every morning I’d open App Store Connect and stare at my conversion numbers.</p><p>One day it was 20%.</p><p>A few days later it was 2%.</p><p>Then 1%.</p><p>Then back to 7%.</p><p>I started doing what every indie developer does when numbers go down:</p><ul><li>Changed screenshots</li><li>Tweaked metadata</li><li>Ran product page optimization tests</li><li>Rewrote copy</li><li>Compared competitors</li><li>Questioned every decision I’d made</li></ul><p>I thought I had a conversion problem.</p><p>I was wrong.</p><h3>The Data That Sent Me Into Panic Mode</h3><p>I’m building a couples app called We2.</p><p>Like many solo founders, I check metrics more often than I should.</p><p>My daily App Store conversion numbers looked terrible:</p><ul><li>May 22: 1.09%</li><li>May 23: 2.04%</li><li>May 24: 1.96%</li><li>May 25: 2.61%</li><li>May 26: 1.00%</li></ul><p>Looking only at those numbers, you’d assume the product page was failing.</p><p>I certainly did.</p><h3>Then I Looked At Product Page Views</h3><p>The same days had:</p><ul><li>5 product page views</li><li>6 product page views</li><li>5 product page views</li><li>7 product page views</li><li>5 product page views</li></ul><p>Suddenly everything clicked.</p><p>With only five visitors:</p><ul><li>0 installs = 0% conversion</li><li>1 install = 20% conversion</li></ul><p>My conversion rate wasn’t actually changing much.</p><p>The sample size was too small.</p><p>I had spent weeks optimizing noise.</p><h3>The Benchmark Report Changed Everything</h3><p>Then I looked at RevenueCat benchmarks.</p><p>The results surprised me.</p><h3>App Store Initial Conversion</h3><p>60th–70th percentile</p><h3>Play Store Initial Conversion</h3><p>80th–90th percentile</p><h3>Refund Rate</h3><p>90th–100th percentile</p><h3>LTV Per Paying Customer</h3><p>80th–90th percentile</p><p>Those are not the metrics of a broken product page.</p><p>Those are not the metrics of an app people hate.</p><h3>The Real Problem</h3><p>The benchmark report highlighted two weak areas:</p><h3>Trial Conversion</h3><p>Below average.</p><h3>Monthly Churn</h3><p>Below average.</p><p>And suddenly everything made sense.</p><p>Users understood the app.</p><p>Users installed the app.</p><p>Some users paid.</p><p>Paying users often stayed.</p><p>The problem was getting enough people to form a habit.</p><h3>The Mistake Most Indie Founders Make</h3><p>When numbers drop, we immediately focus on acquisition.</p><p>We redesign screenshots.</p><p>We rewrite descriptions.</p><p>We change icons.</p><p>We chase keywords.</p><p>Sometimes that’s the right move.</p><p>But often it’s more comfortable to optimize acquisition because it’s easier than confronting retention.</p><p>It’s easier to change screenshots than to answer:</p><p>“Why aren’t people coming back tomorrow?”</p><h3>What I’m Focusing On Now</h3><p>Instead of spending the next month obsessing over conversion rates, I’m focusing on:</p><h3>Pairing Completion</h3><p>How many users actually connect with their partner?</p><h3>First Value Moment</h3><p>How quickly can a couple experience the app together?</p><h3>Daily Habit Formation</h3><p>What reason do users have to come back tomorrow?</p><h3>Better Trial Timing</h3><p>Am I asking people to pay before they’ve experienced enough value?</p><p>These questions are much harder.</p><p>They’re also much more important.</p><h3>The Lesson</h3><p>If you’re a founder staring at a dashboard right now, ask yourself:</p><p>Are you optimizing the metric that’s easiest to see?</p><p>Or the metric that’s actually holding back growth?</p><p>In my case, I thought I had a conversion problem.</p><p>The data eventually showed me something different.</p><p>I had a retention problem.</p><p>And that’s where the real work begins.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7a9c547a91b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Built and Shipped an AI App as a Solo Developer — Without Touching Xcode Most of the Time]]></title>
            <link>https://medium.com/@basavaraja-dev/i-built-and-shipped-an-ai-app-as-a-solo-developer-without-touching-xcode-most-of-the-time-b2657f0e2205?source=rss-1516ae19b56------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2657f0e2205</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[relationships]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <dc:creator><![CDATA[Basavaraja V]]></dc:creator>
            <pubDate>Thu, 07 May 2026 06:55:06 GMT</pubDate>
            <atom:updated>2026-05-07T06:55:06.056Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JiAn35F4Pkbs6Jsnj0bcFw.png" /><figcaption>illustration from chatgpt</figcaption></figure><p>A few weeks ago, this app didn’t exist.</p><p>It started as a random thought after seeing how many couples struggle with misunderstandings in text conversations. Not because they don’t care about each other — but because tone, timing, and emotions get lost in messages.</p><p>I kept thinking:</p><p>“What if an app could help people understand what actually went wrong in a conversation… and suggest what to say next?”</p><p>Normally, an idea like this would stay in my notes forever.</p><p>Because building an iOS app as a solo developer usually means:</p><ul><li>setting up architecture</li><li>dealing with SwiftUI bugs</li><li>configuring App Store certificates</li><li>creating screenshots</li><li>writing ASO metadata</li><li>implementing monetization</li><li>handling App Review rejections</li></ul><p>…and honestly, that’s where most ideas die.</p><p>This time was different.</p><p>I used <a href="https://mwm.ai/?via=basavaraja&amp;utm_source=chatgpt.com">MWM AI</a> — and it completely changed how I approached app development.</p><p>What surprised me wasn’t just the code generation.</p><p>It was the fact that the platform was designed around the entire app business lifecycle, not just “build UI from prompts.” (<a href="https://mwm.ai/?via=basavaraja">MWM</a>)</p><p>I could:</p><ul><li>generate native Swift app flows</li><li>iterate on UI/UX quickly</li><li>implement monetization</li><li>create App Store metadata</li><li>generate screenshots</li><li>optimize ASO</li><li>prepare the app for publishing</li></ul><p>All in one workflow.</p><p>That changed everything for me.</p><p>Instead of spending weeks wiring infrastructure together, I spent my time improving:</p><ul><li>emotional UX</li><li>onboarding</li><li>paywall timing</li><li>AI prompts</li><li>App Store positioning</li></ul><p>The app eventually became “BetweenUS” — an AI-powered relationship conversation analyzer that helps users:</p><ul><li>understand emotional patterns</li><li>see where conversations escalated</li><li>understand what their partner likely felt</li><li>get a better reply to send</li></ul><p>And after multiple iterations, App Review rejections, redesigns, and late-night fixes…</p><p>…it finally went live on the App Store.</p><p>The biggest lesson I learned wasn’t technical.</p><p>It was this:</p><p>The bottleneck for indie developers is no longer coding.</p><p>It’s:</p><ul><li>shipping</li><li>distribution</li><li>positioning</li><li>iteration speed</li></ul><p>That’s where tools like MWM AI become genuinely powerful.</p><p>Because the real challenge isn’t generating an app.</p><p>It’s turning an idea into a product people can actually download, pay for, and use.</p><p>And for the first time, I felt like I could focus more on the product itself instead of drowning in setup and tooling.</p><p>If you’re a solo developer sitting on app ideas, my advice is simple:</p><p>Ship faster.<br>Learn publicly.<br>Iterate aggressively.</p><p>You’ll learn more from one launched app than from 100 unfinished ideas.</p><p>And honestly, seeing something you imagined appear live on the App Store is still one of the coolest feelings ever.</p><p>App:<br><a href="https://apps.apple.com/in/app/betweenus-relationship-advice/id6766166805?utm_source=chatgpt.com">BetweenUS: Relationship Advice</a></p><p>Platform I used:<br><a href="https://mwm.ai/?via=basavaraja&amp;utm_source=chatgpt.com">MWM AI</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2657f0e2205" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>