Maybe, maybe not. You thought is additional work for the dev team. So if they are already in the code making automation changes, what else can they do that seems straightforward and improves quality of life for HexOS. My thought is a very small improvement but I have noticed that is the app is stopped and I try to do an update, it seems the update process hangs. In my head like your snapshotting potential improvement request to "simply" tell the process to 1) check if an app is running, 2) stop it if it is, 3) do snapshot, 4) do update, 5) restart app. For mine it's similar as it's when the update button is clicked 1) check to see if the app is running and start it if it isn't, 2) do snapshot, 3) do update and 4) return the app to original state. Both would take work to do but could make things simpler. I know we are making some assumptions that HexOS knows the state of the app but since is displays that info it seems that is available. The problem is similar with both our thoughts in that the update process needs to know what to do if the app won't stop or restart as needed. Seems like nothing is really ever simple and it's tough to know how much is to much.