Considerations for Migrating an Application from Lightning v2 to Lightning 3 with Blits

I am currently working on an application for various smart TV models, developed using Lightning v2, and I am considering the possibility of migrating it to Lightning 3 with Blits. I am conducting an investigative study to understand if this migration is feasible and what benefits, if any, could arise from this update.

Has anyone done a similar migration or has experience with the differences between Lightning 2 and Blits? I am particularly interested in knowing:

  1. What are the main challenges or considerations when migrating to Blits?
  2. Is it possible to reuse parts of the application already developed in Lightning 2?
  3. Are there significant improvements or new features in Blits that could benefit my application?
  4. What is the best approach to plan and execute the migration effectively?

Thank you in advance for your help and insights!

1 Like

I’m in the same situation and am seeking the same types of info, thanks so much!

  1. Lightning 2 → L3 is a new framework. It would be similar to migrating from one front end framework to another. The ideas behind L2 & L3 are the same, but the syntax is much different.
  2. Sortof - if you’re architected your app to separate your models / api calls from your UI, you should be able to copy over your API / business logic and just rewrite the UI portion of the app.
  3. L3 is lighter and easier to do future development. If you already have a working app in L2 then it’s hard to justify an upgrade to L3. New development I’d highly recommend L3. The SDF font rendering provides much crisper fonts on screen.
  4. Separate your code up into suggested in number 2. I’d recommend having two apps to migrate. Start building some pages in L3 and leaving some less trafficed pages in L2 while you migrate (settings pages, first time setup pages).

Writing code in one of the new frameworks using L3 is much easier to do development.

1 Like

Thank you for the response @chiefcll .

I have one more question:
Would it be feasible to have both L2 and L3 in the same app? The idea was to avoid changing everything all at once.