Units update & App progress

Note: This update may require a browser refresh to ensure you have the latest files. We recommend a hard refresh (CTRL+F5) which will force a refresh of the browser cache.

Today a broad range of updates have been applied throughout iGP Manager. Much of what has been included are fixes and substantial progress in the mobile application version iGP Manager, which is currently being tested privately. Below, I will list the front-end changes you will probably notice. There are relatively few noticeable changes in the web version of iGP Manager with this update, but here they are:

• New 'Units' tab on the 'Settings' page
  • Set custom units and symbols for Currency, Temperature, Speed, Weight and Height values throughout iGP Manager
• Added clear indication of Chief Designer strength and weakness to 'Cars' page and Upgrade and Research dialogs
• Default Speed unit of measurement has changed to MPH, but can be changed back to KPH easily using the new Units setting
• Fixed incorrect Objectives showing when 'Go to race' buttons appear
• Moved 'Save' button to header for several dialogs to improve mobile interfaces

Mobile app update

As I hinted at above, work continues behind the scenes on the iGP Manager mobile app. We are seeing good progress in all areas and recently began devoting most of our focus towards the first version of the mobile app as it comes nearer to release. There has been a huge amount of progress in that area as of late and we are continuing to accelerate its development up to launch.

Translations update

We will also begin translating iGP Manager soon, and if you volunteered then I should be in touch around the start of February, possibly at the end of January. The main reason translation keeps getting pushed back is we want iGP Manager to be in a relatively static state before we do them. Once translations are added, there will be a lot more work involved in launching changes or new content, because obviously it all has to be translated. With iGP Manager only being in English currently, the workflow is much more direct and allows rapid deployment of updates. For that reason, we don't want to put translations ahead of too many big changes or new features, to avoid having to go back time and again for translations.