Here is a sentence no software engineer wants to hear: people do not care about your app.
They do not care how quickly you built it, how clean the interface is, or how many AI features you managed to fit into it. People are becoming less inclined to even download a new app.
For a long time, building an app was the obvious way to deliver a solution to a problem. The formula felt simple: have an idea, give it a fancy-looking interface, put it on the App Store, and wait for people to find it.
But in reality, we already have enough apps. AI has made it possible to ship things faster, so turning a product into an app is no longer the hardest part. At the same time, the audience has changed. People are less willing to download another app when they already have so many.
Are You Worth Someone’s Home Screen Space?
Every new app asks something from its users. It asks them to create an account, learn a new interface, move their data, change their habits, and remember that the app exists.
Most of the time, they just want the tools they already use to work better. If using your app creates more friction than the problem it solves, they may be better off without it.
The next great solution may not be another app trying to take over. It might be the infrastructure people cannot see, quietly improving their experience without taking up space on their home screen.
Building an App Has Never Been Easier
AI has made it possible to move from an idea to a working interface faster than ever. You can generate components, connect a database, and deploy something before you have fully decided who needs it.
That speed is useful, but it also means more software is competing for the same limited amount of attention. The app itself is becoming the easy part. The harder and potentially more valuable work may be happening underneath it.
The Solution Is Something You Don’t Even See
Infrastructure is not always easy to show in a product demo. I would know; I have to be the face explaining it in videos. It lives underneath the visible experience: APIs, SDKs, data pipelines, integrations, automation, authentication, and observability. Did you really read all those terms? Have I lost you yet?
There is a strange tension in building infrastructure: when it works well, people barely notice it. Nobody celebrates an API for working as expected, and nobody stops to admire a data pipeline. In fact, these systems are often more noticeable when they fail.
That invisibility can make infrastructure feel less exciting than an app with a polished launch video. But reliability, compatibility, and trust are features too. In many cases, they are the features that determine whether the visible product works at all.
That is a different kind of value. Instead of asking, “How do I get people into my app?” I think the question becomes, “How can what I build make everything around it work better?”
This Is Not the End of Interfaces
None of this means the visible layer no longer matters. I am not saying that every interface is useless or that nobody should build apps again. People still need thoughtful and beautiful ways to interact with technology. The problem is starting with the assumption that every idea needs to become an app.
I see it more and more online: “I built this website…” or “I built an app…” I think those projects are fun to show, but I do not think that alone sells people anymore. It is app fatigue, really. Everyone already has the same rotation of apps they use, so what would make them choose yours?
So, to finish this final yap: yes, stop building apps.
At least, stop treating the app as the goal. Build the connection between tools. Build the layer that removes repetitive work. Build the system that lets the next person move faster. Build something people can rely on, even if they never think about the infrastructure making it possible.