Too many columns

I love Glide and the way it has sheets and tables as we know it as the starting point for building apps, but everytime I build something with a lot of columns I think: it would be nice if there was a way to do things in a different / simpler way. I’m no UX designer but It feels that there are improvement options there. Hope so!

1 Like

like what? I do many platforms and really advanced coding… Glide is still my favorite for great fast apps

in Glide … specially Apss you can do anything you want… CSS… JS… GS… GAS… HTML

Like I say, I’m no UX designer, I don’t have the solution but I feel the problem.
And this is not about advanced or not, to me, it’s about data presentation.

just ask… and I or others will find a solution…

Thank you!

1 Like

UI especially in Apps is almost unlimited… just try my Code BOOK or my calendar… click my image… there is no website that can do that… for free… both of these links were made using free Glide accounts

I agree about the front end, but I am talking about the back end. The data editor. When you end up with tens of columns that look the same and as important as eachother.

wow… have you tried GAS? I have thousands of lines of code to do just a few elements in Glide… I know is much faster execution and millions of times more possibilities than Glide… but… I can do the pp in few hours and collect money

Are you using Column Grouping?
I find that helps a lot to keep things organised in the Data Editor.

1 Like

i just wanna say… editor is not like the code editor in google… but… we don’t need to create thousands. lines of code to do simple tasks

We are both on the other side of the spectrum. You are a technical man that uses no code to do things faster and still uses code to do the extras. I am a non-technical person that loves Glide but thinks it can (always) be simpler and clearer. We both may be right :wink:

no… from my end … Glide is doing an excellent job to put together so many factors… it blows my mind, that they even try

Even good things have room for improvement.

I know … today we have so many systems that can do things… these systems took years to develop and a humongous amount of $… platform like Glide is one of the tops for sure… and for a guy like me… I just can’t believe is real… i have a huge respect for Glide, but I know I am their biggest headache lol

1 Like

That’s what I was thinking :wink: I only think something can be better and the man that’s criticizing Glide so often becomes their biggest defender :wink:

yes… I do… my business depends on Glide in 60%… and Glide gets their $ from my customers… so it is very circular dependency situation lol

1 Like

You seem to always have good intentions and you bring so much to Glide and the community of fellow Gliders.

Hey, thanks to you I might even start doing some Google AppScript someday. (But don’t hold your breath : )

1 Like

I… do… but sometimes it looks bad because of my English… or protecting my business…

If you are talking about the design/presentation of your data tables, I’m a little like you, I get uncomfortable when tables get messy.

Things I try to keep in mind:

  • You know how in Excel, you can have a formula in one column, then another formula based on the output of the first in the next column, and so on 100 times? 100 columns. In Excel though, you can “merge” all of those formulas into one column with the onion method: you put one formula into the other, then into the other, and so on 100 times. Monster formula. One single column, it’s “clean”. We just can’t do that in Glide, it’s one computation per column.

  • But, big but: boy is that monster formula difficult to work with, maintain, audit. Having separate columns is, in a way, the clean version. Maybe not visually because it all spreads out, but all the columns/variables are not intertwined with one another in our tables in Glide. That feels good.

  • So to “merge” things, as Darren suggested, grouping columns is the way to go. Really, reminding myself that it’s one variable/computation/piece of data per column makes me feel better. Grouping columns by feature built is usually how I do now.

  • I also try to imagine how it would be in the coding world. I’m like you, I’ve never coded. But I imagine that coding create variables all over the place to store data. Some long term variable, some short term variables (columns in our working tables). Each variable in coding is probably a column to us in Glide. I’m willing to bet managing those variables in coding gets messy, that duplicate variables appear all over the place if the code is not clean, not maintained properly. So if it’s messy in the coding world, I find it reassuring that the same might happen in our visual coding world as well: tons of variables, tons of columns, same same.

  • Remember that “Hold my beer” moment where Jeff solved a problem in one math column where it took Darren 40 columns? When building new features, I keep that moment in mind and try to visualize how I somehow could simplify things. I often find myself thinking to myself “What would Jeff do?” Then quickly thereafter “What would _____ do?” (the Darrens come to mind, Bob, Thinh, Uzo, Lucas, Marco and Vincent, etc.) If you listen carefully sometimes you can almost hear what they would say : )

  • There was a discussion a few weeks ago about if a table gets too big, is it good practice to split that table? I’m not a fan of splitting tables, but Gvalero commented that in the coding world, database normalization calls for more tables with fewer columns rather than fewer tables with less columns. I don’t know. But I keep in mind that comment.

Not much practical advice here, mostly the way in seeing things, but I hope it helps.