Structure Data to present in Front-End App Soccer Results

Ask for Help
1

Hi everyone,

I´m trying to build a Soccer App to show game results and I have a little difficulty finding the ideal Data structure.
So, I have 10 teams which they Play every Weekend and my idea is show the game results per Week (If Someone open some “dropdown or something like that” about Week 1 see five games with the results, if you open Week 2 see the games in that week and so on)

I share below the Google Sheet with the approach that I have

Can someone help me find the correct logic or ideally structure?
Thank you in advance,

Google Sheet Doc: Inter Freguesias 22/23 - Google Sheets

2

Haven’t gotten the chance to look at your existing data structure, but to achieve what you’re envisioning, you’d ideally want to record game results for each team via a form button/container. Collect the score, week, teams, etc. in the form and send it to a table of “results”. Then use that table as data source for the screen. You can add a filter for the week, team, etc.

3 Likes
3

The data structure Megann mentioned would work, and it can look like this.

Week Team 1 Name Team 1 Score Team 2 Name Team 2 Score
1 Team A 2 Team B 1
1 Team C 3 Team D 2
2 Team A 1 Team D 1
2 Team B 2 Team C 1

And ideally you should keep that all in the same table.

2 Likes
4

First of all, thank you (both) for the quick answer/ help.
Now, I think I understand the logic in the DB structure, in order to see the main solution/ next steps, after I collect that info I can put the filter in the Front-end/ interface correct?

One more time, thank you all for your time
Kindest,

5

Hi, i’ve done many football apps on Glide. Your biggest challenge is making the display look good. The backend is not that complicated.

You can place a choice component that writes to a user specific column where the user selects the week and then filter the collection below it to show only fixture results from that week, but I don’t advice you to do so, because every change in the drop down, will cost you an update.

instead if you can, display all fixtures from all weeks in the collection and allow users to use Glide’s In App filter to view a certain week.

6

Hi Abdo,
Thank you for your time.

Could you send me some Glide App about Football Results to see how it look?
How i can execute your suggestion “display all fixtures” and use filter view in the Interface Glide App ?

Taking into account that you glide accounting updates, using the approach of placing a “card” per week and after entering the card you automatically see the results for that week, would this be considered an update? (or more than one update)

Kindest

7

It is somewhat like this but like @abdo said, it will eat your updates quota.

No, that won’t be considered an update. You can keep the same data structure as I have, but add a new table that you only store weeks. Then you create a relation from that weeks table to the records table and display the records inside each week’s details view.

1 Like