A few months ago, I wrote about building ten apps that nobody asked for.
On the surface, that article was about creating projects, experimenting with ideas, and learning through the process of building. But after publishing it, I found myself reflecting on a deeper question:
Who are these apps actually for?
The answer surprised me.
Many of the projects I have found most meaningful were never designed for large audiences. They were built for small communities with specific needs. Communities that larger companies often overlook.
Not because those communities are unimportant.
But because they are usually too small, too specialized, or simply not attractive enough from a commercial perspective.
That realization changed how I think about building software.
The Internet Serves the Largest Audiences First
Most technology companies operate under a simple reality: resources are limited, so products are often designed to reach as many users as possible.
From a business standpoint, that makes perfect sense.
If millions of people need a solution, companies can invest significant time, money, and talent into creating it. The potential return justifies the investment.
But what happens when the audience is smaller?
What happens when a group's needs don't neatly fit into a mass-market business model?
In many cases, those needs remain unaddressed.
Not because nobody cares.
Not because the problems are unimportant.
Often, it's simply because nobody has built the tool yet.
That creates an opportunity for independent developers.
Small Communities Have Real Problems Too
One lesson I have learned through building software is that a problem does not need to affect millions of people to be worth solving.
Sometimes helping a few hundred people is enough.
Sometimes helping a few dozen people is enough.
The number of users does not always reflect the value of the solution.
A tool that saves five minutes for a million people creates one kind of impact.
A tool that significantly improves the daily experience of a small community creates another kind of impact.
Both matter.
Throughout my work, I have repeatedly found myself drawn toward problems in areas that do not always receive much attention:
- Catholics looking for simple online prayer resources.
- People seeking faith-centered technology tools.
- Internet users trying to avoid scams and deceptive downloads.
- Individuals searching for educational resources outside mainstream platforms.
- Niche audiences with highly specific needs.
These communities may never attract large investments or venture capital funding.
That does not mean they deserve less support.
The Catholic Web Apps Directory Started With a Simple Observation
As I created more faith-based tools, I noticed something interesting.
Finding large Catholic websites was relatively easy.
Finding major Catholic mobile apps was also straightforward.
Finding smaller Catholic digital resources was much harder.
Many useful tools existed, but they were scattered across the internet. Unless someone happened to discover them through a search engine, they often remained hidden.
I started asking myself a simple question:
What if there were an easier way for people to discover these resources?
That observation eventually led to the creation of the Catholic Web Apps Directory.
The goal was not to compete with large app stores or technology platforms.
The goal was much simpler.
I wanted to make it easier for people to find useful tools that were already serving the Catholic community.
In the process, I learned something unexpected:
Sometimes the directory is just as valuable as the tools themselves.
Helping people discover solutions can be just as important as building new ones.
Why Niche Problems Are Worth Solving
Many people assume that valuable technology must solve a massive problem.
I'm not convinced that's true.
Some of the most successful products in history started by serving a very specific audience exceptionally well before expanding further.
Niche communities offer advantages that are easy to overlook:
You Understand Users More Clearly
When you're building for a specific audience, their challenges are often easier to understand.
You spend less time guessing and more time solving real problems.
Feedback Is More Focused
Broad audiences bring broad expectations.
Smaller communities tend to provide feedback that is directly tied to their actual needs.
That makes it easier to improve the product.
Competition Is Often Lower
Large markets attract large competitors.
Smaller markets are often underserved, which creates opportunities to build something genuinely useful.
Purpose Becomes Clearer
When you know exactly who you're serving, many product decisions become simpler.
Instead of trying to please everyone, you're helping specific people accomplish specific goals.
Technology Can Be an Act of Service
Many conversations in technology focus on growth, funding, valuation, revenue, and scale.
Those conversations are important.
Sustainable projects need resources.
Builders need to support themselves.
But I have come to realize that not every project needs to be evaluated exclusively through a financial lens.
Sometimes technology is simply a form of service.
A prayer resource that helps someone maintain a spiritual habit.
A safety tool that helps a user avoid online scams.
An educational resource that makes information easier to understand.
A directory that connects people with tools they otherwise would never find.
These projects may never become billion-dollar companies.
That does not make them insignificant.
In some cases, their value is measured less by revenue and more by the people they help.
Independent Builders Have a Unique Advantage
One advantage independent developers often possess is speed.
Large organizations frequently have layers of approval, competing priorities, and lengthy development cycles.
Independent builders can often identify a problem and start working on a solution immediately.
We can experiment.
We can adjust quickly.
We can serve communities that larger companies may never notice.
That flexibility creates opportunities to solve problems that would otherwise remain ignored.
In many ways, the future of technology will not be shaped solely by major corporations.
It will also be shaped by thousands of independent creators building solutions for communities they understand firsthand.
Build for People, Not Markets
If there is one lesson this journey has taught me, it is this:
A community does not have to be large to deserve useful technology.
Some of the most rewarding projects I have worked on were aimed at audiences that traditional product planning might consider too small.
Yet those projects often generated the most meaningful feedback.
When someone tells you that a tool helped them pray more consistently, avoid a scam, find a valuable resource, or solve a problem that had frustrated them for years, user-count statistics suddenly seem less important.
Because behind every statistic is a real person.
And real people are the reason we build in the first place.
Final Thoughts
The internet often rewards scale.
But meaningful work is not always measured by scale.
Sometimes the best opportunities exist where few others are looking.
In small communities.
In overlooked problems.
In audiences that major platforms rarely prioritize.
Those spaces may never produce headline-grabbing numbers.
But they can produce something equally valuable: genuine impact.
That is why I will continue building tools for communities that larger platforms may never notice.
Because every community deserves useful technology.
And sometimes the people who are easiest to overlook are the ones who benefit most from someone taking the time to build.
If you'd like to explore faith-based digital resources, prayer tools, online safety initiatives, and other Catholic technology projects, visit CatholicDevotion.org and browse the Catholic Web Apps Directory.
You may discover a tool built specifically for a community that the rest of the internet overlooked.
Reflection: What is a problem you encounter regularly that seems too small for large companies to solve, but meaningful enough that someone should?