Describe the internal tool you need in a conversation and an agent builds it over your own bases, then publishes it privately to the workspace. No repository, no deploy, no ticket.
The brief is a sentence in a stream. The agent reads your bases, picks the fields it needs, builds the views and shows you the result — then changes it when you reply.
Mini apps sit in folders with an owner, a modified date and a history. They are not shadow IT — they live inside the same permissions as everything else, and an app cannot reach past what its user already can.
No repository, no build step, no ticket in someone else's backlog.
The app reads and writes the same rows your team works in.
Organised like files, with a history and someone responsible.
Install what has already been built instead of describing it again.
A mini app cannot see past what its user and its agent already can.
Shared inside the workspace, not on the internet.
A mini app is never finished in one message. Ask for a change and the agent reads the app, the base behind it and what people actually use, then rebuilds and shows you the difference.
No. The brief is a sentence. A developer can extend it later through the API, but nothing about building one requires code.
Yes, within its authority, and the result arrives as a draft for a person to publish.
The app follows it — it reads the base rather than a copy, so a new column is available immediately and a removed one is flagged.
One sentence in a stream, one agent, and the thing exists before the afternoon is over.