Blazing Wheel 1000 binds every session β±οΈ you log π to the exact hoof package that was on the horse at the time, so you can see π which shoeing and stud combination actually held up on which surface and going.
Record a hoof package once β shoe type β¨οΈ, pad, stud size and stud pattern π’ across all four positions β and set the date it took effect. From then on, each jog, training session β±οΈ or race you log π in Blazing Wheel 1000 inherits that package automatically. You never re-enter hardware to reconstruct history.
Going is structured, not free π text. Pick the surface and condition from a catalogue that ships inside the app π± β dirt, turf, synthetic, gravel and snow across hard, good, cushion, sloppy, deep and frozen β and set cushion depth against a live cross-section gauge. Slipping, grabbing and interference are typed session β±οΈ flags, so they feed the package score π’ instead of sitting in a comment.
The going matrix is built from your own record. Each cell is one package against one surface, sized by how many sessions β±οΈ sit behind it and shaded by how that package survived. Open any cell to read the exact sessions that produced the number π’, alongside the shoe-loss events counted against it. Pin a package to a surface and it becomes your one-tap π starting point at the next reset.
Attach a photo πΈ of the track or of the shoe to any session β±οΈ, from the camera π· or your gallery πΌοΈ. Photos stay on the device, filed to the session and reachable from the matrix cell they belong to.
No account, no sign-up and no network connection are needed. Horses, packages, sessions β±οΈ, flags, scores and photos πΈ are all stored on your device π± and computed there β Blazing Wheel 1000 works the same on the rail with no signal as it does at home.
Add your first horse in Blazing Wheel 1000 with its current package, then log π your next session β±οΈ from the rail.
Log π every session β±οΈ with the hoof package and going it was actually run on