Navigate back to certain page without click next (200 pages)


I have screen with so many pages 200+
Users sometimes need to get back at same spot , how to make this feature?

Clicking next is time consuming , so it will not help!

Can you clarify what “get back at same spot” mean? Do they go to another tab and want to get back to a certain step in your process?

Also, what are the 200 pages for? Is it a form?

1 Like

No i’ve a content app , more than 20K of questions (not a form) , so every page has about 10-20 questions , so there are about 500 pages at least , so if user conumed the content and lets say he stopped at page 30, next time how he will get back to the same spot ?

I’d try limiting what’s displayed, to not be listing all 20k questions. Lots of ways you could do such, but anytime you want to know what’s been seen, you’re going to have to use updates to be recording what they’ve viewed.

I would think along these lines…

Display only 20 questions, and a next button. The next button needs to iterate between pages of questions. If you were doing single items at a time, I’d put a “last read” timestamp column on the data. Then filter the list to see only items with a last read date that’s not more recent than a last reset timestamp that’s used for resetting the view. With 20 items that you want to mark read at once, it makes it harder. I think you’d need to batch them.

You could do it the same as the individual item method, but relate it to another sheet, call it question batches. The batch is then marked with the last read timestamp.

Or use an index to label each batch, and your next and back buttons increase or decrease the index, and the list of questions is filter viewed or queried by batch index.

Think that would work for your app?

1 Like

Nice, but am not sure how this could be done, I am new to the concept of timestamp but after reading your reply, I thought about using a filter, whenever the question is answered, it will not be visible by default, basically when the user answers any question I store that question as (used/attempted), then i hide it form the list. What do you think, which way is more convient for me and the user.

Thank you very much for your reply

I didn’t realize in your previous post that the questions were being answered, rather than just viewed. I checked out your app… nice! Quizzes with the answers explained are a really nice study tool.

I’m definitely thinking about update cost with this app though. When someone clicks an answer, that’s marking the question answered… doesn’t seem you’re actually recording the answer, just toggling for visibility sake, but that’s still an update. Since you’re already doing that, you might as well have that doing a timestamp. I’m thinking something like this:

  • Only one question is displayed… use a rel & single value rather than filter, so it loads faster.
  • Clicking an answer is a custom action that does two things… writes a datestamp (could also record the answer… would be nice for later reviewing questions answered incorrectly) and opens the details screen to show the right answer, explanation, save, etc. When closing the overlay, the user sees the next question.

More explanation on how to view a single question with datetime…
Have a relation for all the questions of the topic you want, along with having a datestamp empty or older than last reset timestamp. Then have single value to pull a random question from this list (or sheet order if you want same order for everyone)… and have that question displayed. If it’s important for you to have the same question displayed if a user leaves and comes back to the app, you can do sheet order rather than random. And if you want random and to hold place, you need to do a bit more which I won’t explain here, but you can do it.

Hopefully that helps! Definitely reminds me of my friend finding app that goes through one profile at a time, only showing one at a time, in random order, lots of filters on which profiles are eligible to view, and coming back to same profile if you leave/refresh the app.

1 Like

Data structure , i will look for any lessos about datetime and the how it is done , bc it is new to me