You've built an app with Rork. It's published on the App Store. Downloads: zero. This is where most indie developers give up. But here's the truth—if you can get those first 100 users, you've built the foundation for organic growth. The challenge isn't getting people to notice your app exists; it's knowing where to look and how to ask.
As an indie developer, you don't have a marketing budget. What you have is time and conviction in the product you've built. To reach 100 active users in this position requires a deliberate three-phase approach: preparation, execution, and iteration. This article maps that journey, grounded in real examples of successful indie developers and the playbooks that worked for them.
Pre-Launch Preparation (Two Weeks Before)
Most indie developers start marketing after the app is finished. This is the first mistake.
Think of launch not as "publishing the app" but as "beginning contact with users." The first task isn't App Store optimization—it's creating a destination that tells people why they should care.
Build a landing page. A single-page site works fine. The App Store product page is good for conversion, but it doesn't tell your story. A simple landing page is where you control the narrative: what the app does, why you built it, and why someone should try it today.
The landing page needs three elements:
- A clear explanation of what your app does (aim for 30 seconds to understand the core idea)
- Real screenshots (they can be the same ones from the App Store)
- A call-to-action: "Join the beta testing group"
Beta testing is the underrated lever. If you can gather 30–50 beta testers before launch, they'll become your first wave of organic reviews and recommendations on launch day. Post "beta testing recruiting" in app developer communities on Twitter/X, Reddit's /r/iOSDeveloping, and /r/swift. You'll find willing testers quickly.
App Store Optimization (ASO)
Indie developers often overlook ASO, but the App Store is a search engine with its own algorithm. Optimization during the early stage shapes your trajectory far more than you realize.
Keyword Strategy:
- Choose your primary category based on how users actually search
- Include your strongest keyword in the app title (1–2 max; don't cram)
- Populate the keyword metadata field with 10–15 related terms users might search
For example, a budgeting app could use:
- Title: "Budget Pro - Expense Tracking"
- Keywords: "budget, budgeting, expense, money, tracking, finance, savings, app, simple, easy"
There's an advantage specific to you here. Your app was built with Rork. That's a differentiator and a story. The no-code and low-code communities actively look for apps built with these tools. Lead with it—not as a gimmick, but as transparency.
Screenshots matter too. Users spend 1–3 seconds on the first image. Use that first screenshot to visually show the problem your app solves, not just its beauty. This single change can lift your click-through rate by 20–30%.
Launch Week: Community Submission Strategy
The most effective launch strategy for indie developers is community submission. Product Hunt, Reddit, and Hacker News aggregate users actively looking for new apps. This is where you go.
Product Hunt:
- Post at midnight Pacific time
- Lead with the problem and your unique angle
- Title example: "Budget Pro—A Rork-Built Expense Tracker for Indie Developers"
- For 24 hours after posting, answer every comment and question immediately. This responsiveness influences ranking.
A strong Product Hunt launch brings 100–500 downloads. The community there has consistently supported indie projects, especially those with clear maker stories.
Reddit:
/r/iOSDeveloping: Use the "Show & Tell Wednesday" flair. Frame it as a learning journey, not a pitch./r/IAmA: "Ask Me Anything" format. Position yourself as an indie developer sharing your process, tool experience, and decisions.- Example post: "I'm an indie developer. I just launched a budgeting app built with Rork on the App Store. Happy to answer questions about the process."
Reddit users tend to be higher quality than quantity—they try the app, use it more, and provide thoughtful feedback. For your first 100, quality matters.
Hacker News:
- Avoid pure promotion. This community has strict norms.
- If you post, frame it around what you learned (e.g., "Building an app with no-code tools in 2026: here's what actually worked").
- Hacker News users are incredibly discerning and critical. Their feedback, if you get it, is gold.
Twitter/X: The Ongoing Narrative
Community launches are one-time spikes. Sustained growth comes from ongoing visibility. Twitter/X is where you build that.
Share your process in real time. Every decision, every feature launch, every bug fix you're proud of—it all becomes content that keeps your app in people's minds.
Post Template 1: Development Journey
"Just shipped the budget app I've been building with Rork.
Launch day was nerve-wracking—would anyone actually care?
But 47 people tried it on day one. Here's what I learned
about distributing as an indie developer.
[link]
Feedback welcome."
This type of post taps into the shared experience of indie makers. It doesn't bring huge engagement, but it brings real downloads—people who care about the maker story.
Post Template 2: Use Case Discovery
"Spent all morning watching how beta testers use the app.
Observation: people immediately create a 'impulse purchases'
category just to see it. That category alone makes their
spending patterns visible. Never planned that. Users told me
what mattered. Now we're building from that insight."
This signals that your app improves based on real user behavior. Post this type of discovery regularly—after each meaningful release.
Post Template 3: Transparent Challenge
"Real talk: first week post-launch was discouraging.
15 total downloads. But I started sharing on Twitter and
in developer communities. Now 10-15 new downloads daily.
If you're launching an indie app, share your process.
Show your work. That vulnerability is actually what
draws people in."
This resonates deeply with the indie developer audience. It's honest, and honesty builds community.
Turning Users Into Partners: The Feedback Loop
Your first 100 users aren't just a metric—they're your design team. Treat them as collaborators.
Create multiple feedback channels:
- In-app feedback button: A single tap that sends thoughts directly to you
- Twitter DM open door: "Found something? DM me @yourhandle"
- Monthly survey: A quick Google Form asking "What's working?" and "What's missing?"
The key: respond to every piece of feedback, and report back when you've acted on it. A user who sees their suggestion become a feature becomes a vocal advocate.
Pre-Launch Checklist
Get these done before you hit publish:
- [ ] Landing page complete (with screenshots and copy)
- [ ] App Store metadata optimized (title, keywords, description, screenshots)
- [ ] Beta tester recruitment plan ready
- [ ] Product Hunt post scheduled for launch day
- [ ] Reddit communities identified (minimum three)
- [ ] Three Twitter post templates written and scheduled
- [ ] Feedback collection system set up (form + DM monitoring)
- [ ] Week 1 posting calendar created
Beyond Week One
Launch momentum peaks in week one and plateaus by week two. That's when most people stop. Don't.
The second phase is sustaining attention through consistent, value-driven content. New feature? Share what problem it solves. Milestone reached (50 users, 100 reviews)? Celebrate publicly. These small moments add up.
By month three, if you've executed this playbook, you'll have passed 100 active users. Some will have become regular users. A few might become true fans who talk about your app unprompted. That's not just 100 downloads—that's the beginning of a real product.
The first 100 users matter because they're the foundation. Build with care.