I'd like the ability to flag laps as bad data. Last night was my first night experimenting with this specific app/device but I've run into this with LiveTime and Flipside as well.
Use case - https://www.youtube.com/watch?v=65CUPTmQkEY&feature=youtu.be
This was the track I laid out for testing, I wasn't able to keep the track ONLY in the basement, I assume reflective issues and a high 5.8 noise floor contribute to this issue. (I live next to apartments and can see anywhere between 4 and 8 SSID's at any given time.)
Scenario - 10 second min lap time, I clear the lap timer on the table saw but have a delay in rounding the turn and getting back out before 10 seconds is up... as I pass the timer again it pings a 2nd hit at 11 seconds... and my lap time on the lap I complete is wrong as well.
First Min Lap Time - this can be increased, but it's not the ONLY solution. For example I'm running ~25 second laps on this course, but it's quite possible for a pilot better than me to fly it much faster, so there's a point where "Min lap" and "reasonable lap" get too close to each other.
The ability to (after the session is done) tap a time and designate it as "bad data", remove it and adjust the following lap to have that time included in it, would eliminate this in the rare case Min Lap Time doesn't.
This is also an issue on the start, if I have a 10 second min lap time and start the race, but for whatever reason it takes me 20 seconds to get started I have bad data for my 'fastest lap' and my average is skewed.
Another issue, but along the same thought is missed laps despite going through the gate. In this case the way I've seen it handled is allow the user to "split" a lap... so if you know you flew 5 laps but have times on 4 and one is ~2x normal, being able to split that at least gives SOME data integrity for your average lap times.
This is all about data after all...