I am not questioning the number of Glide engineers that are on staff, nor am I questioning their work ethic, productivity, or assigned tasks. I am simply pointing out that there have been a handful of announcement posts recently in which users have been challenged to integrate AI into their apps; yet, since the official launch of Glide Pages / (new) Apps nearly 2 years ago, there have been requests on requests on requests by the user base for the features that I mentioned and it’s been either conjecture by forum members or total radio silence by Glide staff until you responded a few days ago.
So that all forum users are clear: how many more duplicate posts and feature requests are needed for these to be added to the roadmap? The workaround for our users to zoom in/see an image enlarged is absurd - not to mention impossible - if they have no internet connectivity. And, forcing users to scroll to the bottom of a (sometimes) very long screen just so they can return to the previous one (when there is a custom action tied to a non-floating button) is cumbersome and ugly. These are strange features to omit especially when they’ve been requested so many times; having them only help us make our apps that much more visually appealing and user (and no/low-code) friendly.
You are correct - that is not what I meant. Similar to how a native Android or iOS app behaves, I’m simply looking for mine to download/cache ALL information on the end user’s device during the initial installation so that it will open and function normally when internet connectivity is low or non-existent the next time it is opened. Updates would be obtained the next time the app is re-opened in an area with adequate internet signal.
If we are attempting (literally and figurately) to sell our apps to users by calling them “apps,” they should behave like an “app.” And yes, some folks create apps that DO require constant connectivity but there are some of us that don’t, and to have to jump through hoops to get ours to function appropriately offline shouldn’t be this difficult. Glide clearly has the ability to keep what is downloaded on the individual device in a cached and useable state, as evidenced by the functionality of the current “(partially) Offline Mode” feature. So, why can’t the session be stored indefinitely and the data can be updated every time the app is re-opened subsequently, and successfully (i.e., connected to the internet)?
If Glide truly has no plans at all to introduce this type of offline mode, please let us know so that we can stop hoping the feature will appear someday and we can take our apps, and our time, to another platform where it is already available.
If I recall, and I may be way off the mark, we were advised that migrating our apps from Classic to (new) Apps was strongly recommend because they would be fully optimized for mobile and desktop devices, maintain all the same core capabilities from the Classic Apps that we loved, and would include powerful functionality like Big Tables, Actions, and Integrations that the Classic Apps would not; additionally, we were told that if we wanted to get the most out of Glide, we should consider using Tables instead of external data sources because they could hold much more data than a Google Sheet, we could share tables between apps, and they wouldn’t cause sheet edits/sheet reloads.
Are you now saying that Glide Tables are no longer Glide’s focus? My assumption is that, because you made this statement as part of your response to my request for a true offline mode, those of us who built our app databases entirely within the Glide database structure (i.e., Tables), or migrated away from Google Sheets entirely in order to benefit from everything that is mentioned above, should no longer expect a true offline mode because Glide’s focus is on… external databases? Those of us who are all-in on Glide won’t benefit from a true offline mode because of users who aren’t? The logic here is baffling.
Exactly what @David_Gabler said:
This: CSS Trick: Inset Switch Components for Grouping
This one isn’t for me but it’s in the top-5 requested features so I wanted to make sure that my fellow Hebrews are represented 