If this is any help I counted the times the animation runs from starting/restarting the app until it becomes responsive. It was about 35 times (that’s the blue blob going all the way around). I think it’s about one second per revolution.
We are aware of a bug in Gobang which results in the game showing the spinner perpetually when sending a chat. However we thought we had fixed it for 1.5, can you let us know which version of the client you were running? (Its in the options screen)
The load time at start up that you counted is unrelated to that bug but is directly related to the number of games you have in your list. As one of our most active players you do have a larger that average number of games, but none-the-less we are looking into optimising the amount of data you need to exchange with the server. Or at the least ways of mitigating this wait.
I’m no expert on this stuff but presumably it must be possible for the game to check in with the server and receive back a list of incoming turns/messages which should be near enough instant if there’s nothing new incoming?
Currently the delay happens every time which would suggest the client is polling every active game or downloading the status of all active games each time.
You’re right, each time the app is brought to the foreground we do a full match retrieval, which brings to your device all the information about your games list. The reason we do this is data-integrity across multiple sessions (across multiple devices). This is necessary so that we actually can use partial match retrievals within a session safely across multiple devices.
Now that we are happy with the functionality, we are now looking into optimising the data which should ease the load on your games list