- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2024 12:19 AM
Opening one kind of experiences from another is simple but is that recommended or not? Should there be no way to navigate from one UI experiences to another?
The difference between various interfaces is clear from horizon app frameworks. I understand that Workspace UI and Core UI are targeted for different user personas.
What about scenario where Workspace UI is slowly being adopted while Core UI still being used. For example, should the task record form have "link" or anything that would directly open some related workspace?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2024 06:31 AM
There is no hard and fast rule that says that users shouldn't span multiple app frameworks. In fact, as long as you have Next Experience "turned on" on your instance, the switch from CoreUi to a Workspace should not feel that dramatic to your users.
The key things to consider:
- Do you use different language to refer to things in the CoreUI list & forms vs. the Workspace views
- Is it obvious to the user that they are leaving the simple lists and forms and moving to a workspace?
- What are the use cases in which a user would switch between the UIs?
I would suggest considering a more aggressive move to Workspaces for the right set of users. If you provide both options to your users as part of their experience, many will default to what they are comfortable with. People generally don't like change; even when it makes them more efficient and reduces friction. There are always switching costs.
But, if you include your users in the process of making sure the workspace is easy to use (think running usability studies and incorporating their feedback) you can create champions that will encourage adoption of the better, enhanced Workspace experience.
Hope this helps!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2024 06:31 AM
There is no hard and fast rule that says that users shouldn't span multiple app frameworks. In fact, as long as you have Next Experience "turned on" on your instance, the switch from CoreUi to a Workspace should not feel that dramatic to your users.
The key things to consider:
- Do you use different language to refer to things in the CoreUI list & forms vs. the Workspace views
- Is it obvious to the user that they are leaving the simple lists and forms and moving to a workspace?
- What are the use cases in which a user would switch between the UIs?
I would suggest considering a more aggressive move to Workspaces for the right set of users. If you provide both options to your users as part of their experience, many will default to what they are comfortable with. People generally don't like change; even when it makes them more efficient and reduces friction. There are always switching costs.
But, if you include your users in the process of making sure the workspace is easy to use (think running usability studies and incorporating their feedback) you can create champions that will encourage adoption of the better, enhanced Workspace experience.
Hope this helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2024 11:14 PM
Thank you @AJ Siegel for the clarification on this. This definitely helps me on how to handle the use case. We are partner distributing our application via store. We are thinking in a way that allows the customers to make choice. However, at the same time promoting the idea that for certain role Workspace UI enables to provide more context. Let's think of task resolution, for example.
I completely agree with switching costs, and expect Workspace UI adoption to increase for relevant personas.