Closed heymarkreeves closed 9 years ago
Hey there, Mark! I think that you mean that it should pop up automatically on the first visit, and after that it should pop up automatically whenever they click on something that would normally require a login, like favorite stars. But we don't want it to pop up on every single page, correct?
The trouble with telling it to always check against the auth token cookie is that, due to the way jQM events are set up, the check would fire every time a page change occurred. I would think this would be pretty annoying, as it would just pop and pop and pop...
Brainstorming...I can put in a check for certain IDs within page content, if we want to take the approach of having it trigger only on certain pages? Or we could stick with the prior visit approach + adding in modal pops from favorite stars, or always pop it on certain pages (Discover page, for example). Or maybe we could start a running count of pages visited and pop the modal every 20 pages visited or so?
Lots of ways we could approach it...thoughts? :) Thanks!
Hi, Sherri!
Sorry for the ambiguity on this :) Just the Discover screen (the homepage), if auth token is not present, as well as anything that would normally require a login.
So if you visit the site's homepage and don't have a logged-in session, you should see the sign up screen.
Thanks!
Mark
This should be all set now! Let me know what you think. :) Thanks!
Great - Thanks!
Hi, Sherri!
Giving this some thought, I think the Sign Up modal has to display any time the auth token cookie is absent, not based on a cookie tracking whether the user has seen it already.
To keep in mind here is that they don't want this to be a "what's coming up" app that people go to just to find events. They want to focus on relevancy, which means you really need to be a logged-in user with history & interests. We need to get anyone who visits the URL to sign up.
Thanks!
Mark