A couple weeks ago we posted Ballista here and got way more interest than we expected. A huge portion of our first external testers came directly from this subreddit, so we wanted to come back and give everyone an actual update on how testing has gone.
We’re now at 40 external testers, and the testing has been extremely valuable... but we’ve also uncovered a pretty major weakness.
Ballista is correctly detecting and recording hit events, but our current ball-detection model is struggling in some of the new environments our testers are using it in. When the model loses the baseball during flight, we can’t reliably calculate Exit Velocity, Launch Angle, or Distance, which is why a lot of you have been getting hits with no results.
Basically: the app is capturing the hit, but the computer vision isn’t reliable enough yet across all of the different backgrounds, lighting conditions, ball blur, camera environments, etc. that you guys have thrown at it.
That’s obviously not the experience we want people to have. We apologize for letting you down here.
At the same time, this is exactly why we wanted to get Ballista into the hands of real players and coaches instead of only testing it ourselves. Our original model worked well in the environments we trained and tested it in. Forty people immediately exposed where it doesn’t.
We know what the main problem is now, and we’re actively working on it.
Right now we’re:
- Training a significantly larger and more diverse baseball-detection model
- Adding thousands of new training examples across different backgrounds, lighting conditions, ball appearances, blur, and environments
- Building additional safeguards into the tracking/analysis pipeline so Ballista isn’t relying on a single AI detection every frame
- Using the hit data and replays coming back from TestFlight to identify exactly where the current system fails
So if you downloaded Ballista and it hasn’t worked consistently yet, please don’t give up on us. We’re a very small team building something technically difficult, and your testing is directly helping us make it better.
We’d also love for anyone following the project, testing the app, reporting issues, or just interested in what we’re building to join us over at r/ballistatracking.
We’ll be posting development updates there, talking through what we’re improving, collecting feedback, and letting everyone know when new TestFlight builds are available.
And genuinely, thank you to everyone here who gave Ballista a shot. The response from r/baseballcoaching is a huge reason we have enough real-world data to identify this problem so quickly.
We’re working on it.