What a Kaddy app is made of
The parts of every Kaddy app: its records, its screen, and its assistant; the two conversations you have with it; and how a change is previewed, applied, and undone.
What an app is made of, what its screens can show and do, how you talk to it, and who can see a shared app. Written for someone deciding what to ask for.
A Kaddy app is three things: the records it keeps, the screen you use them through, and an assistant that knows both. You talk to it in two separate conversations, one for using the app and one for changing it. Record changes in Chat happen when you ask; changes to the app itself stay in a preview until you apply them. This page is the map; the other Docs pages go into each part.

The parts of every Kaddy app: its records, its screen, and its assistant; the two conversations you have with it; and how a change is previewed, applied, and undone.
What a Kaddy screen can show: page layout, live lists of records, forms, summary numbers, controls, dialogs, and the appearance Kaddy handles for you.
What a button, checkbox or switch on a Kaddy screen can do; how named actions work; why a press can wait for your approval in Chat; and why a total is shown complete or not at all.
What an app's assistant can do in Chat and in a live Voice call, how it hands a change to Code, what it remembers and how to correct it, and how a scheduled run works.
Who can see and change a shared Kaddy app: what a viewer gets, why an editor is trusted like the owner, what a public link exposes, and what only the owner can ever do.
The capabilities of a Kaddy app in one place: records, screens, actions, an assistant with memory and voice, connections, sharing, versions, and backups.