Buildr turns a written description into a working application. You write a few sentences, choose whether you are building for the web, for iPhone, for Android or as a game, and the app is generated and rendered in a live preview beside the conversation. From there you refine it by asking for one change at a time.
Why we metered it in credits
Generating an app costs real money in model calls, and hiding that behind a flat seat price would mean either charging light users for heavy ones or quietly throttling everybody. Credits make the cost visible: a small focused edit is about half a credit, a full generation is a few, and the cost of every message appears in the conversation once it lands.
Every account gets free build credits each day. Plan credits roll over; purchased credits are always spent last so they keep their value.
The parts we are careful about
Two things in this product are easy to fake and we have chosen not to. The first is store publishing: we generate the listing text, enforce the real character limits and produce artwork at the exact sizes Apple and Google ask for, but actually sending a signed binary needs a build service, a developer account and signing certificates. When those are missing, the submit button fails with an explanation instead of showing a fake progress bar.
The second is your keys. A key you add goes into an encrypted vault; the database keeps only a reference and the last four characters. Keys are used server-side only and are never included in an exported project.
What comes next
We are working on the pieces that turn a generated app into a shipped one: a build service for native targets, deeper store integration, and more of the generated backend under your control. When those land, they will be described here the same way — including their limits.