Vibelets

Watch it. Build it. Remix it.

Build an app: Track customer requests and handovers

Give each customer request a responsible person, deadline, status and next step. Watch a shared work board being built to make team handovers clear.

← All demos

Small idea. Real app.

What you will build

Give each customer request a responsible person, deadline, status and next step. Watch a shared work board being built to make team handovers clear.

Make responsibility visible so requests do not get lost between people.

01 · SEE THE PROBLEM

A customer is waiting. Who owns the request?

Everyone assumes someone else is handling it. See why clear ownership and next steps matter.

40 seconds · Animated story: Someone Else is on it.

02 · WATCH THE BUILD

Build a customer-request and handover board

Follow the real build of a shared board with request owners, deadlines, statuses and next actions.

58 seconds · Real prompts, refinements and app footage

03 · REMIX THE VIBELET

On It

This shared board uses fictional requests. Everyone can see demo edits. Remix it for your own work; your copy has its own data and requires a Vibelets account.

Prompts you can start with

Initial prompt

Build On It, a polished mobile-first shared work board for a small office. A customer request or task has a title, a person responsible (George, Lily, Felix or Nora), a due date, a status (New, In progress, Waiting, Done) and a clear next step. People can add, edit and finish requests, filter by responsible person and search titles. Persist requests in Vibelets shared collections and synchronize open views. Use a small fictional example workload, and provide Load example work when a fresh remix is empty. Make every field accessible with a visible label. Use cream, deep teal and warm coral accents, clear cards and reassuring typography. No AI, email, integrations or additional login. Build now and make sensible decisions.

Refinement

Improve On It while preserving all requests. Add a top-level Overdue filter that excludes completed requests, show an unassigned count, and make the next step prominent on each card. A new request should allow Unassigned until someone takes ownership. Include a clearly visible activity note when status changes, using the saved request data rather than invented history. Keep owner, due date and next step editable on phones. Add the small shared-demo notice: changes are visible to everyone; remix your own copy for real work. Preserve shared live updates and the empty-copy example loader.