LFC History 2.4.1 has now been released to Google Play.New FeaturesTRANSFERS
A lot of performance and stability changes have gone into this but the main thing worth talking about is transfers.
It is now possible to see a list of transfers by season or by manager. A new tab has been added to these areas of the app which list players in and players out, clicking on the player will take you to that players profile.
For each view the spending totals are displayed including net spend.
As requested by some users, it is now possible to select the content of the widget. The options are history facts and the next match or just the next match.
The match notifications should now work off your local timezone so you should no longer have the issue where you are told a match is about to kick off an hour or so after it is finished.
LOSS OF SERVICE
A couple of weeks ago there was a problem with our servers which meant the app could not update. Most parts of the app were fine but a couple of features did not handle this loss of service as well as it should have. This has now been resolved.
NEXT MATCH WIDGET
Previously the next match was only loaded when the app was opened. This meant that if there was a game on Saturday and you had not opened the app since the game, on Sunday the widget would say that the match was -1 days ahead. The moment you opened the app it would correct itself and point to the next game. This have now been updated so that the next match data is automatically downloaded when the previous match finishes. This means that the widget will always be showing the correct data even if you don’t open up the app itself.
Get over to google play to get the update now. Don’t forget to leave a rating whilst you are at it
If you experience any issues or would like to suggest some new features you’d like to see, please leave a comment or get in touch on Twitter or Facebook
NOTE – These features were originally released as 2.4.0 up that contained an issue when downloading and trying to display just one transfer from the seasons view. 2.4.1 was quickly released to fix this issue.
I am a Liverpool supporting software developer originally from North Wales, now living and working in Manchester.