First of all, congratulations on getting an app working across the 3 powerbases and with nice graphics and logo. I'm sure Scalextric will be over the moon to see your support following their positive decision to release the protocol. Thanks for the time you have devoted in getting this out so quickly.
A couple of minor observations:
The app crashes if it loses focus through minimising, switching to another app and back or going to standby mode and back. Feedback submitted via Google.
I'm not sure if it's intentional, but one thing I notice (on a 5 lap race): at race start and countdown, 1 lap is already showing for each car and 5 laps remaining .
When a car first crosses the S/F line, I don't notice anything to confirm it - "laps remaining" is unchanged and no reaction time or lap count change.
When the car passes the S/F line for the second time, the lap count increases by one (1 to 2), but the laps remaining reduces by 2 (from 5 to 3). A bit confusing.
Also, when the winning car passes the S/F line for the 5th time (and correctly showing 5 laps), I get the "last lap" and "race won by xxx" audio messages together (one after the other).
Apart from the above, I have to say I prefer to start at lap 0, with the first lap counted when the car has actually completed a full lap (after passing the S/F line for the second time) - most slot car lap timers function in this way. Indeed, at launch, the Scalextric app originally started races at lap 1 but later changed to starting at lap 0.
Which method do others prefer?