I had a question about editing, is there a way to make edits or changes to your app to see how it works and looks, before you re-publish it for users to see?
I also noticed sometimes when I create new columns in my sheet, they get added to the bottom of my components for a certain tab. When does this happen?
Regarding columns being added to the bottom - you should get a pop-up message in Glide each time you add a column asking if you want to add the new column, just click no.
No.
You can create a copy of the app using the same sheet and do you changes and then if all good make the same changes in the main app if its used UI. If changes are in sheet then copy app with sheet. No other go as far as i know.
Publish Control is an extreme challenge and will for sure fire back if compatibility not counted for.
Take this scenario, you implemented three “tweaks” 1, 2 and 3. in which 3 depends on 1. User decides to publish 3 but not 1, what’s going to happen?
In my opinion, and as suggested by @Coupons_Deal , user can have two apps, live and test. and once a new feature is validated on test, he/she can roll it to Live “carefully”
On this point, I respectfully disagree with you. In an Orgs environment, you would then pay for both apps. I’m looking at PWA like a Website in terms of publishing…you publish all changes when you push. If you want to publish one change, you work on that one change and publish it then you start working on another. This would be highly preferable to things just popping up and constant refreshing on the user side because you’ve made one tiny change. Duplicating tabs that have conditional visibility, putting conditional visibility on items you’re working on, it’s all just one big complicated and unnecessary messy work around with too much reliance on human care. None of it is a long-term replacement for proper publishing control. Having two apps is another workaround that I don’t want to get into when publishing control is a fundamental. Being careful is a given, but that’s totally different than the minefield of potential mistakes we are navigating under with the current conditions. Of course Glide should ensure it won’t backfire. It is complex but also standard.
That’s the tough part for Glide! We all have different opinions and preferences! Glad we have a voice here and we can have some influence/impact through our collective dialogue!
I have businesses added continuously via a google sheets form so the sheet is always changing. How do I make a copy of the app without making it copyable?
I guess I will have to do these if needed in the middle of the night if someone is using it. Is there a way to put up a maintenance note or take it offline for a while? I know sites always do that, it would be cool to do that for the app as well.
Yes you can do it. Have a One Row Sheet with maintenance flag can be true/false Yes/No 1/0 any such condition. Then create a Tab which shows maintenance page. Based on your maintenance condition show this and hide everything else
Regarding the first point, you can make copy of any existing app which you see all your apps. What do you mean by “without making it copyable”?
In my model the customer gets a link to a Pro app that I have created. They use the app with no concept of Glide or any other services being used behind the scenes (e.g. Integromat or Zapier).
From time to time they will request a new feature (maybe chargeable) or find a bug (rarely, clearly …). I then need to work on the app to essentially create a new version, so I very much share @Deena pain in this respect. It is a nightmare trying to hide stuff while you work on it, let alone perform testing.
However for me, I would prefer the more traditional “staging” or “draft” environment for dev and QA which could then be “made live”. I think that offers the best blend of flexibility and ease of use.
I’m not saying this is easy to do, however I think it’s essential when you are building apps with any level of complexity for customers with demanding requirements. Glide fits the bill in terms of creating the apps, no question, but is not there yet in terms of maintaining them.
Yes, I was thinking of a ‘draft mode’ then hit update once all changes are made. You can’t save the changes as a draft since it’s already published, but once your ready hit the update button.