Know how much legacy UI you really have, and what to replace first.
legacy-shopjQuery 1.12.4AngularJS 1.5.11JSP templates- views
- account
- billing
- checkout
- orders
- partials
- Badge / label · orders
- Button · account
- Button · partials
- Button · partials 2Not used
- Button · templatesA decision is waiting
- Data table · templatesA decision is waiting
- Modal dialog · partialsA decision is waiting
- Navigation · partials
- Pagination · orders
- Search · partials
- 1Button · accountLarge job
- 2Button · partialsMedium job
- 3Badge / label · ordersLarge job
1 file is never used. Delete it; nothing renders it.
- rendered insideButton · account
Rendered inside: Card / panel · tags, Custom block · checkout, Form · account. Shown on: Account, Checkout, Orders.
Sweechle reads your repositories without changing them, maps every legacy component and sizes the work, so your teams replace it piece by piece.
Explore the sample scanWhat counts as legacy here
Legacy here means UI built with an old technology the team still relies on: jQuery, AngularJS, JSP and similar. Sweechle counts a component only when its own code or behaviour depends on one of them.
jQuery
Behaviour bound to an element with jQuery
jQuery
$("#save").on("click", function () { $("#dialog").dialog("open");});
AngularJS
An ng-* attribute in the template
AngularJS
<button ng-click="save()">Save</button>JSP
A server template, filled in on the server
JSP
<%@ include file="header.jsp" %><table class="orders">...</table>
Markup alone doesn't make a component legacy: a plain <button class="btn"> with no old behaviour isn't counted.
What you can do
1Map
Know how much legacy UI you have and how big the job is: every component, how many places it's written, and which ones are dead and can simply be deleted.
2Plan
Get a recommended order that never breaks a dependency, then reorder it to fit how your teams work: small jobs first or big ones first.
3Migrate
Your developers get each component's context: where it lives, what has to move with it, what to decide first, and a generated React or Vue version to start from.
4Track
Scan again to see what was replaced and whether anyone added new legacy code.
Built to be trusted with your code
Read-only access
Sweechle's GitHub app reads only the repositories you choose and can't change them.
Your code isn't kept
Repositories are read for the scan, then deleted; only the results are saved, encrypted.
Local folders stay on your computer
Your browser reads and scans them; only the results are saved.
See it on your own code
Start with a sample project, no repository needed, then connect GitHub or scan a folder.