Understand Changes to Other Development Tools
- Describe how Lightning Experience impacts your development tools, including:
- Installed package management
- API and Apex
- Authentication and security
- Salesforce mobile development
- Salesforce Mobile SDK
This last unit is a bit of a grab bag. We’ve already covered all of the “hard” stuff, so at this point you’re in the home stretch. Can you feel it? That’s the itch you get when you’re close to a new badge. Let’s do this.
Managing your installed packages in Lightning Experience is the same as it ever was. The Installed Packages landing page is available in the Lightning Experience setup area. It looks and works the same way it does in Salesforce Classic.
Of course, finding and using this page isn’t the only thing on your mind. You’re also wondering whether your packages installed from AppExchange still work in Lightning Experience.
The best answer we can give is maybe. Apps listed on AppExchange are marked with a “Lightning Ready” sash if they’re fully compatible with Lightning Experience. Check the listing to see if an app is Lightning Ready. If it’s not, you can still try to use it in Lightning Experience, but we recommend sticking to Salesforce Classic to prevent unexpected behavior.
As a developer, one of your most important tools on any platform is the API. As a Salesforce developer, Apex is just as important to your success.
We’ve kept our promise that we won’t do anything that breaks your dependencies on our APIs. Your Apex code and queries continue to function as expected, regardless of whether you’re using Lightning Experience or Salesforce Classic. It really is just that simple. Breathe a sigh of relief.
Regardless of the user experience you’re developing for, security is still Salesforce’s top priority. Lightning Experience doesn’t fall short of our promise to keep your organization’s data safe.
Continue to treat authentication and security as you do when developing for Salesforce Classic. The only difference in access controls between Salesforce Classic and Lightning Experience is in the App Launcher. The App Launcher is available by default to all users in your organization. While this change is of concern mostly to administrators, it’s important to work with your Salesforce admin to ensure that your development work is only seen by the people who are supposed to see it.
Canvas allows you to easily integrate third party applications in Salesforce. Canvas functionality in Lightning Experience is the same as in Salesforce Classic. You can still embed Canvas apps in Visualforce pages, the Salesforce app, and everywhere else they’re supported—with the added bonus that you can integrate Canvas apps in Lightning Components!
Lightning Experience and Salesforce mobile are like peanut butter and jelly. They’re made for each other. Your mobile development practices in Lightning Experience are the same as they were in Salesforce Classic.
By now you’re probably tired of reading overview information and are ready to dive in to the nitty-gritty technical details. We won’t keep you much longer. Literally just another two sentences!
As its own client, or front end, to Salesforce the Mobile SDK isn’t impacted by Lightning Experience. If you use Mobile SDK to develop mobile apps, you can rest easy.