Xander Mitman - 2 years ago
Some of the reason for the "interesting" UX was due to various platform constraints at the time we shipped support for Visualforce overrides in Lightning Console in Winter '19.
Since then we've made various improvements that do open up more options - but now we have change management to consider.
I'd say three general priorities/constraints of the platform are:
a) The underlying technology should *ideally* be decoupled (or at least decouple-able) from the user experience
b) The out-of-the-box/standard UX should not change from one release to the next unless there is a VERY good reason and/or thoughtful change management process (e.g. opt-in via a CRUC)
c) Different customers have different thresholds, opinions, and productivity estimates on different UX scenarios and therefore enabling configuration by the customer is valuable.
TBD if/when/how we will tackle this idea but it has been a discussion point among various PMs here on the Lightning Platform team. Please keep the feedback coming!
Director, Product Management | Navigation Experience
Matt Rosin - 2 years ago
This is really needed for my customer. I have a custom object developed as an aura + lightning component, it is already deployed. Now I want to integrate it with the Event synchronized from Outlook, so I add a lookup to the Event object. When I click in the lookup and scroll down to the "+ New" button at the end of the lookup's picklist, it sends me to a new page! If it was a standard object lookup it would open the New input screen as a modal popup, then after creating the new object its reference would automatically be inputted in the lookup field I added to Event. This means it is not possible to deliver a streamlined work flow to the user because of a design failure. Please add it!