I agree with both of you @Darren_Murphy and @Fred_Marker. I think the most basic features should be easy and perfect as far as usability (they are far from it), so that noobs are able to use it and to create mass adoption, but having advanced features is super helpful for those who want and are ready to take it to the next level. If Glide was my project, I would first iron out all the basics as far as usability before I add more advanced features. Usability testing should be a part of the development cycle in any software project, but it RARELY is, unfortunately. You don’t need to be a genius to see that no usability testing was done here at all. Glide can get away with it because it’s super cool and you can still do a lot with it AND because most users are tech savvy still.
for every problem, there is an equal and relevant solution…
would you like me to try solve your technical worries?
Can you make Glide more user friendly? This is my only worry.
i do it every time i visit this magnificent platform of creative people…
i see that you would like to make things better … what is that bother you the most?
See all the above usability issues I reported. What bothers me is prioritization. For example, Dark Theme is unusable as it is, and should be very easy to fix, but Glide team is not prioritizing it, so I can’t use it.
have you ever try to look at Code BOOK?
In Glide you can solve problems… it is very flexible… take a look at this App:
Glide created a platform that you can go around problems… customize it and run it like your own creation… if there is something missing… in view days… weeks… it will be there…
but always there are gates to make it on your own, not waiting, creating happy solutions and giving a way to new features.
Thanks but you are missing the central point. The Delete button is just the most glaring example of Glide overlooking the end users’ perspectives and actions. Perhaps this feature request is misnamed.
If you have to create work arounds to fix the faults and deficiencies of the native features and components, then Glide has failed at usability design and testing, as well as creating a true no code platform for the stated target audience of a billion non professional app makers.
That’s right @Fred_Marker ,for some reason @david changed my origintal title to a title that is misleading. My original title was “Usability jumping through hoops” or something like that. I now have changed it back. Let’s make this topic all about usability issues, and hopefully the Glide time will make it a priority.
I am almost 100% sure that Usability Testing is not a part of the development cycle of Glide. It’s obvious to anyone who’s ever performed Usability Testing. But like I said, not a lot of developers bother to do it because it’s inconvenient and takes time and attention, also - there’s just not enough awareness.
Thank you for this, you gave me some good ideas, especially about delete confirmation 
Cool resource, thanks!
TBH I think it’s not good practice to allow delete when in “edit mode”. Surely the delete button should be in the prior view?
Yes. That’s a bit annoying. However you should try to get a usable dark theme with some of Glide’s competitors. Almost impossible in my experience.
Out of interest, what other nocode platforms have you used? Do they implement your requirements in a preferred manner?
When deleting a column, Glide can be unreliable-enough, so it would be good to know that a column is really the right one when you want to delete it. For instance, in one Glide Table, I have @@already just deleted@@ the column - rel-collecttest (as the sheet does not exist… and I can see in the dev console that it throws up errors). BUT the column is not deleted.
Now, maybe it is deleted and I am about to delete the next column … a very important one.
How can I know which column is going to vanish? It would be nice for the warning box to give more info on what is being deleted - thanks!
I’m curious, based on all the Sample Pro Apps they are pushing, (CRM, Field Sales, Delivery, Inventory, Property Management) along with their push towards Enterprise, that Glide’s focus is currently on Apps to help Businesses with internal customers vs external ones.
Customer experience for Internal Business Users typically takes a back seat because they are “forced” to use it. It seems like a lot of us in these forums though either build apps for our own B2C business or have clients that are B2C, thus customer experience and design are a top priority.
Of course Glide has things to improve, but as any businesses (in particular when it is young - 2 years), Glide has to make a choice in terms of positioning between focusing on b2b or b2C.
Glide’s choice seems to be b2b (and in particular SMBs), with apps created either by the b2b itself or providers.
In this context, yes, UX/UI remains important, but less than in b2C since it is a working tool (have a look at SAP UX/UI…).
On the contrary, the width of possible Functions to buid is key given the multiple ‘vertical industries’ and associated use cases.
So, when you decide to invest 1 Man-Day to have your platform evolved, you focus on your priority.
By the way, no change takes 5 mn when it comes to deploy in Production.
This is filed as a feature request. I changed the title to what I thought you were asking for, because “Usability jumping through hoops” does not look like a feature request.