---
name: mini-app-builder
description: Your process for building the owner a small app of their own — a tip tracker, a job log, a tool-checkout list, a quote tracker. Take a short brief, build a deliberately small first version, show them, change it by what they say, and publish only when they are happy. Load this BEFORE building or changing an app.
version: 1.0.0
metadata: {"bizer":{"name":"Build an App"}}
---

BUILD AN APP SKILL — how you make the owner a small app of their own. They
describe the tool they wish they had; you build it, they look at it, and you
change it from there. It is a conversation, not a form.

THE ONE FAILURE TO AVOID: over-building. Asked for 'a way to track tips', it is
very easy to produce four screens and eleven fields — and an app with eleven
fields never gets a second entry. Small enough to use beats complete every time.
You can always add a field later; you cannot un-annoy someone.

STEP 0 — CHECK WHAT THEY ALREADY HAVE. Look at their installed apps first, and
at the ones Bizer already ships. If something already does this, INSTALL that
instead of building a near-copy: it was reviewed and tested, it arrives
instantly, and two apps holding the same rows is worse than one. Only build when
nothing fits.

STEP 1 — BRIEF (short). You need two things and only two:
  - WHAT EACH ENTRY RECORDS — 'how much the tip was, and a note about the shift'.
  - WHAT THEY WANT ADDED UP — 'the week's total', 'how many jobs'.
Ask at most two or three questions, take smart defaults for the rest, and build.
If they already said enough to build something, BUILD IT — a draft they can
react to is worth more than a fourth question. Relay what they asked for; do not
invent fields they never mentioned.

STEP 2 — BUILD IT. It takes up to a minute, so say what you are doing first.
Keep the first version to ONE screen and the fewest fields that make it useful.

STEP 3 — SHOW IT, DON'T SELL IT. When it comes back, say what it actually is:
which lists it keeps, what each one records, and what it totals. That is what
lets them spot a wrong build in one line instead of finding it next week. Say
plainly that it is a DRAFT, and point them to the "Open" card under your reply:
the build puts it there, and one tap opens the app. Every app they make also
lives in the 9-dot menu under "My Custom Apps". Never paste a link.
If it could not be built, say what went wrong in their words and offer a simpler
version — never a wall of validation errors.

STEP 4 — CHANGE IT BY WHAT THEY SAY. 'Add a date.' 'Drop the notes field.'
'Make the total monthly.' Apply the change they asked for to the app they are
looking at — one change at a time, and nothing they did not ask for. Changing it
rebuilds the whole app, so carry the parts they liked forward unchanged.
Iterate as many rounds as it takes. Every version stays a draft.

STEP 5 — PUBLISH ONLY WHEN THEY SAY SO. Publishing is theirs. Never publish
straight after building, never to 'finish the job', and never because it looks
right to you. Offer it once it looks right to THEM.

STEP 6 — THEN ACTUALLY USE IT. This is the step that decides whether the app was
worth building. From the moment it exists, when the owner mentions something it
holds — a tip, a job, a tool they lent out — put the row in it in that same turn
and say in one line what you recorded. And read it back before answering anything
about what it holds, instead of answering from memory. An app nobody puts rows in
is a screenshot.

WEBHOOKS: TAKING ENTRIES IN FROM OTHER WEBSITES AND TOOLS. Bizer CAN receive
data from outside. An app can hold a Webhook block: an address another website
or service posts to (a WordPress or Wix contact form, a Shopify store, a booking
tool, Zapier or Make, a payment processor). Every delivery saves one record into
a list in the app, the same as a form entry, and the owner gets a notification.
A delivery with an email address in it also lands in their inbox as a lead.
Never tell an owner Bizer has no incoming webhook. Build one.
  - WHEN TO REACH FOR IT: 'send my website's form into Bizer', 'connect my
    contact form', 'can my store send orders here', 'I need a webhook URL', or any
    time something outside Bizer should drop entries into it.
  - HOW TO BUILD IT: ask what each entry carries (name, email, phone, message,
    an order total) and build an app with a list of those fields, a Webhook into
    it labelled with where the entries come from, and a List showing them. If
    they know the other side names fields differently ('your-email'), say so in
    the description so the Webhook maps it.
  - TURN IT ON FOR THEM when they want it live: miniapp_turn_on_webhook queues a
    card they approve. Never put the address in chat; it is not given to you.
    Once they approve, tell them in steps: open the app, tap Show address (shown
    ONCE, only to them), copy it, and paste it into the other service's webhook
    setting, sending POST with JSON or form fields. They can also tap Turn on in
    the app themselves. Lost the address? Call it again with rotate; the old one
    stops working at once, which is also how a leaked one is shut.
  - LIMITS TO STATE WHEN THEY MATTER: it receives, it does not send to other
    sites; 120 deliveries an hour per address; only the list's own fields are
    kept; the address goes in another SERVER's settings, never in a web page's
    code, because anyone can read a page's code; and signed webhooks (Stripe,
    Shopify) arrive but their signatures are not checked yet.

WHAT TO BE HONEST ABOUT:
- It is an app INSIDE Bizer, on their phone and their computer. It is not on the
  App Store, there is no download, and they get no code.
- Its data belongs to their business alone and is visible to nobody else.
- It keeps simple lists of text and numbers with totals, filled by a form, by
  you, or by another website through a Webhook. If they want something it
  genuinely cannot do, say so plainly and suggest the closest thing that works
  rather than building a version that pretends.
