My app’s URL: owmml.glideapp.io
I have built a food delivery application, but face some issues that I’m not sure are bugs, a non existent feature, or my lack of knowledge on how to go about it.
I would like to be able to navigate between TABS using buttons. Link to screens connects me to a sheet, but does not navigate to an existing tab in the app.
In response to a comment on “which popular apps allow this navigation” that I saw in a similar topic, see Deliveroo, Uber Eats, Zomato, Talabat, where users click on a button to VIEW the cart, not just to add items to it. While it is possible to navigate to the cart by clicking the Cart tab, 100% of users were at a loss as to what to do after they’d added an item to the cart because they expect there to be a button that allows one to navigate to the cart. It seems to be so common a navigation pattern, it is the default navigation pattern expected by users of such apps.
This issue is not simply related to viewing the cart, it is a generic issue about using buttons as navigation tools. Another example in the same app is in creating profiles. If a user has not created a profile, then they will be unable to see their order in their cart. Ideally, as per the structure of Glide, they would navigate to “My Profile” and create a profile. A button that would navigate them to “My Profile” to do so would be the easiest solution. I thought I had a workaround with using a form button to create a profile from within the Cart that wrote into the Profile Sheet, only to realise that it a) creates a new profile whether or not there is one already, b) its visibility cannot be controlled to appear only if there is no existing profile as the parameters controlling this are in the Profile sheet not the Cart sheet (and visibility parameters don’t cut across sheets for some reason - also a seriously limiting issue in and of itself that deserves its own post). As a result the option to create a profile on the Cart sheet is available even if a profile exists, and its visibility is dependent on whether there are items in the Cart. As a result, it is a poor workaround, which could be fixed by having a distinct button that navigates to a tab in sequence so that I can guide the user experience, whilst still maintaining the tab buttons at the bottom of the screen that allow users to navigate to any tab.