BOTH the classifier function AND the follower/Markov chain function work! They display the data in tables, and then can drill down into the column stats view with the additional stats collected!

When I started building this, I designed from the top level screen down each button path...

The main screen has 2 buttons, "update draws" and "choose game"

I went down the update path first and got that 100% functional.

The choose game brings up a collection of buttons representing 14 current PA lottery games. When you choose a game, it takes you to a screen where you can choose to calculate classifiers or show followers.

The next screen for each displays the column headers and the aligned column data. From there you have 2 choices... go back or display the column statistics... the stats screen shows the stats unique to the chosen processing method... and it does it correctly!

Every screen has a back nav button.

I went through multiple games to ensure specialized features worked (like the bonus balls in PB, MM and Cash4Life)

It is not perfect yet, but the thing just works!

The learning curve was a bit steep, but not as bad as I thought. Having done some Ruby on Rails tutorials a few years ago helped with the MVC pattern concepts.

Because I kept with the mantra of make it work first, then make it look good, I know how all of the parts fit together, so any changes to ball matrices or new games can be easily added, and if a game gets discontinued, I know how to remove it. As I learned more about kivy, the screens near the end look better, so I will have to make sure the new concepts get propagated to the earlier, more utilitarian look of the starting screens.

I wrote the follower script over a year ago. It went through many tweaks to get it modular enough to use in an app... even before I knew what shape the app would take.

I am just super excited that this went from project folder last month to functional prototype application now!

The only functional change I need to make yet is to put my frequency sort back into the classifier output... then the rest will be cosmetic changes, creating and adding graphics and ensuring there are no more edge cases left to test for.

I will say that one decision I made was to NOT have a settings page where the numbers could be tweaked... that is best left to the original script sandbox. That saved on generating another screen that was context sensitive AND I did not have to sanitize user input.

Every screen can make use of Google's Material Design elements, so getting a unifying theme together should be straightforward.

Up until today, I was faced with the follower output working but the app crashing when trying to view the column stats for classifiers... that was fixed on the python side by reading the data shape for the script output and matching it to a specific display format (using kivy "card" widgets instead of generic display areas).

The end to end tests were a success! No idea how long it will take to make it look nice and to incorporate graphics, to properly document and to get ready for the Android port, but I have a gut feeling that I will hit my 2026 goal of having this app on my phone before year's end!

Just had to celebrate the functional win! 😎