Whenever a user has the current round open, scan the fixtures every [time period] and if a fixture that doesn't have results yet is within a time range where results might be on the server, check for results and update. This way, if a user has the app open and during that time results come in, things don't look stale.
The implementation of this could be smart enough to prevent initiating too many server hits although it'd only need to do a shallow fixture request anyway so it'd be very light touch.
Whenever a user has the current round open, scan the fixtures every [time period] and if a fixture that doesn't have results yet is within a time range where results might be on the server, check for results and update. This way, if a user has the app open and during that time results come in, things don't look stale.
The implementation of this could be smart enough to prevent initiating too many server hits although it'd only need to do a shallow fixture request anyway so it'd be very light touch.