My boss believes this was discussed before, but I can't seem to find any info.
We would like to force the user to go back to an HTML navigation at the end of each stack via a button. The problem is that if the user ignores the button, they are able to swipe to the next stack.
What we would like to do is prevent the user from swiping from stack 1 page 10 to stack 2 page 1 while still allowing the user to swipe from stack 1 page 10 back to stack 1 page 9. (Otherwise I would add an invisable scrollable frame)
Any experience with this?
The scrolling frame thing is going to be fixed next week…and why exactly do you want to stop your reader from moving forward through a publication?
We have one large HTML element that contains portals (with video) to each section. What we would like is for it to throw the user back into the HTML element after each article so that they have to watch the intro video for each section.
I know this is controlling the UX a little more than usual.