have Lightning Web Components retrocompatibility?











up vote
7
down vote

favorite
1












I've just read here that Salesforce decide to change the framework use for Lightning Component. In according with this article seem very powerful under some aspects. In your opinion, the actual Lightning Component (aura) will work in the future? I've an entire org developer with the actual lightning components and I'm a bit afraid of it.










share|improve this question




























    up vote
    7
    down vote

    favorite
    1












    I've just read here that Salesforce decide to change the framework use for Lightning Component. In according with this article seem very powerful under some aspects. In your opinion, the actual Lightning Component (aura) will work in the future? I've an entire org developer with the actual lightning components and I'm a bit afraid of it.










    share|improve this question


























      up vote
      7
      down vote

      favorite
      1









      up vote
      7
      down vote

      favorite
      1






      1





      I've just read here that Salesforce decide to change the framework use for Lightning Component. In according with this article seem very powerful under some aspects. In your opinion, the actual Lightning Component (aura) will work in the future? I've an entire org developer with the actual lightning components and I'm a bit afraid of it.










      share|improve this question















      I've just read here that Salesforce decide to change the framework use for Lightning Component. In according with this article seem very powerful under some aspects. In your opinion, the actual Lightning Component (aura) will work in the future? I've an entire org developer with the actual lightning components and I'm a bit afraid of it.







      lightning-components aura lwc lightning-web-components






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 12 hours ago









      Daniel Ballinger

      71.7k15146384




      71.7k15146384










      asked 14 hours ago









      DarkSkull

      5211922




      5211922






















          3 Answers
          3






          active

          oldest

          votes

















          up vote
          9
          down vote













          Having played a little with lightning web component during pilot , I think yes sooner or later everyone will be using lightning web component framework to build their apps.To begin with currently what i know is it lacks support for communities or flows and many other areas (Official docs are yet to be released so we will come more when docs go out on 17th Dec).However eventually (may be an year from now ) I think Salesforce will make every attempt to add the support lwc everywhere with time.



          Why I think LWC is future?




          1. Excellent ES6 and beyond Javascript support .


          2. Faster rendering performance .


          3. Consistent with the webcomponent framework specifications from w3 (https://www.w3.org/standards/techs/components#w3c_all)


          4. Excellent tooling support .(Salesforce built great tooling utility - https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-lwc)


          5. The syntax and semantics looks to be very clear and adheres to the current webcomponents standards .



          Current State Of Aura




          1. Still supported by salesforce and going to be supported

          2. Salesforce looks to have great documentation (available in spring 19 orgs) on how to use aura with lightning web components as well how to migrate your existing aura components to lightning web components .


          I am sure salesforce will support aura for long time as it will take few more years for them to replace everything under the hood(Safe harbor and not that I don't work for salesforce so do not buy in).




          I think you should support your aura components and keep enhancing
          them however start the learning path by playing with docs. Since the
          product will be GA in new year , if you have a new component coming up
          surely look to build using the LWC.




          For existing components take opportunity to ask few questions




          1. Should I redesign with better UX as a part of lwc migration ?

          2. What were some of the bottlenecks you encountered when building with aura . Does the new framework fill them ?

          3. What your end users want from the components you have .Your release backlog .If you think lwc will full fill some of these requirements at a greater velocity then I would say just go for it knowing its going to GA so you know you will have access to support on this .






          share|improve this answer























          • please feel free to revert changes if you think they're not needed. Thanks!
            – codeyinthecloud
            14 hours ago










          • "If you are new to developing on Lightning or if you are starting a new project, we recommend using the Lightning Web Components programming model." in my opinion Salesforce it is encouraging to switch to the new model
            – Enrico Murru
            14 hours ago










          • Fact that it straight went to GA from pilot makes me feel it's time to start using lwc .And Salesforce has been using this internally so that gives some level of confidence to me to start working with it
            – Mohith Shrivastava
            14 hours ago


















          up vote
          4
          down vote













          Yes, Aura components will work with LWC. In fact, Salesforce has already internally been using LWC for a year now! All those standard components you've used, like lightning:button, are actually LWC components, and you didn't even notice. Aura will be used for the foreseeable future, as it is still the core base of Lightning Components; it's only the higher-level components that we use every day are written in LWC. An underlying framework is still required. What LWC means is that your components will (eventually) be portable to other platforms, like React, with little or no modification, unlike Aura, which is inherently not compatible with other platforms. The most relevant text is actually from that post itself:




          If you are already developing Lightning components with the Aura programming model, you can continue to do so. Your Aura components will continue to work as before. You can build new components with Aura or Lightning Web Components. Your Aura and Lightning Web Components can coexist and interoperate. Over time, you can consider migrating your Aura Components to Lightning Web Components, starting with the components that would benefit the most from the performance benefits of Lightning Web Components.




          You can keep using Aura, or you can use LWC, or you can mix-and-match. LWC has better performance characteristics, so you should consider learning and leveraging LWC, but you'll be able to use Aura until such time that you decide to move to LWC.






          share|improve this answer




























            up vote
            3
            down vote













            To add on top of @sfdcfox. You got your answer in the blog itself.



            Coexistence and interoperability:



            With the addition of Lightning Web Components, there are now two ways(but not the only way!) to build Lightning components:




            • Aura Components, leveraging its own component model, templates, and modular development programming model.

            • Lightning Web Components, built on top of the web standards breakthroughs of the last five years: web components, custom elements, Shadow DOM, etc.


            If you are already developing Lightning components with the Aura programming model, you can continue to do so. Your Aura components will continue to work as before. You can build new components with Aura or Lightning Web Components. Your Aura and Lightning Web Components can coexist and interoperate. Over time, you can consider migrating your Aura Components to Lightning Web Components, starting with the components that would benefit the most from the performance benefits of Lightning Web Components.




            Basically you can use the base components and framework specific
            components as if today, but you can migrate if you want to take
            benefit of those of lightning web components







            share|improve this answer





















              Your Answer








              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "459"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              convertImagesToLinks: false,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f242490%2fhave-lightning-web-components-retrocompatibility%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              9
              down vote













              Having played a little with lightning web component during pilot , I think yes sooner or later everyone will be using lightning web component framework to build their apps.To begin with currently what i know is it lacks support for communities or flows and many other areas (Official docs are yet to be released so we will come more when docs go out on 17th Dec).However eventually (may be an year from now ) I think Salesforce will make every attempt to add the support lwc everywhere with time.



              Why I think LWC is future?




              1. Excellent ES6 and beyond Javascript support .


              2. Faster rendering performance .


              3. Consistent with the webcomponent framework specifications from w3 (https://www.w3.org/standards/techs/components#w3c_all)


              4. Excellent tooling support .(Salesforce built great tooling utility - https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-lwc)


              5. The syntax and semantics looks to be very clear and adheres to the current webcomponents standards .



              Current State Of Aura




              1. Still supported by salesforce and going to be supported

              2. Salesforce looks to have great documentation (available in spring 19 orgs) on how to use aura with lightning web components as well how to migrate your existing aura components to lightning web components .


              I am sure salesforce will support aura for long time as it will take few more years for them to replace everything under the hood(Safe harbor and not that I don't work for salesforce so do not buy in).




              I think you should support your aura components and keep enhancing
              them however start the learning path by playing with docs. Since the
              product will be GA in new year , if you have a new component coming up
              surely look to build using the LWC.




              For existing components take opportunity to ask few questions




              1. Should I redesign with better UX as a part of lwc migration ?

              2. What were some of the bottlenecks you encountered when building with aura . Does the new framework fill them ?

              3. What your end users want from the components you have .Your release backlog .If you think lwc will full fill some of these requirements at a greater velocity then I would say just go for it knowing its going to GA so you know you will have access to support on this .






              share|improve this answer























              • please feel free to revert changes if you think they're not needed. Thanks!
                – codeyinthecloud
                14 hours ago










              • "If you are new to developing on Lightning or if you are starting a new project, we recommend using the Lightning Web Components programming model." in my opinion Salesforce it is encouraging to switch to the new model
                – Enrico Murru
                14 hours ago










              • Fact that it straight went to GA from pilot makes me feel it's time to start using lwc .And Salesforce has been using this internally so that gives some level of confidence to me to start working with it
                – Mohith Shrivastava
                14 hours ago















              up vote
              9
              down vote













              Having played a little with lightning web component during pilot , I think yes sooner or later everyone will be using lightning web component framework to build their apps.To begin with currently what i know is it lacks support for communities or flows and many other areas (Official docs are yet to be released so we will come more when docs go out on 17th Dec).However eventually (may be an year from now ) I think Salesforce will make every attempt to add the support lwc everywhere with time.



              Why I think LWC is future?




              1. Excellent ES6 and beyond Javascript support .


              2. Faster rendering performance .


              3. Consistent with the webcomponent framework specifications from w3 (https://www.w3.org/standards/techs/components#w3c_all)


              4. Excellent tooling support .(Salesforce built great tooling utility - https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-lwc)


              5. The syntax and semantics looks to be very clear and adheres to the current webcomponents standards .



              Current State Of Aura




              1. Still supported by salesforce and going to be supported

              2. Salesforce looks to have great documentation (available in spring 19 orgs) on how to use aura with lightning web components as well how to migrate your existing aura components to lightning web components .


              I am sure salesforce will support aura for long time as it will take few more years for them to replace everything under the hood(Safe harbor and not that I don't work for salesforce so do not buy in).




              I think you should support your aura components and keep enhancing
              them however start the learning path by playing with docs. Since the
              product will be GA in new year , if you have a new component coming up
              surely look to build using the LWC.




              For existing components take opportunity to ask few questions




              1. Should I redesign with better UX as a part of lwc migration ?

              2. What were some of the bottlenecks you encountered when building with aura . Does the new framework fill them ?

              3. What your end users want from the components you have .Your release backlog .If you think lwc will full fill some of these requirements at a greater velocity then I would say just go for it knowing its going to GA so you know you will have access to support on this .






              share|improve this answer























              • please feel free to revert changes if you think they're not needed. Thanks!
                – codeyinthecloud
                14 hours ago










              • "If you are new to developing on Lightning or if you are starting a new project, we recommend using the Lightning Web Components programming model." in my opinion Salesforce it is encouraging to switch to the new model
                – Enrico Murru
                14 hours ago










              • Fact that it straight went to GA from pilot makes me feel it's time to start using lwc .And Salesforce has been using this internally so that gives some level of confidence to me to start working with it
                – Mohith Shrivastava
                14 hours ago













              up vote
              9
              down vote










              up vote
              9
              down vote









              Having played a little with lightning web component during pilot , I think yes sooner or later everyone will be using lightning web component framework to build their apps.To begin with currently what i know is it lacks support for communities or flows and many other areas (Official docs are yet to be released so we will come more when docs go out on 17th Dec).However eventually (may be an year from now ) I think Salesforce will make every attempt to add the support lwc everywhere with time.



              Why I think LWC is future?




              1. Excellent ES6 and beyond Javascript support .


              2. Faster rendering performance .


              3. Consistent with the webcomponent framework specifications from w3 (https://www.w3.org/standards/techs/components#w3c_all)


              4. Excellent tooling support .(Salesforce built great tooling utility - https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-lwc)


              5. The syntax and semantics looks to be very clear and adheres to the current webcomponents standards .



              Current State Of Aura




              1. Still supported by salesforce and going to be supported

              2. Salesforce looks to have great documentation (available in spring 19 orgs) on how to use aura with lightning web components as well how to migrate your existing aura components to lightning web components .


              I am sure salesforce will support aura for long time as it will take few more years for them to replace everything under the hood(Safe harbor and not that I don't work for salesforce so do not buy in).




              I think you should support your aura components and keep enhancing
              them however start the learning path by playing with docs. Since the
              product will be GA in new year , if you have a new component coming up
              surely look to build using the LWC.




              For existing components take opportunity to ask few questions




              1. Should I redesign with better UX as a part of lwc migration ?

              2. What were some of the bottlenecks you encountered when building with aura . Does the new framework fill them ?

              3. What your end users want from the components you have .Your release backlog .If you think lwc will full fill some of these requirements at a greater velocity then I would say just go for it knowing its going to GA so you know you will have access to support on this .






              share|improve this answer














              Having played a little with lightning web component during pilot , I think yes sooner or later everyone will be using lightning web component framework to build their apps.To begin with currently what i know is it lacks support for communities or flows and many other areas (Official docs are yet to be released so we will come more when docs go out on 17th Dec).However eventually (may be an year from now ) I think Salesforce will make every attempt to add the support lwc everywhere with time.



              Why I think LWC is future?




              1. Excellent ES6 and beyond Javascript support .


              2. Faster rendering performance .


              3. Consistent with the webcomponent framework specifications from w3 (https://www.w3.org/standards/techs/components#w3c_all)


              4. Excellent tooling support .(Salesforce built great tooling utility - https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-lwc)


              5. The syntax and semantics looks to be very clear and adheres to the current webcomponents standards .



              Current State Of Aura




              1. Still supported by salesforce and going to be supported

              2. Salesforce looks to have great documentation (available in spring 19 orgs) on how to use aura with lightning web components as well how to migrate your existing aura components to lightning web components .


              I am sure salesforce will support aura for long time as it will take few more years for them to replace everything under the hood(Safe harbor and not that I don't work for salesforce so do not buy in).




              I think you should support your aura components and keep enhancing
              them however start the learning path by playing with docs. Since the
              product will be GA in new year , if you have a new component coming up
              surely look to build using the LWC.




              For existing components take opportunity to ask few questions




              1. Should I redesign with better UX as a part of lwc migration ?

              2. What were some of the bottlenecks you encountered when building with aura . Does the new framework fill them ?

              3. What your end users want from the components you have .Your release backlog .If you think lwc will full fill some of these requirements at a greater velocity then I would say just go for it knowing its going to GA so you know you will have access to support on this .







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited 14 hours ago

























              answered 14 hours ago









              Mohith Shrivastava

              59.2k795135




              59.2k795135












              • please feel free to revert changes if you think they're not needed. Thanks!
                – codeyinthecloud
                14 hours ago










              • "If you are new to developing on Lightning or if you are starting a new project, we recommend using the Lightning Web Components programming model." in my opinion Salesforce it is encouraging to switch to the new model
                – Enrico Murru
                14 hours ago










              • Fact that it straight went to GA from pilot makes me feel it's time to start using lwc .And Salesforce has been using this internally so that gives some level of confidence to me to start working with it
                – Mohith Shrivastava
                14 hours ago


















              • please feel free to revert changes if you think they're not needed. Thanks!
                – codeyinthecloud
                14 hours ago










              • "If you are new to developing on Lightning or if you are starting a new project, we recommend using the Lightning Web Components programming model." in my opinion Salesforce it is encouraging to switch to the new model
                – Enrico Murru
                14 hours ago










              • Fact that it straight went to GA from pilot makes me feel it's time to start using lwc .And Salesforce has been using this internally so that gives some level of confidence to me to start working with it
                – Mohith Shrivastava
                14 hours ago
















              please feel free to revert changes if you think they're not needed. Thanks!
              – codeyinthecloud
              14 hours ago




              please feel free to revert changes if you think they're not needed. Thanks!
              – codeyinthecloud
              14 hours ago












              "If you are new to developing on Lightning or if you are starting a new project, we recommend using the Lightning Web Components programming model." in my opinion Salesforce it is encouraging to switch to the new model
              – Enrico Murru
              14 hours ago




              "If you are new to developing on Lightning or if you are starting a new project, we recommend using the Lightning Web Components programming model." in my opinion Salesforce it is encouraging to switch to the new model
              – Enrico Murru
              14 hours ago












              Fact that it straight went to GA from pilot makes me feel it's time to start using lwc .And Salesforce has been using this internally so that gives some level of confidence to me to start working with it
              – Mohith Shrivastava
              14 hours ago




              Fact that it straight went to GA from pilot makes me feel it's time to start using lwc .And Salesforce has been using this internally so that gives some level of confidence to me to start working with it
              – Mohith Shrivastava
              14 hours ago












              up vote
              4
              down vote













              Yes, Aura components will work with LWC. In fact, Salesforce has already internally been using LWC for a year now! All those standard components you've used, like lightning:button, are actually LWC components, and you didn't even notice. Aura will be used for the foreseeable future, as it is still the core base of Lightning Components; it's only the higher-level components that we use every day are written in LWC. An underlying framework is still required. What LWC means is that your components will (eventually) be portable to other platforms, like React, with little or no modification, unlike Aura, which is inherently not compatible with other platforms. The most relevant text is actually from that post itself:




              If you are already developing Lightning components with the Aura programming model, you can continue to do so. Your Aura components will continue to work as before. You can build new components with Aura or Lightning Web Components. Your Aura and Lightning Web Components can coexist and interoperate. Over time, you can consider migrating your Aura Components to Lightning Web Components, starting with the components that would benefit the most from the performance benefits of Lightning Web Components.




              You can keep using Aura, or you can use LWC, or you can mix-and-match. LWC has better performance characteristics, so you should consider learning and leveraging LWC, but you'll be able to use Aura until such time that you decide to move to LWC.






              share|improve this answer

























                up vote
                4
                down vote













                Yes, Aura components will work with LWC. In fact, Salesforce has already internally been using LWC for a year now! All those standard components you've used, like lightning:button, are actually LWC components, and you didn't even notice. Aura will be used for the foreseeable future, as it is still the core base of Lightning Components; it's only the higher-level components that we use every day are written in LWC. An underlying framework is still required. What LWC means is that your components will (eventually) be portable to other platforms, like React, with little or no modification, unlike Aura, which is inherently not compatible with other platforms. The most relevant text is actually from that post itself:




                If you are already developing Lightning components with the Aura programming model, you can continue to do so. Your Aura components will continue to work as before. You can build new components with Aura or Lightning Web Components. Your Aura and Lightning Web Components can coexist and interoperate. Over time, you can consider migrating your Aura Components to Lightning Web Components, starting with the components that would benefit the most from the performance benefits of Lightning Web Components.




                You can keep using Aura, or you can use LWC, or you can mix-and-match. LWC has better performance characteristics, so you should consider learning and leveraging LWC, but you'll be able to use Aura until such time that you decide to move to LWC.






                share|improve this answer























                  up vote
                  4
                  down vote










                  up vote
                  4
                  down vote









                  Yes, Aura components will work with LWC. In fact, Salesforce has already internally been using LWC for a year now! All those standard components you've used, like lightning:button, are actually LWC components, and you didn't even notice. Aura will be used for the foreseeable future, as it is still the core base of Lightning Components; it's only the higher-level components that we use every day are written in LWC. An underlying framework is still required. What LWC means is that your components will (eventually) be portable to other platforms, like React, with little or no modification, unlike Aura, which is inherently not compatible with other platforms. The most relevant text is actually from that post itself:




                  If you are already developing Lightning components with the Aura programming model, you can continue to do so. Your Aura components will continue to work as before. You can build new components with Aura or Lightning Web Components. Your Aura and Lightning Web Components can coexist and interoperate. Over time, you can consider migrating your Aura Components to Lightning Web Components, starting with the components that would benefit the most from the performance benefits of Lightning Web Components.




                  You can keep using Aura, or you can use LWC, or you can mix-and-match. LWC has better performance characteristics, so you should consider learning and leveraging LWC, but you'll be able to use Aura until such time that you decide to move to LWC.






                  share|improve this answer












                  Yes, Aura components will work with LWC. In fact, Salesforce has already internally been using LWC for a year now! All those standard components you've used, like lightning:button, are actually LWC components, and you didn't even notice. Aura will be used for the foreseeable future, as it is still the core base of Lightning Components; it's only the higher-level components that we use every day are written in LWC. An underlying framework is still required. What LWC means is that your components will (eventually) be portable to other platforms, like React, with little or no modification, unlike Aura, which is inherently not compatible with other platforms. The most relevant text is actually from that post itself:




                  If you are already developing Lightning components with the Aura programming model, you can continue to do so. Your Aura components will continue to work as before. You can build new components with Aura or Lightning Web Components. Your Aura and Lightning Web Components can coexist and interoperate. Over time, you can consider migrating your Aura Components to Lightning Web Components, starting with the components that would benefit the most from the performance benefits of Lightning Web Components.




                  You can keep using Aura, or you can use LWC, or you can mix-and-match. LWC has better performance characteristics, so you should consider learning and leveraging LWC, but you'll be able to use Aura until such time that you decide to move to LWC.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 14 hours ago









                  sfdcfox

                  244k10185418




                  244k10185418






















                      up vote
                      3
                      down vote













                      To add on top of @sfdcfox. You got your answer in the blog itself.



                      Coexistence and interoperability:



                      With the addition of Lightning Web Components, there are now two ways(but not the only way!) to build Lightning components:




                      • Aura Components, leveraging its own component model, templates, and modular development programming model.

                      • Lightning Web Components, built on top of the web standards breakthroughs of the last five years: web components, custom elements, Shadow DOM, etc.


                      If you are already developing Lightning components with the Aura programming model, you can continue to do so. Your Aura components will continue to work as before. You can build new components with Aura or Lightning Web Components. Your Aura and Lightning Web Components can coexist and interoperate. Over time, you can consider migrating your Aura Components to Lightning Web Components, starting with the components that would benefit the most from the performance benefits of Lightning Web Components.




                      Basically you can use the base components and framework specific
                      components as if today, but you can migrate if you want to take
                      benefit of those of lightning web components







                      share|improve this answer

























                        up vote
                        3
                        down vote













                        To add on top of @sfdcfox. You got your answer in the blog itself.



                        Coexistence and interoperability:



                        With the addition of Lightning Web Components, there are now two ways(but not the only way!) to build Lightning components:




                        • Aura Components, leveraging its own component model, templates, and modular development programming model.

                        • Lightning Web Components, built on top of the web standards breakthroughs of the last five years: web components, custom elements, Shadow DOM, etc.


                        If you are already developing Lightning components with the Aura programming model, you can continue to do so. Your Aura components will continue to work as before. You can build new components with Aura or Lightning Web Components. Your Aura and Lightning Web Components can coexist and interoperate. Over time, you can consider migrating your Aura Components to Lightning Web Components, starting with the components that would benefit the most from the performance benefits of Lightning Web Components.




                        Basically you can use the base components and framework specific
                        components as if today, but you can migrate if you want to take
                        benefit of those of lightning web components







                        share|improve this answer























                          up vote
                          3
                          down vote










                          up vote
                          3
                          down vote









                          To add on top of @sfdcfox. You got your answer in the blog itself.



                          Coexistence and interoperability:



                          With the addition of Lightning Web Components, there are now two ways(but not the only way!) to build Lightning components:




                          • Aura Components, leveraging its own component model, templates, and modular development programming model.

                          • Lightning Web Components, built on top of the web standards breakthroughs of the last five years: web components, custom elements, Shadow DOM, etc.


                          If you are already developing Lightning components with the Aura programming model, you can continue to do so. Your Aura components will continue to work as before. You can build new components with Aura or Lightning Web Components. Your Aura and Lightning Web Components can coexist and interoperate. Over time, you can consider migrating your Aura Components to Lightning Web Components, starting with the components that would benefit the most from the performance benefits of Lightning Web Components.




                          Basically you can use the base components and framework specific
                          components as if today, but you can migrate if you want to take
                          benefit of those of lightning web components







                          share|improve this answer












                          To add on top of @sfdcfox. You got your answer in the blog itself.



                          Coexistence and interoperability:



                          With the addition of Lightning Web Components, there are now two ways(but not the only way!) to build Lightning components:




                          • Aura Components, leveraging its own component model, templates, and modular development programming model.

                          • Lightning Web Components, built on top of the web standards breakthroughs of the last five years: web components, custom elements, Shadow DOM, etc.


                          If you are already developing Lightning components with the Aura programming model, you can continue to do so. Your Aura components will continue to work as before. You can build new components with Aura or Lightning Web Components. Your Aura and Lightning Web Components can coexist and interoperate. Over time, you can consider migrating your Aura Components to Lightning Web Components, starting with the components that would benefit the most from the performance benefits of Lightning Web Components.




                          Basically you can use the base components and framework specific
                          components as if today, but you can migrate if you want to take
                          benefit of those of lightning web components








                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered 14 hours ago









                          codeyinthecloud

                          2,721321




                          2,721321






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Salesforce Stack Exchange!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.





                              Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                              Please pay close attention to the following guidance:


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f242490%2fhave-lightning-web-components-retrocompatibility%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Ellipse (mathématiques)

                              Quarter-circle Tiles

                              Mont Emei