What's up, nerds 👋

In January 2025, Lukas and I set an ambitious goal...

Launch 10 apps this year.

A very optimistic goal, considering everything else we are doing at notJustDev.

But guess what?

We've already launched 6 out of 10 apps. And it's only September.

How? Because we cracked the code and created something we call THE PLAYBOOK.

A battle-tested system that turns app ideas into real, revenue-generating products faster than we ever thought possible.

Last week I used this exact system to go from idea to App Store in just three days.

And today, I'm sharing my learnings with you!

Every idea goes through five phases:

Research → Planning → Building → Pre-Launch → Launch.

📌 Read till the end... I've got something EXCITING to share.

Phase 1: Research 🕵️‍♂️

Here's the brutal truth: Your idea sucks.

Not because you're not smart. Not because you lack creativity.

But because you're trying to solve a problem that doesn't exist by thinking you are smarter than everyone else.

Don't try to reinvent the wheel. Find something that already works, and build a better version.

I learned this the hard way after spending years building a "revolutionary" app that I thought was completely unique. Turns out, there was a reason no one had built it before: zero demand.

Now I follow a different strategy: Instead of creating markets, I grab a piece of existing markets.

Markets that are already proven. Markets where people are already spending money.

Here's my process:

I use getastro.app to hunt for keywords like an addict. The sweet spot is keywords with at least 20 popularity but under 60 difficulty.

But here's the secret sauce: I don't start with app ideas anymore. I start with competitor analysis.

I stalk successful apps in different categories. I study their keywords, dive into their reviews, and analyze what they rank for. When I see apps with thousands of downloads and decent ratings, I know there's a proven market.

The reviews are pure gold – they tell you exactly what people love and what they're frustrated with. That frustration? That's your opportunity to build something better.

By the time I'm done researching, I don't just have a keyword. I have proof that people want this solution AND a clear understanding of how to improve on what already exists.

Once I find that golden keyword backed by competitor validation, everything else falls into place: app title, subtitle, brand name. I just note everything down straight into Notion.

Simple. Systematic. Effective.

Phase 2: Planning

Keywords guide the app’s purpose. If the keyword is “PDF generator,” then the app should…

Generate PDFs (crazy! I know! 😄)

In this phase, I:

• Define Must-have vs. Nice-to-have features. I used to be the guy who built 10 okay-ish features, and now I build apps with 1-2 features that work incredibly well.
• Sketch basic mockups. Nothing fancy. Just sketches that prevent me from coding myself into a corner later.
• Decide on monetization. For us, that usually means in-app subscriptions, with:
  • Weekly plans ($5–$8) with a 3-day free trial
  • Annual plans ($25–$35)

Just as important: define which features are free vs. behind a paywall. This directly affects conversion.

Don’t overthink this phase. You don't need business plans of thousands of pages. A simple 1-2 page plan is enough.

That app I built in three days? The entire research and planning phase took me 3 hours.

Not three weeks. Not three days. Three hours.

I stopped trying to create the "perfect" business plan and started focusing on speed and iteration.

Phase 3: Building 🛠️

Time for the fun part... and the part where most developers get stuck forever.

Build the MVP: one or two core features, done really well. Everything else? Cut it.

Your focus is validation, not perfection. You can always come back and improve the application.

But here's where it gets interesting...

Lukas and I noticed we were writing the same boring code over and over: onboarding flows, settings screens, user profiles, in-app ratings.

So we created a starter template.

That three-day app I mentioned? It was our first test of this template. And to be honest, it saved me so much time because I managed to build the whole application in just one day.

This template lets us focus on what matters most: the unique core features.

Phase 4: Pre-Launch 📖

This is the boring phase. But also the most important one.

Most developers skip this stuff or rush through it. Then they wonder why their app crashes on launch day or why nobody leaves reviews.

Here's what actually happens in pre-launch:

Visual Polish: App icon, splash screen, and all the visual elements that make your app look professional instead of like a college project.

Third-Party Integrations: Setting up crash reporting (Sentry), analytics (Amplitude), and all the tools that tell you what's actually happening when users touch your app. The good news? Our starter template already has all the integrations built-in. The tedious part? You still have to create accounts on each platform and grab API keys. It's like digital paperwork, but necessary.

First Builds: Time to create your first real builds for testing. Here's where our CI/CD pipeline saves you hours (maybe days) of setup headaches. What used to take a full day of configuration now happens with a few commands.

In-App Subscriptions: Setting up RevenueCat. This isn't optional if you want to make money. Configure your pricing tiers, trial periods, and make sure everything talks to the App Store properly.

Onboarding Screens: This is where you either hook users or lose them forever. Our starter has the templates, but a good onboarding experience requires actual thought and design time. Don't phone this in – first impressions matter.

Review Prompts: Configure those in-app review requests that appear after users complete successful actions. This is crucial for building your app ratings, which directly impact App Store rankings.

This phase isn't glamorous. It's digital plumbing.

But it's the difference between an app that crashes on launch day and one that actually works when real people start using it.

Phase 5: Launch 🚀

Launch day. The moment of truth.

Before submitting the app for review, make sure you test it on a physical device really well. Especially the main feature and the payment flows.

Then, it’s time to create the App Store Screenshots.

Apple now indexes text in screenshots, so your keyword strategy applies here, too. Good screenshots can double your conversion rate, bad ones - kill your app before anyone downloads it.

Finish with the rest of the App store configuration: metadata, privacy policy, etc.

Once ready, it’s time to press that “Submit for review” button.

We usually start with App Store first because App Store users are more willing to pay.

Reality check: prepare for 2-5 rounds of rejections 😅

Once approved, Apple gives you a visibility boost for the first week. After that the downloads might slow down, but don't panic. Apps often get a second wind after several months.

Monitor everything. Learn from the data. Then decide: improve this app or ship the next one?

Wrapping Up 👨‍💻

This is the process we’re following at notJustDev. With every iteration, Lukas and I refine our starter template, improve our practices, update our playbook, and share our learnings across our portfolio.

Everything I just shared with you, this 5-step process, is how we’re going to help you launch your own app inside the notJust.Incubator.

Yes, that’s right. We are bringing back the Incubator and we are looking for 10 exceptional developers to join the next cohort 🚀

Here’s the thing:

👨‍💻 You don’t need to know how to code - AI can do that

💡 You don’t even need to have an idea yet - we’ll help you find one

🕺 All you need is the drive and motivation to finally launch something real.

Inside the Incubator, you will:

• Launch and validate your app in 10 weeks instead of working on it for 2 years.
• Use AI tools as your coding superpower instead of fearing robot overlords
• Get access to our internal project templates, saving you weeks of setup.
• No bullsh!t, just pure grind, together with me and my team, helping you 1-on-1

The best part - you keep 100% of your project. We don’t take any equity.

Only 10 spots available.

Why so few? Because there is a ton of personal attention and hand-holding to make sure you never get stuck until you get your app on the store.

​Join the waitlist and receive detailed information on Incubator submissions, deadlines, and everything you need to know. We’ll also share industry insights on why you should consider these changes if you want to be successful.

Not so secret surprise: we’ll even share the first chapter of the Playbook with the waitlist only.

Let’s build profitable apps together!

P.S. That app that I built in three days is already generating revenue. Sometimes the best apps are the ones you actually finish, not the ones you perfect forever.

P.S.S. Check out our documentary about the Incubator and see how ordinary people with the right guidance became successful app founders.

🔴 Join me live

This Friday we will build Mobile App with AI (from 0 to market). From brainstorming and design, to code generation, testing, and shipping, this is how you build fast in 2025, so set a reminder and don't miss it out 👇

​

​

​

🔁 In case you missed it

A Journey of Transformation: Inside the notJust Accelerator (Incubator) From no coding experience to launching professional apps, our participants prove that with the right guidance and determination, anything is possible. It's not just about building an app; it's about creating a viable product that addresses that brings real revenue. Watch now

Tools I use to build mobile apps FAST with React Native ​ In this video, I’ll walk you through my complete tech stack for building modern, production-ready mobile apps - fast. From the frameworks and libraries I use daily, to the AI tools and IDEs that supercharge my workflow, you’ll get an inside look at how I ship scalable apps using React Native, Expo, Supabase, and more. Watch now

Did you learn something new today?

If you found this email valuable, forward it to one friend or coworker who can also benefit from it. That would be much appreciated 🙏

Vadim Savin Helping you become a better developer together with the notJust.dev team