SkieHow do releases of the Skie app work: publish, pause and stage?
A new version of the Skie app is published as a release, rolled out in stages to chosen organisations, and can be paused if something looks wrong. Devices update themselves and verify a checksum before installing. The releases screen is where the Skie team controls this; your Insights show how far each release has reached your devices.
Updating an app on hundreds of devices is risky if everything changes at once. Skie handles this with staged releases. A new version is published, offered first to a small set of organisations, and widened only if it behaves.
Publish makes a version available. Stage controls who receives it and in what order, so a release can reach chosen organisations before others. Pause stops a rollout in its tracks if something looks wrong, so no further devices pick it up until the issue is understood. Devices update themselves, and each one verifies a checksum before installing, so a damaged or altered file is not installed.
The releases screen is a control for the Skie owner and technician roles. As a customer you do not have to do anything. What you see is the result: the share of your devices on the latest app in Insights, and the release stats described in release stats explained. If your pilot organisation is chosen to receive new versions early, you may see updates before the rest of the fleet.
A staged approach means two devices in the same school can briefly run different versions. That is normal and is visible in Insights as the on-latest-app figure. See on latest app. Devices that were offline will update when they reconnect.
Skie does not push-install other apps automatically yet. Apps are managed through app lists and the organisation app store, with draft and Publish. Practical tip: if you want early access to updates for testing, say so when you plan your pilot.