Aller au contenu
Agentivity
Star on GitHub Commencer gratuitement

What a VibeApp is

Ce contenu n’est pas encore disponible dans votre langue.

A VibeApp is an application that adapts to the person who uses it. Behind it, a team of AI specialists does the work.

Set the goal. The VibeApp handles the rest.

A traveller wants a long weekend in Lisbon for two, with a budget.

In a classic application, the traveller adapts to the application. They open the flights screen and fill in the dates. They open the hotels screen and fill in the dates again. They add up the prices themselves to stay within the budget. They look for the page about travel documents. If their case is unusual, there is no screen for it.

In a VibeApp, the traveller writes one sentence: Lisbon for two, these dates, this budget. A manager hands each part to the right specialist: flights, hotel, transport on the spot, dinner, activities, insurance, travel documents, the budget. The traveller sees a few flights and chooses. Then a few hotels, already within what is left of the budget. Dinner is proposed to fit what remains. The team stops and asks each time a choice belongs to the traveller.

This is Trip Planner, one of the Agentivity showcases. You can watch a real recording on the use cases page. In this demo, the flights, the hotels and the payment are simulated.

You explain, it adapts: the right skills, at the right moment.

  • They say what they want, in their own words. They do not look for the right screen.
  • They see only what their request needs. Not every screen and every setting of the application.
  • Each choice shapes what comes next. A cheaper hotel leaves more for dinner.
  • They stay in charge. The team proposes. The application stops and asks each time a decision is theirs.
  • They receive finished work, not a list of things to do next.

Your need evolves, it moves forward with you. When the person changes their mind halfway, the team takes it from there. Nobody starts again from the first screen.

It is closer to dealing with someone who knows the job than to filling in software.

You run a process: operations, customer service, HR, finance. Your people lose time in forms, tickets and exceptions.

  • Before: a request that does not fit the form comes back three times, or is given up halfway.
  • After: the person explains their case once. The team handles it, and asks only for the decisions that are theirs.

You deliver solutions to clients, as a builder or an agency. Each change asks for a new development cycle.

  • Before: the client wants one more step, and you plan a release.
  • After: you change the team, and the application stays the same. You deliver it under the client’s brand.

You own an application that already works. Your users get stuck on the complicated cases.

  • Before: each special case needs a new screen and a new rule.
  • After: you keep the screens that work, and you put a team behind the cases they do not cover.
WayWhat it isWho is needed
The ready-made portalYou publish a team, and it appears in a portal under your brand.Nobody develops.
A VibeApp of your ownAn application made for one job, connected to your team. Many screens are ready-made: forms, tables, choices, cards.A developer, for the application.
A team inside an application you already useYour existing application calls the team for the cases that need it.A developer, for the connection.

In the three cases, the team itself needs no developer. See One app for one job, or one portal for all your teams.

Shopping Lab shows the first way. A shopper asks for headphones. Nine specialists work in turn, and a report appears with product cards and photos. It is published in a portal, with no application to build.

  • The people stay in charge. The team proposes, and the application stops and asks each time a choice belongs to the person.
  • You change the work without a developer. The team is built and changed in the Studio, in plain words and by drag and drop. The Assistant creates and changes a team from a description. The application stays the same.
  • Your server and your keys. The Community edition runs on your own server, and you bring your own key from your AI model provider.
  • Real work, with people deciding. The other showcases, Invoice Clerk and CV Screening, show teams that do the work and leave the key decisions to a person.
  • A VibeApp can have classic screens too. A list of past requests, a profile page: most real VibeApps mix ordinary screens and a team.
  • A classic application is sometimes the better choice. When everyone needs the same thing, a form is right. See A VibeApp or a classic app: what changes.
  • Each request uses an AI model, and your provider bills you for it.

A VibeApp or a classic app: what changes.