How Kyle Fowler Built Two Apps Generating More Than $120,000 a Month.
There is a common trap in the startup world: people spend weeks hunting for the “perfect” idea, only to end up with a long list of bookmarks and nothing shipped. Kyle Fowler took a different route. Instead of chasing trends, he built around a problem from his own hobby, and that decision led to two apps that together generate over $120,000 in monthly revenue.
That story matters because it strips away a lot of the mythology around entrepreneurship. No dramatic origin story. No giant venture round. No complicated market thesis. Just a developer who noticed a real problem in his own life, built a solution, and then repeated the process when he saw another opportunity.
The idea was already there
Kyle had been collecting cards since childhood, and like many collectors, he wanted a simple way to organize what he owned and understand what each card was worth. When he looked for an app that could digitize his collection and help identify cards from his phone, he found that the product he wanted did not really exist in the form he needed.
That gap became Cardstock, a sports card value scanner that lets users identify cards, check market value, add them to a digital collection, and monitor value over time. According to the interview, Cardstock now has around 15,000 active subscriptions, roughly $75,000 in monthly recurring revenue, and about 13,000 downloads each month.
The second app, Scanémon, applied a similar model to Pokémon cards. Although it launched only about a year before the interview, Kyle said it had already reached roughly 3,400 active subscriptions and around $17,000 in monthly recurring revenue, with approximately 16,000 new customers per month.
Why this approach works
The strength of Kyle’s method is that it starts with lived experience rather than abstract brainstorming. He did not begin by asking what market was hot. He began by asking what was annoying, repetitive, or missing in a hobby he genuinely cared about.
That matters because real users often behave the way founders behave. If a problem is persistent enough to irritate one engaged person, there is a reasonable chance it affects a wider group as well. Kyle framed it simply: if a founder can solve a problem for themselves, there is a decent chance other people have it too, even if monetization still has to be tested in the market.
This is a more practical validation model than waiting for certainty. Instead of trying to eliminate risk before building, the founder reduces uncertainty by shipping a minimal solution and watching how the market responds.
From idea to launch
Kyle said he started building Cardstock in winter 2019 and reached a working version in roughly six months, including a three-month gap in the middle. He got his first downloads quickly after posting an update on Reddit, which shows how even lightweight distribution can matter if the product solves a clear problem for a specific niche.
What is more striking is how different the second launch looked. For Scanémon, built in 2025, Kyle said he relied heavily on AI-assisted development and produced the MVP in a single day using Cursor’s agent capabilities.
That contrast captures a bigger shift in software creation. The first app required a more traditional grind, while the second benefited from a new generation of AI tools that compress development time dramatically. The important insight is not that building is effortless now, but that the distance between idea and testable product is much shorter than it used to be.
The stack behind the business
In the interview, Kyle explained that Cardstock was built with Swift and SwiftUI, using Core Data for storage. He also mentioned third-party tools and services such as RevenueCat for subscriptions and AWS EC2 for backend infrastructure tied to the card database.
He also listed a broader modern tool stack that includes ChatGPT subscriptions, Notion, Cursor, Slack, Framer, Claude, Supabase, Railway, Code Rabbit, WhisperFlow, and Granola. The exact tools are less important than the pattern: modern app businesses increasingly combine native app frameworks, lean backend services, and AI-assisted workflows to move faster with small teams.
That pattern is especially relevant for indie developers. A solo founder or small team no longer needs a massive operation to get a product live, maintain it, and build supporting systems around monetization and content.
His framework for finding app ideas
One of the most useful parts of the conversation was Kyle’s step-by-step thinking for discovering potential app ideas. His first step was simple: pay closer attention. He suggested keeping a notes document for repetitive, frustrating, or slow tasks that show up in daily life, because those are often overlooked opportunities.
Get Founder Stories Lab’s stories in your inbox
Join Medium for free to get updates from this writer.
The second step is to design the most minimal solution that actually removes the pain. Not the dream version, not the fully loaded roadmap, just the fastest product that solves the problem clearly enough to test.
The third step is to build and monetize quickly. In his view, many people still overestimate how difficult app development is, especially now that AI tools can help implement large parts of the product and services like RevenueCat or Superwall make monetization easier to add.
This framework is powerful because it lowers the emotional cost of starting. Instead of asking, “Is this a billion-dollar idea?” the better question becomes, “Does this solve a real annoyance in a way that someone would immediately understand?”
Marketing in 2026
Kyle’s view on marketing was refreshingly direct. He said the team has seen significant success with TikTok slideshows because they are simple to produce, easy to repeat, and testable at scale. The goal is to find the balance between content that gets views and content that converts those views into downloads.
He also mentioned a platform called Noise for distributing slideshow templates to creators, paying based on views. He added that founders can start even more simply by posting from their own account, or from a small group of accounts, to see whether a format gains traction before investing further.
That advice reflects a broader truth about modern software businesses: distribution is no longer a separate phase after product development. It is part of product development. A founder is not just testing what to build; they are also testing how attention turns into installs, subscriptions, and retained users.
What makes the story useful
The most compelling part of Kyle Fowler’s story is not the revenue figure, even though the revenue is impressive. It is the accessibility of the method. He did not present startup building as a mysterious craft reserved for elite founders. He presented it as a habit of noticing, building, testing, and iterating without overcomplicating the process.
That mindset is especially important in a market where many aspiring founders consume more advice than they execute. The interview suggests that progress comes less from perfect planning and more from repeated contact with real problems and fast feedback loops.
There is also a useful emotional lesson in the way he talks about the work. His approach feels grounded, calm, and almost obvious in hindsight: build around what you already understand, solve what bothers you, and let the market tell you what deserves more effort.
Lessons for founders and indie hackers
Several practical takeaways stand out from this case:
- Start with a hobby, niche, or workflow you already understand deeply.
- Keep a running list of repetitive frustrations and missing tools in your daily life.
- Build the smallest version that proves the core utility of the idea.
- Add monetization early so the market can reveal whether the product has commercial value.
- Treat marketing as an ongoing experiment, not a final-stage task.
- Use AI to accelerate development, but not as a substitute for judgment about what is worth building.
These are not glamorous lessons, which is exactly why they are useful. They translate well beyond card apps and apply to almost any niche software product where the founder has domain familiarity and enough discipline to ship.
The clearest takeaway from Kyle Fowler’s journey is that strong app ideas do not always arrive as breakthrough insights. Often, they begin as everyday friction inside a hobby, a routine, or a niche community that most people ignore.
For founders, the real opportunity is not just to brainstorm harder. It is to observe more carefully, build more quickly, and test more honestly. That is how a personal annoyance becomes a useful product, and sometimes, a business doing more than a million dollars a year.
