When a user opens an app, it will first retrieve the latest published version. From that point onwards, the user works with that published version of the app.

Publishing an update will create a new version. So users that already had the app open, will continue to work on that version until they refresh the entire web page, which will then display the newly published app.

Functionality created inside the app will continue to work in published apps, no matter if you are updating a draft or publishing a new version. So if you would delete a page in your new version, users will still be able to visit that page in the old published version they are interacting with.

However, changes done to server-side objects, like automation scripts, GQI ad hoc data sources, ... could cause problems for older versions, if the contract gets broken between the app and the server object. Adding a new required argument to an ad hoc data source for instance will break the queries in the apps that do not have this argument linked yet.

For now, there is no notification yet when a new version gets published. It happens out of the box the next time you open the app.