There should be a Enable and Disable Button on each UX Design.
Because sometimes, some views you are working on it and are not complete , so you put on hold. rather to delete it.
or sometime, when we distribut the APP to users, we don’t want to disclose some UX to show them what is coming into new or underconstruciton.
or sometimes. when it gives an error and your app is almost ready to launch, you can put on hold the UX by pressing the button DISABLE. and go…>
1 Like
We would like to add an Action. called data into CLIPBOARD.
with Seelction of fields or CONCETENATE some fields data into CLIPBOARD.
so later use CTRL+V to paste anywhere required…
This is a must feature desperately required by all of our developers and users.
1 Like
Some quick thoughts: allow for sorting and filtering to easily define in the slice as putting into the view is not convenient.
I also have been seeking a way of having parameters in the slice so as to avoid hard coding slices.
See one of more detailed posts for further insight and direction for reusable components:
[Reusable Items and Sharing (Collaboration)](https://community.appsheet.com/t/reusable-items-and-sharing-collaboration/25668) Feature Requests
The following Feature Request is a long overdue outline I have of having Reusable Items in Appsheet. It is part of a response in part @tony request: This is just the initial outline. I will elaborate further in the future as and when I work on my Apps where it will trigger further thoughts. 1. What would be Reused and then Shared? The basic concept of reuse could be based on table which is reused (for example the Person Table with all the details of a Person like Name, Email, Phone) where …
Dear Brandon,
I am glad you are asking this question because filtering/slices/row and column selection is one of the most confusing issues I have encountered with AppSheet. Not that it is difficult in itself, but it creates unnecessary steps and makes app creation not intuitive for a true no-coder (by way of background, I created a simple time-tracking app for myself and am in the process of creating a few apps for my small business).
Let me walk you through the steps of a no-coder to filter data. Starting with Data, you are proposed to “SHOW?” certain columns in the Data>Columns: that’s the first level of selection, but it’s already counter-intuitive because shouldn’t a decision to “show” data be part of the UX menu? If you want to filter rows, you are proposed a Security Filter: nice, but is only available for PRO plan. Then you go the Views but cannot find any row filter, so you google it and learn that Security Filter was not the way to go anyway: filtering rows is actually called a Slice (?) and appears in the menu Data (even though it is the equivalent of an SQL VIEW : shouldn’t it be in UX then??). So slicing is the second level. Then you go back to your Form View and you would like to show a few limited columns, but you can’t. Oh wait, you actually can: it’s called “Column order” and that also enables to select only certain columns (not clear at all). So that’s the third level of selection. And you learn later that could also have filtered columns from the Slice itself!
Do you see how all these possibilities create confusion? I am sure coders love to have multiple options, but no-coders just want to have minimal options and an intuitive process.
I am very impressed by how robust AppSheet is: there are endless features and it seems that, no matter what you throw at it, it never crashes, and it also automatically corrects your own mistakes; that is so amazing! But I feel that, if it wants to reach out to business professionals with no IT background, the user experience should really be seamless (like the one of your competitor ? you know, the one that sounds like a parachute ?): maybe Googlers could help on that front?
Thanks for listening and keep up the great work!
PS: would it also be possible to improve the naming of several features in AppSheet? I have had to go back to the Help site multiple times to be reminded the meaning of terms such as “Label”, “Ref view”, “Dereferencing”, etc.
2 Likes