ReadYouApp / ReadYouApp/ReadYou

Suggestions for a Better Reading Experience

Open
#647 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Kotlin
Stars
7.5k
Forks
330
PR merge metrics
No merged PRs in 30d

Description

I propose that ReadYou always displays the number of unread articles regardless of the filter condition, whether it's "All," "Unread," or "Starred."

Here are the reasons:

  1. Displaying the total number of articles is not useful:
    The total number includes both read and unread articles, making it difficult to see how many articles need to be processed.
    Users need to take extra time and steps to see the number of unread articles.
  2. Displaying the number of unread articles helps users quickly understand how many articles need to be processed, which can improve work efficiency:
    Users can see the number of unread articles at a glance, without any extra steps.
    Users can decide which articles to prioritize based on the number of unread articles, which can improve work efficiency.
  3. This logic is consistent with Reeder:
    Reeder is a popular RSS reader that also uses this logic of always displaying the number of unread articles.
    This shows that this logic meets user needs and can improve the user experience.
    I suggest the following changes:

Change the article count in ReadYou to always display the number of unread articles.
Before:

All articles: 100
Unread articles: 20
Grouped article total: 100
After:

All articles: 20
Unread articles: 20
Grouped article total: 20
The modified interface is more concise and clear, and it can help users quickly understand how many articles need to be processed, which can improve work efficiency.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Android UI that displays article counts and trace how the current filter determines each count. Confirm the behavior for All, Unread, Starred, and grouped articles. Done means every displayed count uses the unread-article total, matching the examples in the issue, with relevant UI tests updated or added if the project has them.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.