When managing AppSheet apps, especially those in production, ensuring stability while implementing updates or changes is crucial. Whether you’re working within an enterprise environment or managing a standalone app, understanding the right strategies to modify your app safely can significantly reduce risks and downtime.
Enterprise License: Stable Version Management
For enterprise license holders, utilizing the stable version system offers a streamlined approach to manage updates:
- Stable Version Lock-In: You can designate a stable version of your app that all users will see by default. This version is locked and remains unchanged until you decide to update it.
- Version Control: Manage who sees the newest version versus the stable version on an email basis, ensuring that only designated testers or specific users receive access to the latest features.
On-the-Fly Updates ((Caution Required))
While it’s possible to update your apps on the fly, such changes must be handled with care:
- Immediate Corrections: If changes cause errors, promptly fix them to ensure the app continues to function correctly. If necessary, revert to the previous version to maintain operational stability.
- Error Handling: Always check for error messages post-update. Immediate rectification helps avoid disruptions in app usability.
- Timing Is Everything: Make your updates at a time when usages is low, thus minimizing potential impacts.
Using a Development Copy
If you don’t have an enterprise license, creating and managing a development copy of your app is a practical approach:
- Development Copy: Clone your live app but connect it to the same data sources. This setup allows you to make all updates and changes in the dev copy without affecting your live environment.
- App Upgrade Feature: Once you’re ready to transition your updates to the live app, use the “App Upgrade” feature to clone your dev copy over the live version seamlessly.
- Continuous Development: After upgrading, continue your development in the dev copy, preparing it for the next set of updates.
Handling Structural Changes
Structural changes, such as adding, removing, or moving columns, are sensitive and should be handled during downtime:
- Downtime Planning: Make these changes when no users are active, and no automated processes are running.
- Synchronized Regeneration: After modifying your tables, refresh both your live and dev apps to recognize these changes. Initially, you can keep new columns hidden in the live version while you finalize adjustments in your dev copy.
For major version updates, refer to the “How to manage Major Version Updates (when you have users in the wild)” from my AppSheet Explained series, which offers detailed guidance on handling significant updates.
Effectively managing updates in AppSheet apps requires careful planning and execution, especially if the app is in active use. By leveraging the described methods suitable for your licensing level and planning structural changes during off-peak periods, you can ensure a smooth operation and enhance your app’s long-term reliability and performance.