Arrays as source of Choice options and actions when a choice is made
More formatting options for buttons and containers
A container/list view that truly looks like a table of data displayed in programs like Excel spreadsheet with ability to format column and cell dimensions (to use space efficiently)
Please please upgrade the Charts options, we need more chart types and basic formatting options
Continue the amazing AI journey
Import spreadsheet option with ability to append to existing data or overwrite existing rows
lastly - please find away to make the Advanced API column available for Pro subscribers, e.g. with limited functionality like Get only
Providing the payment button is one of the components that Glide explicitly said to not be brought over from the Classic Apps, and their focus on internal apps, I doubt they will do something like that.
Calendar - choose colors of events, choose start and end times for day view instead of 24 hour
Map - control zoom when only one point is showing
Zapier - search for rows action
I had the same issue with my app. The only solve I came up with was to have multiple image columns, each with a different name that is displayed in my app.
-Choose day-start and day-end cutoffs (so 2am doesnāt show, highly irrelevant to 99% of applications). Only display hours needed.
-Let user select custom block length (30min, 1hr, 4hr, etc). Custom, no dropdowns.
-Allow custom colors so calendar types can be categorized.
-Other custom inputs as needed for most scheduling applications. Thatās the desire here.
Invest in being best-in-class with Calendars - make them industry leading from UI to integration. Businesses revolve around calendars - be better than the rest; be THE BEST. From this thread I see I am not the only one.
Create an extension of USER table ā accessible EXACTLY the same as USER table in actions and components ā for storing app-specific local data. Make them free of cheap (1/20th the current cost) by not backing them up. @Jeff_Hager and @Robert_Petitto are more eloquent about the design and usability.
Provide both a Primary Table Row for screens (like currently) and a Secondary Table Row (new). This would solve 95% of challenges when designing logic within the action editor. For example, creating a many to many relation means usually having two objects available at the same time to create/populate a third object. This may be a big lift but it will dramatically simplify creating business Apps (especially integrating with outside apps) cause the hardest thing to do with Glide is to figure out how to get to that āotherā piece of data from within an action sequence and correlating them.
Congrats on all the great work and energy the team has put in - the results speak for themselvesā¦stellar.
Airtable to only import data that sits in a view (this would save me a lot records, updates, etc.)
Builder/Designer:
Would love to see more components (tabbed containers, etc.)
Nested navigation (If someone clicks on a tab in the navigation, a sub-navigation layer)
Ability to change the hex code for the dark/light mode, not just accent mode.
Add maybe another color option besides the primary accent. Definitely donāt think we need a full color palette but just being able to add 2-3 colors would actually go a long way in customizing the experience.
Make the content in containers collapsable.
Automation:
Folders for Automations and ability to rename Automation steps
API:
Update user-specific fields (i.e. select user by row-id and update field)
ā¢ Option to make more form components required fields such as checkbox and switch.
ā¢ More columns and column types for the Table Collection.
ā¢ Actions and saved column widths for the Data Grid.
ā¢ Option to upgrade to more than 25k rows. Or bring all functionality of Glide Tables to Big Tables.
What I mean is, I have a great app I want to resell to similar organizations. How can I maintain one ācode baseā (template?) that I can update to continuously improve a dozen apps with common functionality (for different clients)?
