By Felix — Growth Strategy & App Marketing, Heart Holdings

Most app developers spend three months building something, then three days marketing it. That's the entire story of why 90% of apps die in obscurity. I'm Felix. I run growth and app marketing at Heart Holdings, and I want to walk you through exactly how our AppWorkshop pipeline works — from raw idea to downloads hitting in week one.

This isn't theory. We ship apps. Let me show you how.

The AppWorkshop Pipeline: Idea to App Store in 3 Weeks

At AppWorkshop, we run a tight pipeline. Week one is scoping and design: we define the core use case, nail the UI, and lock in the store listing strategy before a single line of code gets written. That last part matters. Most teams build first and think about the store listing after. We flip it.

Week two is development. We're building for iOS and Android simultaneously from day one — no exceptions. Shipping to one platform first is a legacy mindset from when cross-platform tools were painful. That's not 2026.

Week three is QA, store submission, and launch prep. Screenshots go in. Keywords go in. Review request flows get tested. By the time the app goes live, we already have our launch playbook queued.

Twenty-one days. That's the window. Tight, but it forces discipline.

Why Indie Apps Fail at Marketing, Not Development

Here's the uncomfortable truth: most indie apps are technically fine. The code works. The UI is clean enough. They fail because the developer treated the App Store like a delivery truck — you upload the app, the store delivers the downloads.

That's not how it works.

The App Store is a search engine with a conversion funnel attached. If your listing isn't optimized for search, you don't get found. If your screenshots don't convert, you don't get installs. If you don't generate early velocity, the algorithm never gives you a shot at category charts.

Marketing isn't what happens after you build the app. It's baked into every decision from week one.

The ASO Basics 90% of Developers Skip

Apple gives you 30 characters in your app title. Most developers use all 30 on the app name. Wrong move. Your title is your most powerful keyword field — the algorithm weights it heavily. A title like "FieldQuote: Job Estimate Tool" outperforms "FieldQuote" every time, because you just told the store exactly what queries to surface you for.

Here's the short list of what most developers completely ignore:

Title keyword placement. Put your primary keyword in the title, not just the subtitle. The algorithm treats them differently.

Screenshot optimization. Your first two screenshots are the entire conversion argument for 80% of users. They see those in search results before they ever tap your listing. Most developers put a screenshot of the home screen. You should put your value proposition in large text over the screenshot, like an ad unit.

Description structure. The App Store truncates your description after the first three lines. Those three lines need to be your hook, your proof point, and your CTA. The rest of the description is for keyword density and long-tail discovery — not for selling the app. The screenshots do the selling.

Keyword field (iOS). You have 100 characters in the keyword field. Don't repeat words that are already in your title or subtitle. Use that space to capture adjacent searches.

None of this is secret. All of it gets skipped.

The Launch Week Playbook: 7 Days That Define the Trajectory

Launch week is the highest-leverage window you'll ever have for that app. The algorithm is watching for velocity signals: downloads, engagement time, review volume. Here's how we run it.

Day 1-2: Social proof seeding. Get the app into the hands of 20-30 real users before you push wide. Not for feedback — for reviews. A fresh app with zero reviews converts at a fraction of the rate of an app with even five honest reviews. Warm your email list, your social circle, anyone you can reach.

Day 3-4: Category targeting. Check your primary category's chart. Most developers pick massive categories and wonder why they can't crack the top 200. Find the subcategory where the #100 app has 50 reviews and modest download velocity. That's your entry point. You can move up from there.

Day 5-7: Review request timing. If your app has any engagement loop at all, trigger your in-app review request after the user has had a genuine win moment — not on first launch, not on a random timer. The conversion rate on review prompts is dramatically higher when the user just accomplished something.

Stack these three things and you have a real launch week, not a "I posted it on Reddit and nothing happened" launch week.

A Real Example: What the Numbers Looked Like

One of our recent launches — a utility app in the productivity space — hit the App Store with zero existing audience. Week one: 340 downloads, 11 reviews, 4.8 average rating. By day 10, it was ranking in the top 50 in its subcategory.

How? The title had the target keyword front-loaded. The first screenshot led with a bold value statement, not a UI tour. We seeded 15 installs from a small beta group before going public. The in-app review prompt fired after the user completed their first core action, not on open.

That's it. No paid ads, no PR push. Just clean execution on fundamentals that most developers skip because they're still thinking about the codebase.

The Point

Apps don't fail in Xcode. They fail in the App Store listing, in the launch week plan, in the keyword research that never happened. Development is a solved problem in 2026. Marketing execution is still where most teams drop the ball.

If you have an app idea and you want it built and launched the right way — development, ASO, and launch strategy baked in from day one — check out AppWorkshop.io. That's the pipeline we run.

Got a question about ASO, launch strategy, or app marketing? Reply to this email — I read them.