Comment 3 for bug 1291502

The problem is valid .
The solution you propose is doubtful.
Keep in mind this is not skeumorfism . The behavior of the application should not be used as a real object.
You have to keep the interface clean , fewer items will be better. This is not a real stopwatch , this is just an interface that refers to a stopwatch .
New design guidelines are to come soon and not worth working hard to change the design radically , even when there is a pending design approval.
I propose the following .
The row labeled "Recorded laps " will be hidden until we add a new lap. When a return is added this row will appear .
When the timer starts the upper indicator will move. Likewise when it is paused.
But when we add a new twist , there will be a small animation in the central number , is ultimately where we are always looking and is the largest point of care. In addition it will be an ever visible mark ( in other colors) on the clock.

My English is not very good so I attached a picture.