Building and changing apps · Describe an app in words
Working in Bike
An app and its sheetsThe Data tabViews and the boardYour InboxWaiting on meEach app's own how-toSearch with ⌘KPeopleBuilding and changing apps
Describe an app in words
Say what you need on Home, and Bike writes the app out for you to read before it's made.
For admins.
Track supplier bills, matched to their purchase, and paid only once approved.
Bike replies with the app in plain words: its sheets, steps, who sees what and what happens by itself. Reply to change it, attach a spreadsheet to bring in its rows, and click Create. What a new app needs from the apps you have is listed under Also changes and applied with it.
Building an app well
- A list in place of typed text: a choice question, or a sheet of its own (Categories, Contacts) that rows link to, so names are spelled one way and each one can show what's linked to it.
- Totals: a computed question can add up the rows that link to a row ("Spent this month" on a budget adds up the entries that point at it; "Lifetime revenue" on a contact), here or in another app, counting only rows at some steps if wanted.
- Two apps work together through a link (an entry picks its invoice in Invoices) or a rule (a hired candidate starts an onboarding plan). An app that does a different job is better as its own, connected, than as a fourth sheet.
- Things that sit under each other (cost centres, categories) as a tree: each row names the one it sits under, a total can include every row under it, and Bike refuses a row under itself or under a row below it, and deleting a row that has rows under it.
- Balances as a ledger (leave days, stock, fees due): each entry adds or takes an amount for a person or a row (an item), and Bike keeps the balance after each entry and on the row it counts toward. An entry is never changed or deleted: a wrong one is reversed, once, with Reverse, which adds the opposite entry. A ledger can say its balance never goes below a number (stock never below 0), and Bike refuses any entry, from a person, a rule or an import, that would take it lower. A rule can add an entry (an approved request takes its days off).
- Values by date (a price list, salaries, spending limits by category): each row says what it's for (a product, a person, a category) and the date it starts; Bike keeps Until, the day before the next one starts, and allows one row for the same thing on the same day. A row already in force can't be changed or deleted, so what applied on a past day stays: a change is a new row from the date it changes. A row still to come can be changed or deleted. A check or a computed question elsewhere reads the value in force on its own date (an expense within its category's limit on the expense's date; a quote's price on its date).
- Steps for anything that moves through stages (Draft → Sent → Paid), with who may move it and who it waits on; a check that a row must pass before it's saved.