Swackles/the-finals-tracker

I'm working on a Figma for the project !

Opened this issue · 6 comments

To give the site a more modern tone and to match the design of the game site, I spent some time on a Figma prototype. It's not the prettiest design, I put in random values and then the images are to be changed in the future, but I tried to make something clean. I'm sharing the link here, even though it's not finished. I haven't prototyped the application, but it's simple enough to understand.

Figma File

In this Figma I'm also exploring the idea of making a complete tracker : player tracker, leaderboard, server status, etc...
See if there are other ideas.

Shiit man, this looks badass.

There are only few things I have to add:

  • Currently player search is not happening, it's planned, but for the future.
    • This depends on how many players are willing to 1. supply us with their statistics and 2. how many are willing to make it public
  • The JWT will remain as main input, with JSON upload coming as secondary (in next few days)
  • I'm using Joy as the component library, so if you can use as much of those components as possible.

I'm done with the weapons and match history pages for now, but I'll share my current plan with overview:

  • Move the classes table to it's own page
  • Show playtime/kills/damage per class using donut chart
  • Show winrates using bar chart
  • Show history of round statistics (kills, deaths, revives) over the last 10 games (in a graph)
  • Top Class (create a ranking algorithm based on time played, kills, damage, and win rates)
    • Top weapon and gadget for that class
  • Current rank in each played platform (crossplay, steam, xbox and ps)
  • Fame history similarly on how we dit it here

These changes aren't final, but current idea.

Thank you very much! Of course, the search for players was in view of the site's future. We now hope to have access to a public api where we can access all the data.

I'm going to redesign with your "Joy" component library.
Thanks for sharing your vision of the application's future, I'll work on it after a little rest.

Finally, I think that the overview/dashboard can group together the essential information so that we can quickly see the player's statistics.

I looked at your "Joy" library component. It's a design a bit like the old Android ones, how can I say it's not the thing I like the most. If you're not comfortable with the front-end, I can try to take care of it. I've got quite a few things to finish before I can put 100% into the project. In February I should be a bit freer.

If you can find another component library that better suits your design, I'm fine with that. I just don't want to build a completely new one from scratch. Joy for the most part follows the material design guidelines while giving a bit more freedom, that's why I like it.

I see and I understand. I'll make two versions if you don't mind: one with "Joy" and the other I'll make on my own on a fork. That way I'll deliver it to you when I'm done and you won't have to do a thing.
I think I'm a bit of a pain, but I like having a less rigid graphic part. But I like doing that.