This morning I started attempting to figure out how the 'tap it out' functionality I want can actually work. I want it to be dynamic based on whatever speed the user goes at, as long as it's somewhat consistent per letter. Checking every frame and keeping track of how many frames a button has been pressed is pretty easy stuff, but caused me to have to reckon with the fact that I don't have anywhere to store state yet- I just jumped right in to the Morse code functions because they were fun and interesting.
After some pondering and talking stuff through with my wife, I think I have a really neat layout for how the game state can flow, with a place to keep track of world stuff while in menus, and hopefully a decent bit of structure without being overwhelming. Sorry, that's kind of vague and floaty, but that's where I'm at right now. Gotta keep this mysterious, right? (It's just a bunch of enums and structs. That's all right now. There's going to be associated functions, too, like update and draw. And that's all computers are- just data and functions.) Now that I know where the state should be put, though, I think I get to start biting into more of the meat of how to parse human tippy taps into Morse code a computer can reliably read, which is pretty exciting! (To me, at least.)