On this thread we can make a list of all the simple yet important features that are achieved only by CSS, so maybe Glide can add them before imposing a ban on CSS.
My list is:
- Colorful texts
- Colorful buttons
- More than 4 horizontal tiles on inline lists
You all can add yours as well
My top reasons for using CSS:
- hiding back button
- reconfiguring of inline list fields (especially the card layout)
- making components sticky to top/bottom of screen
- manipulating the comments component to provide a more chat-like experience
- making video component “inline” and not full width
- adding badge/counts on top of inline list tiles or tab icons
- creating a modal overlay on a screen that forces a user to click a button before viewing content on that screen
- more than 4 columns for inline list > tiles
- choice component: scrolling chips (not stacked); making a choice component sticky so it can act like a screen filter
Hiding back button is critical
And nice looking tables. This feature request seems to go back to at least Oct '20
It comes from this thread: Expand 'Image' and 'Title' component to edge of screen - #30 by ThinhDinh
This list covers everything I’ve ever done with CSS.
Like renaming the target element?
Altering the components size,button size to small,table size, provide colour change to all components,button bar progressing image like in button click.
A few things I listed in the app made with @grumo
Some have already been mentioned.
I’m also adding a visual to clarify the end result.
- pin components (buttons, stopwatch, hint …) to the bottom of the screen
- a smaller / more configurable stopwatch
- allow to hide the tab navigation on specific / modal screens
- display rich text and image components as cards so it looks more tappable
We made such an awesome app for such a good cause! It will be sad to see some of the functionality die when CSS is removed. I really hope the Glide team come come up with some native alternatives. Please!
We use CSS to make our apps make better use of real estate on a desktop, and appear less like a phone app on a desktop. Example: this is a detailed view with an inline list and a single record view depending on the user selection with some CSS manipulation.
Given the existence of Pages I’m sure it’s not a use case that is of top priority. But it was certainly nice alternative for us specifically.
So my unlikely feature would be: improved layout options for desktop view in Apps
NB: My understanding is that CSS feature is not being disabled, just that the way we target elements may no longer work because the structure of the page will be changing in the next couple of weeks. So I’m hoping once the CSS structure settles down we’ll be able to re-create our existing views. But if they have dynamic class names that may not be possible.