It was my privilege to attend Salesforce’s Lightning Now tour in London, with colleagues and friends. It was a fantastically productive couple of days and we learnt lots about how easy it is to switch to Lightning Experience, even in spite of having lots of incumbent Visualforce and code to update in order to make the switch.
I couldn’t disagree more. As a consultant, I’ve been seeing a fair amount of resistance to lightning – not just on the side of the installed customer base, but amongst colleagues and friends who also work with Salesforce in a customer-facing role. They have their reasons for not wanting to make the switch; when Lightning Experience was first released, I switched for the first time in 2015 – and, to my horror, felt the last 7 years of my career and knowledge draining away from me! It was very different when it was first released; the tabs were now on the left – but it’s possible that Salesforce made the decision to reel the UI back in somewhat in order to phase the feature releases and focus on building adoption. My company was an ISV, and our products weren’t ready for Lightning yet, so I had no real reason to learn it for a while after that. Now, there is no reason to be afraid. It is so easy to learn; jump in with both feet, try configuring only in Lightning for a bit, then see how you feel about it!
This year I changed jobs and decided to have a look at this thing in earnest. While my husband was working through his Trailhead badges, I decided to focus on the one thing I knew would become more important over the coming years, but that I had the least knowledge on, so I tackled some trailhead tasks of my own, which you can find in my Switchover trailmix, if you’re interested. It was worth it. I found configuring Salesforce soo much faster – getting to objects, fields, page layouts was far easier in the Setup area – but more importantly, I could now build some really snazzy pages to make my customers oooh and ahh about. I was getting a bit excited about the possibilities myself.
Lightning is a reimagined experience; it’s not Classic with a new skin. It works on a completely different framework, driven by metadata. Salesforce took a bunch of UX guys, kicked the Product Managers out, locked them in a building together and asked them to redesign the user interface from scratch, with user productivity, efficiency and activity at the forefront of the design. The result was a new, component-based framework, incorporating standard, custom and AppExchange components that everyone can make. A far greater opportunity to be creative and make your Salesforce org your own.
Developers shout the loudest about sticking with Classic, but it’s developers who stand to gain the most from the switchover. I spent the last few days in a workshop, taking existing Visualforce pages and re-skinning them using <slds /> and the Lightning Design System; if I can do it with no development experience at all, I am certain you can too!
Coding is slightly different for Lightning components, and I can’t profess to offer anything particularly useful in terms of technical trade-offs here, but I’d definitely recommend this project, to show you how simple it is.
It takes a change in mindset to make the switch – possibly some political battles with others who need convincing, but the fact is, Lightning Experience is not going away. In my view, it is far better to face it now, put the time in to learn more and reduce future technical debt. I’ll be recommending Lightning Experience for all new implementations and I look forward to hearing more stories about how switchover projects have progressed over the coming years.
When I was diagnosed with Stage 4 in 2021, writing a memoir came to the…
From my point of view I'm acutely aware that I didn't update my readers on…
Service Cloud - KCS & Chatbots Click the buttons below to find the Trailhead modules…
Click the buttons below to find the Trailhead modules we did and follow along with…
Click the buttons below to find the Trailhead modules we did and follow along with…
Click the buttons below to find the Trailhead modules we did and follow along with…