I’ve been working on an AppSheet app that uses a MySQL backend, but only discovered late in development that we’d need an Enterprise license in order to deploy, whereas we only have the Core license. The app will be very infrequently used (by students to update personal details), perhaps only once or twice/year but across approx. 2,000 users. I can’t justify the increased license cost for that (whatever that might be - Sales are yet to contact me over a month after filling in the form), but I’m wondering what the drawbacks would be (if any) of not deploying, and instead just sharing the preview links? I know that for some apps caching would be a benefit of deploying, but not in this case where data needs to be fetched and updated live in any case, but are there any security drawbacks?
Many thanks SkrOYC; I feared there must be some limitation. We’ll likely be developing a custom web app in that case. It’s a shame the licensing system doesn’t allow for cases such as this, especially given the low demands of Google’s infrastructure for such an app when compared with one using Sheets, for example, but we’ll still be using AppSheet for other internal purposes.
Yes, I’ve been using Appsmith for other projects; we have a self-hosted AppSmith instance currently in use and so will see if we can get that to work in the same way. AppSmith also has its own limitations though, involving user registration requirements that I was hoping to avoid with AppSheet, but with an upgrade I believe we can use OIDC so will look into the cost of that.