Indie App Marketing: A No-Budget Plan for Your First 1,000 Users

Most indie app marketing advice is written for teams with a budget. This guide is for the other case: you built the app yourself, you have no money for ads, and you have maybe an hour a day left over after the job that pays rent. The plan below gets a solo developer to the first 1,000 users with a landing page, a handful of launch posts, and one repeatable daily habit. Nothing in it costs more than your time, and most of it costs less than an hour a day.

The indie trap: 95% building, 5% marketing

Here is the pattern. You spend six months on the app. You polish the onboarding, fix the dark-mode bug nobody reported, and ship. Launch day is a tweet, a Reddit post that gets removed, and 40 downloads from friends. Week two is silence. So you go back to building, because building is the part you are good at, and you tell yourself the next feature is the one that makes it click.

It does not click, because the problem was never the feature. The problem is that nobody who would pay for the app knows it exists. Every successful indie app you can name solved distribution before it solved its roadmap. Apps like Cal AI (15M+ downloads) and Umax (10M+) grew on a flood of TikTok content, not on a better settings screen. You do not need their scale. You need the same ratio flipped: once the app works, most of your spare hour goes to getting it in front of people.

The one-hour-a-day budget

Treat marketing like a fixed-cost line item. One hour a day, every day, booked in the calendar before you open Xcode or Android Studio. Split it roughly like this once you are past launch week:

• 30 minutes: make and publish one piece of content (more on which kind below).
• 15 minutes: answer one real question somewhere your users hang out.
• 15 minutes: reply to comments, DMs, reviews and support email.

That is it. No funnel diagrams, no marketing stack. If you keep this up for 90 days you will have published roughly 90 posts and had roughly 90 conversations with potential users, which is more than most indie apps get in their first year.

Positioning in one sentence

Before you post anything, you need one sentence you can repeat in every bio, landing page, and first slide without rewriting it. The format is boring on purpose: who it is for, the pain they have, and the promise you make.

For [who] who [pain], [app] [promise].

Three hypothetical examples, so you can see how specific this has to be:

• Habit tracker. "For people who have quit five habit apps, Streakly only asks one question a day and never shows a red zero." Not "a beautiful habit tracker", which is what every competitor says.
• Budgeting app. "For freelancers with irregular income, Tally tells you how much you can safely spend this week, not this month." The pain (irregular income) is the hook; the promise (weekly, not monthly) is the differentiator.
• Language app. "For adults who learned Spanish in school and forgot it, Recall rebuilds what you already knew in ten minutes a day." It excludes beginners deliberately. Excluding people is what makes the right people stop scrolling.

Write yours, then test it on three strangers who match the "who". If they cannot explain back what the app does, rewrite it. This sentence is the single most reused asset in everything that follows, so spend a day on it, not an hour.

Pre-launch week: four things, in order

You do not need a six-week pre-launch campaign. You need four things done the week before the app goes live.

1. A one-page landing page

Positioning sentence as the headline, three screenshots, one paragraph about the pain, an email field, and the App Store or Google Play badge once you have it. Use whatever you already know (Next.js, Carrd, a static HTML file on Cloudflare Pages). Spending more than a day here is procrastination dressed as marketing.

2. A waitlist

The email field goes to a Google Sheet, Buttondown, or anything free. The point is not a huge list; even 50 addresses means 50 people you can email on launch day and ask for a review. Put the waitlist link in your social bios now.

3. Ten real conversations

Find ten people who match your "who" and talk to them for 15 minutes each. Reddit DMs, a Discord server, friends of friends, the comments of a competitor's post. Ask what they use today, what annoys them about it, and what they would search for if they were looking for a fix. You will get three things: the words your audience actually uses (which become your hooks), a list of objections (which become your FAQ), and ten people who feel invested enough to leave a first review.

4. A TestFlight or closed-testing group

Put those ten people, plus the waitlist, into TestFlight or Play Console closed testing. Beta testers find the crash you missed, and on launch day they are the ones who download in the first hour and leave the first ratings. Ask them directly: "When it goes live Tuesday, would you rate it?" Most will say yes if you ask one at a time.

Launch week checklist

Launch week is the one time a year you get to be loud on every channel at once. After this week, you will narrow down hard. The table below is the full menu; effort is in hours of your time, and the outcome ranges are rough, based on what solo developers commonly report on Indie Hackers and Reddit, not a promise. A launch that lands 100 to 500 downloads in week one is a normal, healthy indie launch.

One more thing about launch week: write the App Store or Play Store listing before any of this. Your positioning sentence is the subtitle. The first screenshot shows the promise, not the login screen. People who click through from Reddit will decide in three seconds on that page, and nothing above matters if the listing loses them.

The daily habit after launch

Here is where most solo developers stall. Launch week ends, the spike fades, and there is no obvious next thing. Every channel in the table above is a one-off or a slow burn. None of them can be done every day without burning out or annoying people. You need a channel where posting daily is normal, expected, and rewarded by the algorithm rather than punished by a community. For a solo developer in 2026, that channel is short-form social, and the specific format is the photo slideshow.

Why one slideshow a day is the only sustainable daily channel

A TikTok or Instagram slideshow is six to eight still images that the viewer swipes through, with a hook on the first slide and the app on the last. Compared to everything else you could do daily, it has four properties that matter for a solo dev:

1. No camera, no face, no voice. You do not have to be on screen, record audio, or learn an editor. That removes the biggest reason developers never start. The faceless app marketing page goes deeper on why that works.
2. It takes minutes, not hours. A slideshow is text on images. Once you have a hook and six lines of copy, it is laid out in minutes, which fits inside the 30-minute content slot.
3. Daily posting is the norm, not spam. On TikTok and Instagram, a new post every day is what the format expects. On Reddit, Hacker News or a newsletter, a post a day gets you banned or unsubscribed.
4. Each post is a fresh lottery ticket. TikTok distributes photo posts in the same For You feed as videos, and reach is decided per post, not per account. One flat post costs you nothing; one post that lands brings installs for days. Apps like RIZZ (5M+) and Couple Joy (1M+) grew on exactly this kind of high-volume, low-production content.

The content itself comes straight from your ten conversations. Every pain point someone described is a first slide. "I have deleted five habit apps" is a hook. "Why monthly budgets fail freelancers" is a hook. The middle slides explain the pain, the second-to-last slide shows the app solving it with a real screenshot, and the last slide says the name. The TikTok slideshow strategy for apps article breaks down the slide-by-slide structure and what to do with the caption and hashtags, and if you run dry on angles, this list of content ideas for apps is built for exactly that.

Post the same slideshow to both TikTok and Instagram (Instagram needs a Business or Creator account for carousel scheduling, which is a two-minute switch in settings). Two platforms, one piece of work. Do not add YouTube, Pinterest, LinkedIn or anything else until you have 90 consecutive days on these two.

Plus one community reply a day

The second daily action is quieter. Find one question in your niche that your app genuinely answers (a Reddit thread, an App Store review of a competitor, a comment under someone else's post, a Discord question) and answer it properly, as a person. Mention your app only if it is the honest answer, and often it will not be. This is slow, but it compounds. After 90 days you are a known name in three or four places where your users gather, and that is worth more than any single launch post.

Monetisation sanity, briefly

Marketing an app with no budget only works if the app can eventually pay you back, so get three things roughly right before you scale the daily habit:

• Trial, not freemium, for most utilities. A free tier that does the whole job gives you users who never pay and a support load you cannot afford. A short trial (three to seven days) with the full app converts the people who felt the value and lets the rest leave.
• Paywall timing. Show the paywall after the first moment of value, not before onboarding. For a habit tracker that is after the first habit is logged; for a budgeting app it is after the first week's number appears. A paywall on the first screen is the number one reason indie apps show hundreds of installs and zero revenue.
• Pricing. Anchor on a yearly plan, show the monthly beside it, and price higher than feels comfortable. Indie developers systematically underprice. You can always run a discount later; raising prices on existing subscribers is painful.

You do not need these perfect at launch. You need them good enough that a thousand users produces a number you can see, so you know whether to keep going.

The 90-day plan

Put it together and it looks like this. Weeks are after launch; pre-launch week is the week before.

The number 1,000 is a milestone, not a finish line. What you actually have at day 90 is a repeatable system: a positioning sentence that works, a content habit that produces installs, and a feedback loop from users to roadmap. That system is what you scale, whether that eventually means paid ads, a second account, or more posts a day. The downloads-without-ads guide covers what the next layer looks like once this one is running.

What to stop doing

An hour a day only works if you protect it. These are the three ways solo developers spend it on things that feel like marketing and are not.

Chasing vanity metrics

Followers, likes, and Product Hunt upvotes do not pay you. Track three numbers: store page views, installs, and trial starts. If a post gets 50,000 views and no installs, the hook was good and the promise was wrong. If a post gets 800 views and 12 installs, make ten more like it.

Redesigning instead of distributing

When marketing feels uncomfortable, a redesign feels productive. It is not. Unless reviews specifically complain about the design, the current one is fine. Ship the redesign when you have 1,000 users telling you what to change.

Being on every platform

A YouTube channel, a Pinterest board, a LinkedIn presence, a Discord server and a newsletter, each updated twice and abandoned, is worse than nothing. It makes the app look dead. Two platforms, one format, every day. Add a third when the first two are automatic.

FAQ

How do I market an app for free?

With time instead of money: a one-page landing page, launch posts on Product Hunt, Reddit and Indie Hackers, a waitlist you email on launch day, and then one slideshow post a day on TikTok and Instagram plus one genuine community reply. None of those cost anything but your hour. The only optional spend is a tool that saves you part of that hour.

How long does it take an indie app to get 1,000 users?

There is no reliable number, and anyone giving you one is guessing. With the plan above, 90 days is a realistic target for a utility app with a clear audience, assuming you actually post every day. Some apps get there in a week on one post that lands; others take six months. The daily habit is what makes the timeline shorter rather than longer.

Should a solo developer use paid ads?

Not before you know what a user is worth. Ads amplify a funnel that already converts; they cannot fix one that does not. Get to the point where you know your trial-to-paid rate and roughly what one organic post brings in. Then a small ad test is an informed bet rather than a donation to Meta.

Do I need to show my face on TikTok to promote my app?

No. Photo slideshows are text and images, and plenty of apps have grown with accounts that never show a person. Hooks, screenshots and a clear promise do the work. See faceless app marketing for the full argument and examples of the format.

What if my app is on Google Play only?

Everything here applies. Replace TestFlight with Play Console closed testing, and use your Play listing as the source for your positioning and screenshots. Android audiences on TikTok are large and under-served by indie developers, which is an advantage, not a handicap.