How are folks modeling user state for their onboarding tours?
The more I think about it, the more I see challenges with storing this in a traditional RDBMS due to how often the experiences change. I'm considering using a JSON blob but that seems brittle and challenging to maintain/migrate
I'm not saying this is good, but in some previous life, we kept the tour "slides" in the code, and just registered which slide set was seen in the db. If the slide set wasn't seen and was in the code, we'd show it.