Currently, it appears that the "Highlight color" field only accepts static color values (either from the palette or as hexadecimal codes). This limitation prevents users from dynamically setting highlight colors based on data values stored in columns. Problem: This restriction necessitates the creation of multiple Format Rules to achieve dynamic color changes, which can become cumbersome and difficult to manage, especially when dealing with a large number of conditions. Requested Feature: We would greatly benefit from the ability to set the "Highlight color" dynamically using column values. Specifically, we request that the "Highlight color" field be enhanced to: Accept Column References: Allow us to enter a column name (e.g., [ColorColumn]) that contains valid hexadecimal color codes. Evaluate Expressions: Allow us to use expressions (e.g., IFS() or SWITCH()) that return hexadecimal color codes. Example Use Case: As an example, we would like to be able to set the highlight color of map pins based on the value of a "ProgramDay" column, using a virtual column to determine the color. Currently we have to create a format rule for every program day, and set the color statically. this is very hard to maintain. Benefits: Increased Flexibility: This enhancement would significantly increase the flexibility of Format Rules, allowing for more dynamic and data-driven styling. Simplified Management: It would reduce the number of Format Rules required for dynamic color changes, simplifying app maintenance. Improved User Experience: It would create a more intuitive and efficient experience for developers. We believe that this feature would be a valuable addition to AppSheet and would greatly improve the app development process. Thank you for your consideration. ... View more

🎯 Conditional Expressions for "Finish View" Navigation Currently, the Finish View option in AppSheet only allows you to select a static view. But what if we could take this one step further? @amyplin  ✨ Imagine if we could define the "Finish View" using an expression! This would allow developers to dynamically redirect users to different views based on their role, email, or other user-specific logic. 💡 Why This Matters When a user logs into your AppSheet app, they don’t just log in with their email—they log in with their permissions and role. So why not use that to personalize their experience? With conditional navigation in Finish View, we could: ✅ Provide a more polished, role-based onboarding experience ✅ Automatically route users to the most relevant dashboard 🔧 What This Could Look Like   IF( AND( IN( USEREMAIL(), users[id] ), LOOKUP( USEREMAIL(), "users", "id", "user_role" ) = "ADMIN" ), "admin_dashboard", "user_home" ) ☝️ This would allow the form to finish and take the user to different views depending on their role. 🌟 Benefits 🔄 Dynamic navigation based on user data 🧼 Cleaner UX with fewer unnecessary steps or views ⚡ Faster app logic, as no bots or actions are needed to redirect If this idea would make your app better too, please drop a 👍 or a +1 so the AppSheet team knows it matters! Let’s build smarter, more intuitive user journeys together. 🚀 ... View more

AppSheet does not support group view in Menu, so if you have many views that need to be shown in Menu view, it isn't very clear for the user. I suggest that the team dev should consider this feature asap for user to be able to customize their menu flexibly as in the picture below: Grouping views on the menu ... View more

Dear AppSheet Team, @amyplin  Today, I would like to request the separation of the display name of an action from the confirmation message value. There are times when it is necessary to set a display name like "Generate Nutritional Info", but for the confirmation message, a simple "Yes" would be sufficient. That’s all for today. Best regards!     ... View more

As we know in dashboard view, we can add multiple individual views. However the user can move and resize each and every individual view within a dashboard. Also on opening the dashboard , the views may not exactly render in the intended position, order and size in the dashboard view. Will request AppSheet development team to introduce grouping of the selected individual views in the editor as desired by the app creator,  so that those always render in the same relative position and size and together. This will enable more creative ways of grouping and thereby using individual views within a dashboard. The example below shows grouping option in Google slides as an example.   ... View more

I would like to have an option in AppSheet to color entire rows in views (such as table or detail views) based on Format Rules. This feature would enhance the visual appeal and clarity of apps, especially for status tracking, priority settings, or highlighting important information. ... View more

Calendars are a terrific perspective (view) to visualize data (rows in a table) when time (which is literally the only unit of measure agreed upon by every locale in the world) is involved  We can easily see overlaps or conflicts, we can visualize different tracks/types of scheduled events, etc. Being able to direct users to a focus time period is a critical need. Slices can be created to only show events meeting a day/date criteria, however, a calendar view is forcing to start with today which often has zero relevance in event planning. Please provide us more granularity in how we can configure this view, such as: Initial Value = Expression (forcing this type to Date makes sense with this specific view type) Customizable range = Expression (currently labeled as Default View where we choose Month/Week/Day) - let users define an expression to describe these subview definitions and how they are ordered (ie, 5 day weeks (weekdays only), week, months where Monday is the far left column, even says 4 days "weeks" (long weekends, etc) Confined data/time range = Toggle (directly next to View Options pulldown/selections) use the slice's data to determine what range of days/dates should be visible in the view (ie, remove the backward/forward advance buttons if data does not exist beyond the current range). if the slice literally is confined to a single day then users should not be able to advance  I have included a mock-up to help in visualizing said suggestions   ... View more

RE: the following issue: https://www.googlecloudcommunity.com/gc/AppSheet-Q-A/Unfortunate-Side-Effect-for-Desktop-UX-Dashboard-FAB/m-p/839989#M257970 ======================================================================================== Since the addition of the new desktop UX, and having buttons in the Primary position moving themselves to the header bar of a view: it would really help us with the customization of the UX if we were to split "Primary" into two options: FAB Header Having this granular control would really be helpful.  There are plenty of times when I would want the button to be in the header, but also times when it would be helpful to have it float - so it's right in everyone's face. Having these two separate options would really allow me to have fine grain control over certain buttons. -------------------------------------------------------------------------------------------------------------------- Cheers; and as always, thanks for considering!   ... View more

Dear AppSheet Team, I need to request you to please split the option: Settings > Theme & Brands > Hide menu and search buttons It would be ideal if they were two separate buttons (I may need the menu button but not the search button). Thanks for reading ... View more

DISCLAIMER: This feature idea is not related to creating lists, enums, or any other field inside an App and sorting that data in the list given those work as expected. This idea pertains specifically to the built-in search filter users see in the App when trying to filter [rows/lists of data in a table or view.] REQUEST: When using the built-in search filter capability, the list of options should be sorted alphabetically (or at least allow the user to do so). Such sorting should be the default behavior for any search filter list. EXAMPLE/USE CASE: In the thread referenced below, you will see the following example where the search filter shows the options to filter by, but they're not sorted alphabetically. An unsorted list is a poor user experience given it either forces the user to scroll through the entire list to search for a value that should've shown up earlier in the list or somehow know the value ahead of time and type it in. Additional context for this idea: https://www.googlecloudcommunity.com/gc/AppSheet-Q-A/Search-Filter-List-not-Alphabetically-Ordered/m-p/596309 FYI @Suvrutt_Gurjar,  @LLD,  @RowanAngstadt  ... View more

Hi folks, i would really like to have a settings which controls, if the "Menu" in the Desktop view has the View Names displayed by default, or not. Right now, the users only the the Icons. A lot users came back to me, that they like it more, if they also see the view Name instead just the Icon.  Me as a app developer, would also be happy to control it.    ... View more

hi 🔹 Problem Description In AppSheet, users often create slices for filtered data views. These slices can be used in multiple views, but there is currently no simple way to see which views are linked to a specific slice. 🔹 Current Challenges: If a slice is used in multiple views, users must manually check all views to find where it is applied. This becomes a problem in large applications with many views and slices. Accidental deletion or modification of a slice can affect multiple views, and the user will not be aware of it in advance. Proposed Solution Add an automatic list of views that use a slice directly in the slice settings. How it should work: When opening a slice in the editor, a list of associated views appears. Even a simple text list would help users quickly navigate. Ideally, make the views clickable so users can jump directly to their settings. 🔹 Expected Benefits Faster view management. No need to manually search where a slice is used. Fewer mistakes. Users will be aware of all views affected when modifying or deleting a slice. Better application organization. Easier maintenance of complex projects, especially for teams. How it could look: When opening a slice in the editor, a new section called "Used in Views" would automatically display all views that reference the slice. 🔹 Example: Used in Views: ✔ Order_Detail_View ✔ Order_List_View ✔ Dashboard_View (Ideally, these should be clickable links to view settings) ... View more

Hi Team,  Many Nocode Platforms such as PowerApps, AirtTable, LarkSuite, and Glide have been updated with a handy feature that accepts add Multi-Image Picker and Multi-File Upload and can show multiple images in a column but Appsheet hasn't yet. Picker to add multiple pictures or Files to App Now our users have to add each picture to each column or add each picture to each row, I think it is very inconvenient.  Please consider updating this feature asap. Thanks a lot, Hien Nguyen ... View more

That would be great for the UX if we could choose the color or the header in a table view Do you think it is possible?     ... View more

Hello Appsheet team, that would be amazing if we could group the views into sections in the side menu bar, just like the image below: The same thing already occurs in the desktop mode when we group multiple views. One arrow is added and a sorta dropdown is shown. I picture this as a kinda "MENU DASHBOARD" view where we add the views we want and it group them inside this view. It would only work in the side menu for both mobile and desktop devices. I'm sure that this wouldn't be the hardest thing to implement among the ones we have begged for. You can do it. What do you think about it? @lizlynch @Arthur_Rallu @MultiTech @benhare  ... View more

How great it would be if AppSheet enabled a 'Tooltip' property where you could enter text or an expression that returns a message for the user hovering over a specific area. Friends, regardless of those who write to me saying that 'AppSheet does absolutely nothing to satisfy its users in this section and, although I might also think it seems that way,' this post assumes that’s not the case. I imagine that at some point, this project will be picked up again, and I’d like to think it’s currently on hold because Google has other priorities. I use this section as a log of the ideas that come to mind as I develop with AppSheet. After all, I’m confident that this idea bank will be the first place AppSheet looks when they decide to revisit this promising and young project. Best regards! ... View more

I've been weighing the pros and cons of creating virtual columns with formulas that I then reference in showIf, validIf, and other properties. I've noticed that creating a virtual column as a reusable programming object is very helpful in terms of maintenance and tracking significant changes between saves. By changing the formula in the virtual column, the calculation is modified wherever it's used without having to manually update each instance. However, as the number of virtual columns increases, the calculation for each sync becomes enormous, which can become tedious from a user experience standpoint, especially when there's a lot of data to load (though this might not be as big of an issue for personal apps). To find a middle ground, I came up with the idea of a column type that's neither virtual nor real (an object column). Imagine it like working in Excel, where you create a formula and then reference it instead of typing it out multiple times. Having reusable objects would be great for maintaining our apps without impacting sync performance. How do I think this could be implemented? I imagine that, instead of writing a formula in the ShowIf, ValidIf, etc., field, we could reference the formulas contained in other fields within their properties. For example, let's imagine a case where Column 1 has a ShowIf, and Column 2 has another ShowIf that depends on the first one. Instead of duplicating the formula, we could create an AND() with the ShowIf from the first one without needing to rewrite the formula, simply by referencing the first one's ShowIf. That way, we would have a precomputed expression instead of two separate calculations. This would apply to everything. For example the next expression: AND(          showif.column1,          expression       ) Or like we have a "user settings" we could have an "objects settings" that would allow us to configure system columns that we can access.   ... View more

It would be awesome if we could have a way to jump to the current location in a map view. Like we can do in google maps.  In this post I explained a workaround how to build an action that can do this. But this is not very intuitive. ... View more

Accordion Effect for Grouped Rows It would be nice to have an accordion effect on rows grouped by specific criteria, as it would save the user from having to scroll. ... View more