Claude can build the app. Then what?
What happens to developers when Claude can build a working app in a morning?
An agency owner on r/ClaudeAI said he can give Claude a prompt, go to the gym, and come back to a working app. I believe him. Imagine a warehouse app that looks simple in a demo: staff scan a document, and the app posts a delivery record to an inventory system.
In use, a phone can lose its connection. A request can reach the inventory system and time out before the app gets a reply. Retry carelessly, and the same transaction might land twice. The demo works. Someone still has to solve what happens after it.
Some apps really can end at version one
One reply in that thread came from a teacher who used Claude to make a classroom name picker. They wanted a particular way to choose students without hunting for a website, creating an account, or putting up with ads. They got a tool that worked for their lesson.
Good. I want more people to be able to do that. I have no interest in arguing that a teacher needs to hire a software team for a name picker.
I also think anyone selling a basic dashboard as though it takes months of special magic is in trouble. I can now get a rough interface and working flows on the screen much faster than I could a few years ago. Clients can see that too. They will ask why the price has not changed.
But I would ask them what happens after the demo. Who will use the app? What data does it touch? What happens when the internet drops or a record is wrong? For a classroom tool, the answers may be simple. For a warehouse or payments system, they usually aren't.
Where the work goes
In that hypothetical warehouse, scans might need to wait until a connection returns. Each attempted write needs a stable identifier so a retry does not create a duplicate. Someone also has to decide which errors can be retried and which ones need a person to review them.
None of that makes a great five-minute app demo. It matters when staff are using the system every day.
An assistant for a company raises a different set of questions. Which company is this user asking about? Which records are they allowed to see? If the assistant gives a number, did it actually look that number up? If it proposes a change, can the user inspect it before anything is written? The model can help people work with data; permissions and an approval flow decide what it is allowed to do.
AI can help write and check code for both systems. But it cannot decide, on its own, what a warehouse team has agreed should happen after a failed scan or who should approve a change. A developer has to learn those rules from the people doing the work, build them into the software, and check that it behaves as agreed.
I don't think anyone knows the job numbers yet
There is a lot of confidence in the thread about which jobs will disappear and which ones are safe. I'm less sure.
Even the productivity evidence depends on the task. In a 2025 study, experienced developers working on mature projects took longer with the AI tools available at the time. The researchers' 2026 update found signs that newer tools were helping, but they could not reliably measure how much. Meanwhile, Anthropic's study of Claude Code use shows people doing more substantial work with agents, with the user's knowledge still affecting the result.
Those findings fit what I see: a prototype, a small personal tool, and a change to a business system can all be called "building an app," even though they ask very different things of the person doing the work.
I expect some work to get cheaper. I expect people who could never afford custom software to start making it. I would be careful with anyone who claims to know the exact balance between those two changes, or the number of developers they will leave employed.
What I would offer a client now
If I ran an agency that sold only the first build, I would be worried. I would want to know an industry well enough to spot the problems a prompt misses. I would want to stay involved when a new app has to meet an old database, a payment provider, a warehouse floor, or a support team.
And I would be clear about who answers the phone when something breaks.
That is where I want my own work to go. Give me the fast prototype. I'll use AI to help improve it. Then I'll sit with the people who actually have to use it and ask where it could fail them. I'll make sure the data goes to the right place, a retry doesn't quietly duplicate a transaction, and the next engineer can understand what I built.
Claude has made the first version easier for more people. I think that's worth celebrating. It also means I need to be able to say, plainly, what my work adds after that first version. For me, the answer is in the transaction that survives a bad connection, the action that waits for approval, and the person willing to own the system once it is running.