1–6 of 6 posts
By cookie? But he'll be prompted to do it again when he logs in from another device. Database? Overkill? What's a good design? Caveats? Any other ideas?
In Usable Requirements (http://www.usablehq.com) we use an untracked JSON object as part of the user document for preferences (this is in MongoDB). This means we don't have to keep a schema up to date - the front end can essentially put anything in that object (subject to some validation obviously). Consequently the front end code has to be tremendously defensive as values may or may not be there, but that's a good thing anyway.
If for a visitor, meaning you have no clue who they are then I'd store a cookie, and give them the option to skip out of the tour if they have already seen it.
My question would be, user or visitor? If user than I equal that to a logged in or known person and therefore I would store it in a cache of some sort that is also persisted for those times you have to reload. If for a visitor, meaning you have no clue who they are then I'd store a cookie, and give them the option to skip out of the tour if they have already seen it.