Apps use less machine time and reopen on their own on mobile

Every app you build runs its handlers on a machine that starts when someone uses the app and stops once it sits idle. It now stays ready while someone is using the app, so a click never waits for it to start, and stops two minutes after the last sign of use instead of five minutes after the last request. An app left open in a hidden tab or on a phone in your pocket no longer wakes its machine to refresh data nobody sees; it catches up once you look again. On the mobile app, an app the phone paused while you were away reopens on its own, on the page you left, instead of showing "This app didn't load".

How it works

• Warm while you use it. Moving the mouse, tapping, typing, or scrolling in the app keeps its machine ready, and starts it if it had stopped.
• One flat rate, billed to the end of the idle window. An app's machine time costs 80 credits an hour, by the second, whichever machine runs it, and ends two minutes after the last use, never when cleanup runs.
• Opening an app starts its machine only when it needs one. If what you are about to see was saved on a recent visit, the app opens on it without the machine.
• Hidden apps wait. Another member's change, a finished agent run, or a new build is held while the app is off screen and shown once it is back in front.
• A quiet relaunch on the phone. When iOS or Android frees a background app's memory, or its session runs out, the app relaunches up to twice before saying it could not load, and waits for the network when the phone is offline.