This is more of a curiosity than anything else… I was wondering how Glide handles screens/forms/etc that were built in the Editor, but configurations had to change (app re-worked or processes updated) that mean these previous screen’s are hidden away and no longer accessed.
I’m asking because I have an app that I’ve had to re-work in multiple ways and each time I do something like remove a form button, for example, if I add it back later, I have to rebuild the form ---- is that old form actually gone, or still taking up resources in the app? Same goes for screen configurations… It has happened before that I’ve created a screen that ends up not making it to production… Then I’ll work on another part of the app, add a link to screen action somewhere, and that original screen layout comes back because it still exists.
My concern is that all this background configuration/layouts/forms may have the potential to cause unnecessary loading/performance issues in my app.
Is it worth starting fresh now that I have “final” product to create in order to have the “leanest” version of the app in production?
