Legacy is dead. Long live legacy.

Jack5 months ago

I've been following traccar project for many years, and I've been been using almost all it's features depending on the situation.
I have legacy and moden web app generally both served on same traccar API server, so I can easily compare the two.

I think that modern UI is nice but not as good as legacy one, and seeing it dropped from installer in 6.x makes me want to never upgrade from 5.12.

What's wrong imho with moden UI? Top 3:

  • bad multi-select input control: where legacy had a list of checkboxes, modern has dropdown menu. Have you avere tried to link 3 geofences to 10 devices? It is no less than 80 mouse clicks/taps with modern, ~40 with legacy. Same problem when enabling devices on specific users on any user task that require interaction with multi-select input field that can get big.
  • rotating icons on map: where legacy has rotating arrows showing device on move, modern has POI icon. That's simply wrong for a GPS tracker.
  • less efficient use of display space: table-based lists of stuff in legacy UI returns gives more in same amount of space

There are many pros for sure, like the "replay" feature and generally the whole reporting thing, but for a steady use legacy feels more professional and polished than modern.

Do you think modern is really ready to replace legacy?

Anton Tananaev5 months ago

You can continue using legacy app if you prefer it, even with 6.2.

Jack5 months ago

Yes, but with 6.x legacy has just stepped outside the installer.
The "transition" is period is over, It just went from veteran status to second class citizen.

If a new feature is introduced into API, how can I know that legacy won't be left behind (it probably already is somewhere)

Anton Tananaev5 months ago

It is definitely left behind and doesn't support many of the new things.

Jack5 months ago

Is there deliberate intention to not break legacy UI compatibility on traccar API upgrades?

Anton Tananaev5 months ago

There's general intention to not break backwards compatibility of the API, but it's unrelated to the legacy app.

Anton Tananaev5 months ago

But it's not a guarantee.

Jack5 months ago

Thanks for the answers.
I'd want to ask you to write in changelog/blog post when legacy will stop being compatible with Traccar, if possible.
Thanks

Anton Tananaev5 months ago

That's for you to test. We won't be explicitly testing compatibility. Let us know.

Jack5 months ago

Long live legacy! :P

SwayDev5 months ago

I personally think Modern is pretty good, It does have its limitations.

Since this is an open source project that can be easily over-come with user contributions.

I agree with the author of this post, the "connections/permissions" management can be improved. Hopefully someone will share or contribute to improving it.

Walter Spadaa month ago

I agree with Jack.

Legacy might be whatever the reason they took it out, but modern is absolutely not complete, nor fully usable, nor fully friendly.

I and all the users in my server USE A LOT of route reports and current version IS HIDEOUS handling it on screen.
The pointing arrow on the direction of the vehicle, also is a MUST.
The only plus I find is the click device on screen and access it's reports without having to re select it from a list.
The replay feature is actually not too necesary because you can have it using a 3rd party app on a cellphone/tablet, even with older versions without Modern UI.

I'm currently trying to add legacy UI and/or use a 3rd party interface to see if I can recover some functionality.