The #1 toolkit to accelerate custom Salesforce app design, development, and adoption.

We break down some commonly asked questions around Skuid + Salesforce Lightening

Your top 5 FAQs on Skuid + Salesforce Lightning.

This blog was originally published on 5/31/2018 and has been updated.

Skuid is the fastest way to build, migrate, and customize apps in Lightning. Together, you can easily pull in multiple data sources, develop and maintain custom interfaces up to 90% faster.

Because Skuid and Lightning deliver such significant value, we get a lot of questions on how they work together. We’ve answered your top five FAQs on Skuid and Salesforce Lightning to help guide how you think about this winning combination. For a really deep dive into Skuid and Lightning, explore our robust Skuid and Lightning documentation here.

1. What is Salesforce Lightning? How is Skuid different from Salesforce Lightning?

Salesforce Lightning is an umbrella term, essentially re-branding the Salesforce ecosystem/platform. Think of it as Salesforce 2.0.

Lightning includes:

  • the new Salesforce Lightning Design System (think: Style Guide) and
  • the Salesforce Lightning App Builder (LAB)
  • Lightning Component Framework (Aura)
  • Lightning Exchange (The AppExchange with Lightning Components)

Skuid is fundamentally different from the Salesforce Lightning platform because Skuid doesn’t store any data. The Skuid platform strictly interacts with and extends the presentation user interface (UI) and user experience (UX) layers of Salesforce.

2. What are the advantages of moving to Lightning?

According to Salesforce documentation, Lightning is a good fit for your Salesforce org if you’re:

  • Wanting a turnkey solution for Salesforce Sales Cloud—Accounts, Contacts, Leads, Opportunities, and Custom Objects.
  • Already considering an entire reboot of your Salesforce implementation

In addition to these benefits, using Lightning in conjunction with Skuid can dramatically enhance your UX. You can have a mixture of Lightning components and Skuid components (all brought together within the Lightning App Builder) throughout your org. You can also incorporate entire Skuid pages inside of Lightning pages, allowing you to use the power of Skuid’s multi-object, component-based goodness alongside the awesome new tools that come with Lightning Experience.

Learn how we can help your organization switch to Salesforce Lightning >>

3. What is the difference between Lightning components and Skuid components?

As of May 2018, there are 3 categories of standard Lightning Page templates. Depending on which template you start with, you’ll have a different number of standard lightning components available to drag and drop onto the Lightning App Canvas.

  1. Home Page (22 components)
  2. App Page (11 components)
  3. Record Page (22 components)

While these components provide great functionality out-of-the-box, rendering these components or adding new ones to match your business processes can still take a lot of code.

Skuid works like a Lightning component factory, so you don’t have to write code to make Lightning components match your business processes exactly. Many components that you’d have to write code to use in Lightning are already available out-of-the-box and declarative in Skuid. Additionally, components deployed in Skuid do not require maintenance like those built with code. All this means that you can build and maintain apps simply, quickly, and cost-effectively.

4. Where can Skuid be added in a Lightning-enabled org?

You can add Skuid in a Lightning-enabled org in a few places:

  • As a Skuid Page Component for a Lightning Page
  • Inside Lightning Global Actions
  • Inside Quick Actions
  • Inside the Utility bar.

5. How can I move to Lightning with Skuid?

With Skuid’s Migration Services, you can accelerate your move to Lightning. Transform your Salesforce Classic customizations to native Lightning 90% faster than rewriting with code.

If you are an existing Skuid customer, seamlessly move your Skuid pages from Salesforce Classic to Lightning, without losing the amazing user experiences you’ve already crafted with Skuid.

If you’re an existing Salesforce Classic customer, moving to Lightning with Skuid is blazing fast. First, you’ll recreate your Salesforce Classic apps in Skuid through the ease of drag-and-drop. Then, you’ll migrate your Skuid apps to Lightning.

6. Okay, one more question…

How do you get started moving to Lightning with Skuid? Reach out to our Professional Services team to learn more.

Learn more

Content Marketing Manager

By day, I strategize, create, and promote compelling content. By night, I read books and devour chocolate.