🧠 Question for the AppSheet Community: How do you differentiate your views by device?

[Gustavo_Eduardo]

Hey everyone 👋

I'm currently working on a modular app in AppSheet and am entering a phase of device-specific UX improvement. We know AppSheet allows us to simulate interfaces for Mobile, Tablet, and Desktop, but:

❓ How are you currently handling view differentiation based on the user's actual device?

📌 Here's what I've considered:

• CONTEXT("Host") returns "Device" or "Browser", but it doesn't tell us if it's a phone, tablet, or PC.
• There's no DEVICE_TYPE() (yet) to definitively know if we're on mobile vs. desktop.
• I'm considering naming my views with suffixes like _mob, _tab, _dsk, and using LINKTOVIEW() or dashboards to alternate the UX.

But I'm really interested in knowing:

🛠️ What strategies are you using?

🧩 How do you alternate between views based on the device?

⚖️ Do you create a single universal view, or do you duplicate views with conditional visibility?

I'm looking for real-world experiences, limitations you've faced, or clever ideas to optimize the UX for each device.

Thanks for reading 🙏

Eager to learn from your approaches!

[yasarcan · Accepted solution]

Hi

My application is used on 6 tablets and 7 computers. Since most options are common. In order not to confuse 60 employees, I chose only the tablet view.

[yasarcan · Accepted solution]

Hi

My application is used on 6 tablets and 7 computers. Since most options are common. In order not to confuse 60 employees, I chose only the tablet view.

[Gustavo_Eduardo]

I understand there's a CONTEXT("Device"), but I don't really understand the support explanation, and I don't know if anyone has used it. Anyway, I'm doing the same thing for the time being; I use the view for any case, trying not to overuse the content.

[mateo · Accepted solution]

Hey @Gustavo_Eduardo!
I am using this in some of my apps where I need different experiences based on the end device type running the app. In my opinion CONTEXT("Host") is enough but I might be wrong. My approach for this is to create different views for both browsers and devices then in my navigation actions, deep links, etc. use SWITCH() formulas to lead users to the correct views or do some validation to show views in the menu or primary bar based on the device type and other settings (RBAC for example). I also often create a table appViews (almost always read-only table) where I store information about my app's UI. It is helpful, especially for in-app-tutorials for instance, and at the same time, it becomes a kind of documentation on its own.

I'm not sure but I hope it helps.
Cheers!

[Gustavo_Eduardo]

Yes! I think that's just how it is! Thank you so much for writing.