[lwansbrough]

I'm one of the primary engineers behind tracker.gg. If I could offer some constructive criticism:

- You probably don't need individual pages

- You're polluting my browser history as a result, not very user friendly. :)

- I shouldn't have to navigate away from the "direct" view to add weapons

- The "direct" view and the "table" view are functionally equivalent. You should figure out how to combine these into a single optimal view - shouldn't be difficult since they do the same thing.

- Your "winning" cell highlighting isn't really clear. Yes it's lighter, but that's not really an effective indicator of "best" (on tracker.gg we use gold highlighting to accomplish the same thing in our view: https://battlefieldtracker.com/bfv/profile/origin/Z1nYoRiTa/...)

- Your various filters/modifiers should probably be colocated with the selected weapons, they're all filters.

- With a single table there's probably room to split the view in half to show graphs/detailed breakdowns to the right of the main table. Your "direct" view uses an inordinate amount of space. (I'm thinking something like our Valorant match viewer: https://tracker.gg/valorant/match/a06b84a9-bdd2-4509-90ca-fa...)

Overall pretty cool, I could see something like this being popular with Valorant too.

[michaelmdresser]

I really don't mind the individual pages and I don't think it really "pollutes" the browser history either. Rather, I think it makes it much easier to link a friend to a specific comparison.

[lwansbrough]

You can do this without spamming history, just replace the state instead of pushing it.

[bcyn]

I think you should be using `replace` more judiciously. IMO its primary use is redirecting from some kind of invalid state/URL, i.e. when the user does not want to ever go back.

For all valid states/URLs, users expect that the browser's back and forward button work as expected, and that they can save or send that link to others.

[lwansbrough]

I think you should be using push more judiciously. If I visit a site, click 3 buttons and blow up my back button so I have to hit back 4 times to get back to HN/Google, I'm not returning.

Users expect the back button to work for page transitions, not state/UI transitions. And again, this doesn't impact the ability to send the current page state as a link whatsoever.

[vercadium]

Thanks for taking the time to comment! I disagree with you on the history though. By the same token, a large portion of users would press 'back' to expect to return to a previous view, only to exit the site. If I land on a site from Google and click on 'About us', I expect to need to click twice to return. I think it's intuitive as-is.

For what it's worth, pure state changes (that don't occupy a page within the router) do use history.replaceState though.

I understand that this wouldn't be the case if I approached the design as per the rest of your feedback; placing a lot of this content within a single view could be done. However, the UI/UX is designed to be shallow, minimal and mobile friendly.

For example, while I could put weapon selection in as a filter and add controls to toggle between data views - creating a single powerful view - this doesn't actually accomplish much other than trading valuable space for increased UI complexity to avoid moving views.

Admittedly, I see this through a different lens as I'm aware of the amount of controls I need to somehow fit further down the line to support upcoming features. A desktop only site would be very different!

I appreciate your feedback; it's great to see things from another perspective.

[finger]

Some stats on your page seem obviously faked. E.g top 1 cs go player has 11600 days of play time. Longer than the game even has existed.

[lwansbrough]

Yeah, our CS:GO site doesn't get any love, it has received a total of about 10 hours of attention - that's why I avoided using it as an example. Cheaters run rampant in CSGO, it's not a problem exclusive to our site unfortunately. We're exploring ways of automatically detecting cheaters across our network though.