Build your own app

Switch the mode above the message box to Extend and describe what you need. Plainly, the way you would explain it to a colleague.

"We lend equipment to customers. I need a register: which device, which customer, out since when, back when, and a note. Plus a list of the devices themselves with a serial number."

That is enough. You get two tables, the link between them, forms, lists and a record view.

What makes a good description

Name the things and their fields. "A loan has a device, a customer, a start date, an end date and a note" beats "track our equipment".

Say what belongs to what. A loan points at a device and at a customer — say so, and the forms get dropdowns instead of typed-in names.

Leave the layout to it. You are describing what the app knows, not where the buttons go.

Trying it out

The app appears in your list right away. Put a real record in and look at it — five minutes with actual data tells you more than reading the description again.

If it is not right, say so in the same conversation: "The end date should be optional", "Add a condition field with new, good, worn". It changes the app in place; your records stay.

When it is ready

Until an administrator shares it, the app is yours alone — see what Extend is. Share it when it has earned its place in the list.

What it cannot do

Extend builds structure: tables, fields, links, views. It does not write background jobs, it does not send anything out of the house, and it does not touch the five built-in apps' own data structures — for those, see extend an app you already have.