7 Lightning Experience UX Problems That Must Be Fixed!

I’ve been using Salesforce for seven years and running a Salesforce training institute in Nagpur. Although I’ve gotten used to Salesforce Classic, I’ve been as supportive of the new platform and user experience as possible. 

While utilizing Lightning Experience as an end user and administrator, I’ve encountered numerous disappointments despite the platform’s abundance of advantages and limitless potential.

Most of these issues, which can render Lightning Experience ineffective, are related to the overall user experience. Here are my top five Lightning Experience user experience complaints.

7 Lightning Experience User Experience Problems That Must Be Fixed!

1. Text wrapping is lacking:

Salesforce Classic’s productivity is partly due to linked lists’ ability to wrap text in fields. Field truncation would have been straightforward with up to 10 fields per linked list; however, Salesforce Classic wrapped text dependent on the size of the browser window so that, for example, the name field’s complete text is displayed. Naturally, this makes choosing a record quite simple.

There is absolutely no text wrapping in Lightning Experience. The quantity of text displayed in the record name field column decreases when more fields are added to the related list. 

Since the project isn’t wrapped, as you can see from the hover card, there isn’t any more information about its name. 

This issue is only sometimes resolved by selecting View All. My practice is to create a list view or report or click on each record individually until I find the one I want.

2. It’s Time to Spread Configuration Changes:

All Salesforce Admins using Salesforce Classic know that configuration changes may be performed instantly and are immediately implemented. 

In Lightning Experience, this is only sometimes the case. Most of the time, I had to reload a page to observe the configuration adjustments repeatedly.

Since spring 2017, it sometimes takes a while for changes to Lightning Record Pages to appear on the entire record. For instance, before taking the snapshot above, I edited the Projects-related list hover information, but it took almost 10 minutes and numerous Account record refreshes before the changes were reflected. The hover card for the list of projects related items currently looks like this.

3. Save Report Rather Than Running Report:

Reports are where Salesforce administrators spend most of their time. Most of the time, the reports we produce are never saved; they are used only once, for that particular purpose only, and are never used again. 

My use of reports includes performing audits, obtaining a total record count for an object, and other tasks.

Users cannot create these temporary reports in Lightning Experience without saving them. Therefore, I now need to remember to go back and erase the report as an admin (or even as an end user). 

The report could be saved to a “Trash” folder, which is a straightforward workaround, but this seems like an extra and pointless step.

Salesforce training centers train their students with all these things, yet these bugs must be fixed.

4. Page Loading Time for Background Records:

In my Salesforce org, I use tabs a lot. Chrome always has at least five open Salesforce windows for the organization I work with. 

I am able to open links in new tabs in Salesforce Classic, and when I go to that tab, the record page has already loaded. Super!

But even while Lightning Experience is improving, records rarely, if ever, open in the background. 

Once I click on the tab, it usually takes a few seconds for the record to load, wasting valuable time.

If you find this speed annoying, do vote or urge to fix it ASAP!

5. In the Setup, open a New Tab:

Only some of the Setup menus in Salesforce Setup have been converted to the Lightning Experience. When using Lightning Experience, the Salesforce Classic UI behaves differently from when using Classic. Many Salesforce training classes give examples of this to their students too. Here is one instance.

I want to update a few profiles while utilizing Lightning Experience. I would go to Profiles in Salesforce Classic, then open each of the profiles I wanted to change in a different Chrome tab. But if I attempt to do the same thing in Lightning Experience, the tab opens but shows nothing.

Therefore, I must either duplicate the Profiles tab for each profile that needs editing, then click into the new tabs to access the profiles, or open each profile in a separate tab, make the necessary modifications, and then return to the list of profiles.

6. Insufficient Color Contrast:

Lightning Experience has an excellent overall design as one of its strengths. It feels clean and contemporary. However, the color contrast is nearly insufficient. 

After using Lightning for a while, switching to Classic to see records feels rejuvenating to my eyes.

Although I’m not a UX designer, the fields could be more clearly identified, and the distinction between field labels and values should be clarified. After a full day of use, the text can blend for me.

Here’s another suggestion to vote up if you want more contracts in the UI’s colors.

If you are new to Salesforce or want to learn, many Salesforce training classes these days give you in-depth Salesforce training.

7. When Switching to Classic, stay on the Same Page:

The feature gap has been substantially bridged, at least in Sales Cloud, thanks to Lightning Experience. However, users may need to return to Salesforce Classic.

In my use of Lightning, for instance, some records in my production org call for manual sharing. Manual sharing, however, is not currently possible in Lightning Experience.

The page I’m now on in Lightning should be the one that loads when switching back to Salesforce Classic if I’m on a Salesforce record and decide that I need to or want to return to Salesforce Classic. Retracing navigational steps to reach the record while switching between Lighting and Classic is a productivity killer.

These are all the issues that require resolution on the UX part of the Lightning Experience. If you, too, feel any problems, you can always come up and write and ask to vote to fix it.