Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Swipe left loads random article when on most recent history item #1142

Open
nleoutsa opened this issue Mar 18, 2025 · 7 comments
Open

Swipe left loads random article when on most recent history item #1142

nleoutsa opened this issue Mar 18, 2025 · 7 comments
Assignees
Milestone

Comments

@nleoutsa
Copy link

The randomize button is great fun, but its placement at the top makes it difficult to reach. Since nothing happens when you swipe left from the most recent page in history, perhaps it could default to load a random page from the current ZIM file?

Alternatively, we could add an option to relocate the randomize button to the bottom bar for easier access.

@kelson42
Copy link
Contributor

@BPerlakiH Does not swipe left should alloq to navigate back in the history?

@kelson42 kelson42 added this to the 3.9.0 milestone Mar 18, 2025
@kelson42 kelson42 self-assigned this Mar 18, 2025
@rgaudin
Copy link
Member

rgaudin commented Mar 18, 2025

@BPerlakiH Does not swipe left should alloq to navigate back in the history?

@nleoutsa suggests that this behavior would be only for first article, when there's no (more) history to go to.

I don't think it's a good idea: too unexpected and non-intuitive. But maybe the random feature is not visible/accessible enough…

@BPerlakiH
Copy link
Collaborator

Thank you for your suggestion @nleoutsa.
I agree with the above that adding this feature to the top of the "stack", when there's no more page to go back to would be probably confusing, and would lead to other navigation issues as well.

Our current bottom bar is quite packed already, and there's literarily no more space left.
The most compact version of that view is the iPad slide over view:

Image

I remember that adding one more icon there makes the icons "overflow" the width.
That leaves us only one option to swap out the icons (we need to remove something to be able to add something else in place).

The top candidate from my perspective would be the "share" button... but it's hard to tell.

Since we do not gather analytics on our users, it's hard to tell which button is more frequently used by the majority of Kiwix users.

@nleoutsa
Copy link
Author

this behavior would be only for first article, when there's no (more) history to go to.

when there's no more page to go back to would be probably confusing

Sorry, these descriptions are the opposite of what I meant. I meant when you are on the most RECENT page visited, and there is no page to swipe FORWARD to, that it could be fun to have the "swipe forward in history" behavior trigger a random article rather than doing nothing. On my device, swipe left moves forward on history, not back.

Alternatively, exposing the ability to customise which buttons appear at the bottom would circumvent needing to make the choice for users based on usage statistics.

@nleoutsa
Copy link
Author

I agree the swipe idea is not the most intuitive, but wonder if some visual indicators would help. Perhaps when you start swiping past the most recent history item, a screen slides in with a message like "You've reached the most recent page in your history. We'll load a random article for you." A similar page could slide by when going back in history between "history blocks" (consecutive history entries where a direct link was followed rather than a random page loaded).

I'm just brainstorming ways to replace doom-scrolling social media/news with knowledge discovery and would love to hear other ideas!

@BPerlakiH
Copy link
Collaborator

I see what you mean now. I am still not convinced about the swipe approach. Customising the button placement is more interesting in this approach. Maybe we will come back to this, and use the new tab bar from iOS 18 for iPads (the current minimum is iOS: 16.6).

@nleoutsa
Copy link
Author

Love that idea, thanks for considering!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants