i phone break app
- Thread starter almer
- Start date
why technically it's more accurate? I'm not sarcastic, i just want to know why.
Yes it is accurate, i purchased it some day ago and it is accurate, there is another 3d where there are a lot of feedbacks, you should search it.
It's very interesting thus far. On radar, I've clocked as high as 26 mph on a perfect break. With this app, I'm clocking 22 mph which is probably my mode result. I'm actually now questioning radar results. The next time one is available to me, I'm going to use both. If anyone has already done this, I'd be curious to hear what they had to say.
Whoa, now that I think of it, I did my radar speed test on a barbox which might have influenced the results. We have barboxes here so after closing, I'll give it a try on those.
it supposidly calibrates for different size tables,it starts at 7 ft,says 39x78,all the way to 12 ft 62x124 so it shoud get proper readings for all sizes,if 1 is right they shoud all be right,i think they reccommend cueball 1 diamond fr side rail,2 diamonds fr head rail,thats what it shows on diagram on screen,it shows iphone just before side pocket,everybody loves to play around with it and its a good discussion piece
Break Speed.
Whether you like it or not, Jobs' and company created the app market and UI of phones as we know them today with the introduction of the iPhone in 2007.
People decades later still call cotton swabs "cuetips", and facial tissues "kleenex".
It's as accurate as its measurement of distance and time (the math is exact).
It measures distance by where you place the little graphical cue ball on the little graphical table during setup and by where the head ball ends up when you rack. Let's say that, if you're careful, that's accurate to within 2 inches (I think it can be accurate to within 1 inch or less, but let's be conservative).
Accurate to within 2 inches over an average distance of, say, 60 inches = about a 3% average error.
It measures time by clocking the elapsed time between the sound of your stick hitting the CB and the sound of the CB hitting the rack. This is very, very accurate, probably to within 1/1000th of a second - but let's be conservative again and say it's only accurate to within 1/100th of a second.
If we assume that the average player breaks at around 20 mph, then the elapsed time for 60 inches of travel has to be about 0.17 second. Accurate to within 1/100th of a second (.01 second) over an average 0.17 second elapsed time = about a 6% average error.
If I'm not mistaken, that means the app has an average error probably much less than 9% (about 2 mph). The BreakSpeed website says the app is accurate to within one-tenth of a mph at worst and to within a few hundredths of a mph at best - that's at least 20 times more accurate than my rough estimate. Maybe the truth is somewhere between, but that's still much more accurate than a radar gun.
pj
chgo
Last edited:
so what your saying it is very accurate,when you explain how it works it sounds like if its set up correctly its good
Actually, what I'm curious about is, what is the difference between this app and a standard radar gun. One thing that I'm curious about is the difference in speed between breaking on a 9foot table versus a barbox. The reason I'm curious has to do with how speed is calculated. I'm assuming that the cueball's speed is constantly decreasing after the initial impact from the cue. If this is the case, a radar gun MIGHT pick up the speed at initial movement. This app is going to calculate speed based on overall distance, hence an average. Since a bartable is going to be a shorter distance, the cueball should have less time to decelerate hence, the average should be higher.
I agree, in theory it's going to be a more accurate method to measure speed. What's more, it's $5 which is worlds cheaper than a radar gun.
Yes, and setting it up correctly is a simple matter of selecting the right size table and moving the little graphic cue ball to the correct spot on it.
pj
chgo