WebRobot

Designing an app · Lesson 6

Events and checkpoints

An app is not only what people click. Records arrive, dates come due, clocks tick, people decide: each is an event, and the manifest says what each one starts. This part runs without any model: whether a trigger fires is decided by rules, the same every time.

Use Next, or the ← → keys. Fire the events, edit the cron, move the day, type a company: every answer is computed by the runtime’s own functions.

Sources and actions

Who protects you from loops

A trigger whose agent writes the collection that starts it is refused unless a where breaks the cycle; on top of that, the runtime starts at most twenty triggered runs a minute per app, so a mistake that slipped through still stops.

What to take away

Next

Lesson 7 is about money: how the app’s users pay, how the price follows the work, and how limits protect the owner.

Lesson 7: Money, billing →

← The whole path