The plus of the Angular upgrade path that I saw you mention elsewhere
was that you could have both old and new Angulars running in the same
app, and migrate slowly. That would work for a change of backend, using
the same styling.
It really depends on what your goal is: a refreshed UI or getting rid of
My aim was to keep the UI the same as this gave a very clear way to
validate success. If you change the UI at the same time, identifying
success becomes harder.
Also, replacing the backend without changing the UI is quite possible
with limited graphic design skills. Modernising the UI would require a
different set of skills, and would probably involve us bringing in a UI
designer from somewhere to give us mocked-up components to start from.
So really, the question as to how best to do it will likely depend on
who is doing the work.

On Sun, 15 Apr 2018, at 6:13 PM, Jan Høydahl wrote: