Toggle Side Panel
Close search

Activity › Forums › Salesforce® Discussions › Why should we go for Salesforce Lightning Component?

Tagged: , , , , , ,

  • madhulika shah

    Member
    July 17, 2018 at 9:20 AM

    Hello Prachi,

    Salesforce has been promoting lightning but that doesn't mean visualforce is gone. Visualforce enables developers to build custom user interfaces with a native hosting on the Force.com platform. Visualforce enables developers to build custom user interfaces with a native hosting on the Force.com platform.

    Lightning framework aligns with Salesforce user interface strategy to empower users with highly immersive and interactive experience but involves a steep learning curve in comparison to Visualforce. Since application building is an inherent part of Lightning, it is considered a bit more complex than Visualforce.

    Both the frameworks encompass some pros and cons associated with them. If you are developing for a Salesforce1 mobile app, you should prefer Lightning framework and if you want to create a page-centric experience with limited client-side logic, you must opt Visualforce framework.

  • [adinserter block='9']

  • Avnish Yadav

    Member
    September 10, 2018 at 6:41 AM

    Hi Prachi,

    Lightning components give us a client-server framework that accelerates development, as well as app performance, and is ideal for use with the Salesforce mobile app and Salesforce Lightning Experience.

    Thanks.

  • Parul

    Member
    September 10, 2018 at 6:49 AM

    Hi Prachi,

    Visualforce and Lightning both offer ways to design and create custom interfaces for Salesforce.

    Visualforce was designed to follow a Page-Centric model. This means that the intent of Visualforce was to create something that was your full page interface with Salesforce. When the user needed to perform some kind of operation, like Save a record, it would send that request to the Salesforce servers and then reload the entire page with the new state of the UI. All backend processing is done with Apex Code on the Server-Side. You have the option to inject JavaScript into the mix to handle some of the Client-Side processing, but it isn't the default interaction methodology.

    Lightning was designed to follow an App-Centric model. This essentially means that it has been designed to create self-contained components that build on top of each other.

    "To put this in perspective, with Visualforce you would send an interaction to the Salesforce server and then update the entire page". However, with Lightning, you can send an interaction to the Salesforce servers and then update a specific component.

    This has huge implications for performance and for the fluid motion of a UI.

    This allows us to design UIs that are inherently responsive to the user interactions, meaning we update the things the user is interacting with and everything else remains untouched.

     

    Thanks.

  • shariq

    Member
    September 15, 2018 at 10:48 AM

    Hi,

    The Lightning Component framework is a UI framework for developing dynamic web apps for mobile and desktop devices. The framework supports partitioned, multi-tier component development that bridges the client and server. It uses JavaScript on the client side and Apex on the server side.

    The benefits include an out-of-the-box set of components, event-driven architecture, and a framework optimized for performance.
    Out-of-the-Box Component Set
    Comes with an out-of-the-box set of components to kick start building apps. You don't have to spend your time optimizing your apps for different devices as the components take care of that for you.
    Rich component ecosystem
    Create business-ready components and make them available in the Salesforce app, Lightning Experience, and Communities. Salesforce app users access your components via the navigation menu. Customize Lightning Experience or Communities using drag-and-drop components on a Lightning Page in the Lightning App Builder or using Community Builder. Additional components are available for your org in the AppExchange. Similarly, you can publish your components and share them with other users.
    Performance
    Uses a stateful client and stateless server architecture that relies on JavaScript on the client side to manage UI component metadata and application data. The client calls the server only when absolutely necessary; for example to get more metadata or data. The server only sends data that is needed by the user to maximize efficiency. The framework uses JSON to exchange data between the server and the client. It intelligently utilizes your server, browser, devices, and network so you can focus on the logic and interactions of your apps.
    Event-driven architecture
    Uses an event-driven architecture for better decoupling between components. Any component can subscribe to an application event, or to a component event they can see.
    Faster development
    Empowers teams to work faster with out-of-the-box components that function seamlessly with desktop and mobile devices. Building an app with components facilitates parallel design, improving overall development efficiency.
    Components are encapsulated and their internals stay private, while their public shape is visible to consumers of the component. This strong separation gives component authors freedom to change the internal implementation details and insulates component consumers from those changes.
    Device-aware and cross browser compatibility
    Apps use responsive design and provide an enjoyable user experience. The Lightning Component framework supports the latest in browser technology such as HTML5, CSS3, and touch events.

    Hope this helps.

Log In to reply.

Popular Salesforce Blogs
Skip to toolbar