Marketing Your Indie App on a Zero Budget

Why paid ads are usually wrong for indie apps

I want to address this upfront because the temptation is strong. You launch your app, get 12 downloads on day one, panic, and think "I just need to get it in front of people." So you set up a $50/day Facebook campaign.

Here's the math problem. The average cost per install from paid ads on iOS is somewhere between $2 and $5 for non-gaming categories. If your app costs $4.99 one-time or $2.99/month, you are paying more to acquire each user than that user will ever give you. You need roughly a 40-60% trial-to-paid conversion rate to break even on paid acquisition at those prices, and most apps sit around 2-5%.

Paid ads work for apps with high lifetime value: dating apps, fintech, enterprise SaaS. If you're building a $3-5/month utility app, organic growth is not just cheaper. It's the only math that works.

ASO is marketing, not a chore

App Store Optimization gets filed under "stuff to do before launch" and then forgotten. That's backwards. ASO is your single highest-leverage marketing channel because it compounds. A well-optimized listing generates installs every day without you doing anything.

I covered the mechanics in the ASO guide, so I won't repeat them here. The point I want to make is about framing. Most solo developers think of ASO as a one-time setup task. The ones who grow treat it as an ongoing marketing activity.

That means updating your screenshots when you ship a new feature. Testing different subtitle copy every few months. Watching which search terms bring traffic and adjusting your keyword field. Localizing your listing for markets where you see organic interest. If you check your App Store Connect analytics and notice you're getting impressions from Japan but your listing is English-only, that's a concrete marketing action you can take today. Our geo-arbitrage scanner exists because this pattern is more common than people think.

One thing that works surprisingly well: making your first screenshot answer a question rather than describe a feature. "Track expenses in 5 seconds" converts better than "Beautiful expense tracker with charts." People in the App Store are scanning, not reading. Your screenshot has about one second to explain why they should tap. The screenshot guide covers this in detail.

Reddit, forums, and the art of not being annoying

Community marketing is the channel indie developers get wrong most often. The failure mode is showing up in r/productivity or r/fitness with a post that says "Hey I built this app, check it out!" and then wondering why it gets downvoted and removed.

The approach that works is slower. You find the communities where your potential users hang out and you participate in them as a person, not as a marketer. Answer questions. Share opinions. Be useful. Then, when it's relevant, mention that you built something related. The difference between spam and a recommendation is whether you've earned the right to recommend.

Specific subreddits that tend to be receptive to indie developers: r/SideProject (made for this), r/iOSProgramming, r/androiddev, r/IndieHackers, and niche subreddits related to your app's category. A meditation app developer I followed lurked in r/Meditation for three months answering questions before posting about their app. The post got 400+ upvotes and drove enough installs to hit #30 in Health & Fitness.

The same principle applies to Indie Hackers, Hacker News, dev.to, and niche Discord servers. Show up as a person first. Promote second. Or don't promote at all and let people find your profile, where you've linked your app. That works too.

Launch platforms: one-day spikes that sometimes stick

Product Hunt, Show HN, Indie Hackers, and similar launch platforms can give you a burst of attention. Whether that burst turns into sustained growth depends on what happens after the spike.

Product Hunt works best for tools that appeal to other builders and early adopters. If your app is a consumer product for normal people (a recipe app, a meditation timer), Product Hunt will get you a lot of curious developers but not many long-term users. Time your launch for Tuesday through Thursday. Prepare five good screenshots and a 60-second demo video. Reply to every comment on launch day.

Show HN rewards technical depth. If your app has an interesting technical angle (unusual architecture, clever data processing, a novel algorithm), write about that. Hacker News readers click on things that teach them something, not on things that sell them something.

The mistake most people make with launch platforms: treating the launch as the event instead of as the beginning of distribution. A Product Hunt launch gets you maybe 500-2000 visitors in one day. That's not enough to sustain a business. What it does give you is social proof (badges, upvotes, comments) and a backlink, both of which help with everything else on this list.

Building in public (when it works and when it's theater)

"Building in public" became a thing around 2020 and the internet is now full of people posting daily revenue screenshots and feature updates to an audience of other people posting daily revenue screenshots and feature updates. Most of these posts get 3 likes and zero downloads.

The version that works is more specific. Instead of narrating your process ("Today I fixed a bug in the settings screen"), share things that are useful or interesting independent of your app. A chart showing retention curves for different onboarding flows. A breakdown of how much App Store review response time affects ratings. A comparison of your conversion rate with and without a free trial. These are things people learn from, and they attach your name to the topic.

The best building-in-public content I've seen follows a pattern: share a number, explain what caused it, describe what you did about it. "Our 7-day retention dropped from 40% to 28% after we added onboarding. We removed two of the four screens and it went back to 37%. The lesson: shorter onboarding beats thorough onboarding." That's something someone can actually use.

Content marketing without a content team

Writing blog posts or making videos about your app's domain is one of the slowest marketing channels. It's also one of the only ones that keeps working after you stop. A blog post that ranks for a search query generates traffic for years. A Reddit post generates traffic for about 48 hours.

The trick is writing about what your users search for, not what you want to tell them. If you built a budget tracking app, don't write "Why I built Yet Another Budget App." Write "How to track spending when you hate spreadsheets" or "The 50/30/20 rule doesn't work if you have student loans." These are things people search for. Your app is the answer to a question they already have.

You don't need to publish often. One genuinely useful article per month is better than four thin ones per week. If you're building an app in a category you understand, you already have opinions and knowledge worth sharing. Write those down in a way that helps someone, mention your app where it's relevant, and let search engines do the distribution.

If writing feels like too much, short-form video works in the same way. A 60-second TikTok or YouTube Short showing a real use case of your app ("Watch me log a week of food in 30 seconds") can reach more people than any blog post, and the barrier to creation is lower.

Reviews are a marketing channel

I wrote a full piece on handling reviews, but the marketing angle is worth repeating here. Every review response is a piece of marketing copy that gets shown to every potential user who scrolls to your reviews section. Which is most of them.

When someone leaves a 1-star review saying "crashes on my iPad," your response is not for that person. It's for the hundred people who will read the review later and wonder if your app is reliable. "Fixed in version 2.3, released yesterday. If you're still seeing this, email me at support@yourapp.com and I'll sort it out" tells future readers that you're responsive and that problems get fixed.

Asking for reviews at the right moment also matters. Don't ask on first launch. Ask after the user has completed a meaningful action: logged their tenth expense, finished a workout streak, exported their first file. The timing affects both the likelihood of a review and its sentiment.

The free tier as a marketing tool

This overlaps with revenue models, but the marketing angle is different. A generous free tier is not lost revenue. It's your advertising budget in a different form.

The calculation goes like this. If 100 people download your free app, maybe 3-5 will upgrade to paid. But those 100 free users also tell friends, leave reviews, show up in "apps I use" posts on Twitter, and generate word of mouth. If your free tier is crippled to the point of being unusable, none of that happens. Nobody recommends an app they stopped using after two minutes because they hit a paywall.

The sweet spot: the free version should be useful enough that someone would keep using it forever. The paid version should add enough that the people who use it a lot eventually want to upgrade. Limits on volume (number of entries, projects, exports) work better than limits on features for this reason. The user gets to experience everything, then hits a wall only when they're already invested.

Cross-promotion with other indie developers

This is underused. There are thousands of indie developers in adjacent categories who are not your competitors. If you built a workout tracker and someone else built a meal planner, your users are probably the same people. A mention in each other's apps (settings screen, onboarding, or a "recommended apps" section) costs nothing and sends qualified traffic.

Where to find partners: Indie Hackers, Twitter/X indie dev community, dev Discord servers, and niche subreddits. Cold outreach works if you're specific: "I built [app], it has [X] monthly active users, I think your app would be useful to my users because [reason], want to try a cross-promotion?" Most solo developers are happy to try because the cost is zero.

You can also cross-promote through content. Guest posts on each other's blogs, joint Twitter Spaces, or even a shared "indie app bundle" during Black Friday. The indie dev community is small enough that relationships compound. The developer you cross-promote with today might recommend you to a journalist or podcast next month.

Getting press without a PR firm

Tech press is harder to get than it used to be. Most publications have shrunk their editorial teams and the remaining writers cover fewer stories. But smaller outlets, newsletters, and podcasts have multiplied, and they're often more valuable because their audiences are more targeted.

The approach: make a list of 20-30 writers, newsletters, and podcasts that cover indie development or your app's category. Read their recent work. Send a short email that explains what your app does, why it's different, and why their audience would care. Attach 2-3 screenshots. Don't write a press release. Nobody reads press releases.

The angle matters more than the app itself. "I built a new todo app" is not a story. "I quit my job at Google to build a todo app that's been #1 in Productivity in Japan for three weeks" is a story. Find the angle. If you used an unusual approach (geo arbitrage, a data-driven MVP process, or building in a niche everyone ignores), lead with that.

Word of mouth and referral mechanics

Word of mouth sounds like something you can't control. You can't force it, but you can create the conditions for it. Two things drive organic sharing: the app does something the user wants to talk about, and there's a frictionless way to share it.

The first part is about building something with a "wow" moment. Fitness apps with shareable progress cards. Budget apps that generate a year-end spending report. Photo apps with a signature filter look. If your app produces output that looks good in a social media post or a message to a friend, sharing will happen on its own.

The mechanical side: add share buttons where they make sense. After completing an achievement. After generating a report. After creating something visual. Make the shared content look good (a designed image or card, not a URL with no preview). Include your app name but keep it subtle. People share things that make them look good, not things that make your app look good.

Referral programs (give a friend a free month, get a free month yourself) can work but they're hard to implement well as a solo developer. Start with simple share functionality and add structured referrals later if sharing is already happening organically.

Localization as a marketing strategy

Most indie developers build in English and stop there. That's leaving installs on the table. The App Store operates in 175 countries, and most categories have far less competition outside English-speaking markets.

You don't have to localize your entire app immediately. Start with just the App Store listing: title, subtitle, description, and screenshots. This can be done in a weekend and it immediately makes your app visible in searches in those languages. I wrote a detailed walkthrough for Asian markets specifically because that's where the gap between supply and demand is widest.

The numbers on this are hard to argue with. Some indie developers report 30-50% increases in total installs after localizing their listing into Japanese, Korean, and Traditional Chinese. The effort is a few hours. The return compounds forever. Check our geo-arbitrage scanner for apps that are already working in one market but missing from others.

The marketing stack that costs $0

Here's a concrete list of what I'd set up if I were launching an indie app today with no money:

Before launch: Optimize your App Store listing (title, subtitle, screenshots, keywords). Set up a simple landing page with an email capture. Write one blog post about the problem your app solves. Prepare your Reddit and Indie Hackers posts (write them in advance so they sound natural, not rushed).

Launch week: Post on Product Hunt (Tuesday- Thursday). Post on Show HN if there's a technical angle. Post on r/SideProject and one niche subreddit. Email your list of 20-30 writers. Reply to every comment and review that comes in during the first week.

After launch: Write one useful article per month about your app's domain. Respond to every App Store review within 24 hours. Update your ASO every quarter. Localize your listing for 2-3 non-English markets. Find 2-3 indie developers for cross-promotion. Share interesting data from your app on Twitter/X.

That's it. No ad budget. No PR firm. No growth hacker. Just consistent effort on channels that compound.

What to skip

Instagram and TikTok ads. The targeting is bad for niche apps and the cost per install makes the math impossible at indie price points.

Influencer marketing. You can't afford the influencers who move the needle, and the ones you can afford won't move it.

App review sites. Most charge $50-200 for a review that nobody reads. The SEO value of the backlink is the only argument for them, and there are better ways to get backlinks.

Hiring a marketer before you have product-market fit. If people don't retain after installing, marketing just accelerates the failure. Fix retention first. Read your reviews to understand why people leave.

Anything that feels like a shortcut. Buy installs, fake reviews, keyword stuffing. Apple is good at detecting these and the penalty is removal from the store. Not worth the risk when you can grow honestly for free.

The long game

Zero-budget marketing is slow. There's no getting around that. The developers who succeed with it are the ones who treat marketing as a daily habit rather than a launch-day event. Fifteen minutes a day on community engagement. One article per month. ASO updates every quarter. Review responses within 24 hours.

The advantage of slow growth is that it comes with understanding. When you talk to users on Reddit, you learn what they actually care about. When you read reviews, you see what's working and what isn't. When you write content about your domain, you sharpen your thinking about the problem you're solving. Paid growth gives you installs but not insight. Organic growth gives you both.

If you're still looking for what to build, our scanners can help you find opportunities where the marketing problem is already half-solved: apps with angry users looking for alternatives, abandoned apps with existing audiences, or rising categories with low competition. The best marketing advantage is building something people already want.

And if you're already making money and wondering whether to go full-time, remember that organic growth is also more predictable than paid growth. Paid channels can get expensive overnight when a competitor starts bidding on your keywords. Organic channels are yours.