Web app re-design wishlist

[lemon24]

As reader got new features, the web app has accreted a lot of UI clutter compared to when I first planned it; as mentioned in the roadmap, a re-design is inevitable.

This issue is to collect issues / features, in the hope that they may be easier to address in the re-design.

If you have any suggestions, please add them in a comment.

---

Here are some from me (a lot of them can be handled via plugins):

• Suggest to add tags (from the existing ones) after adding a feed.
• Allow using preview_feed_list to find a new feed URL (and switch to it) when the old one goes 404.
• Notify about broken feeds in some way and suggest a resolution.
• Share links (Reddit, HN, etc.).
• Better plugin integration; at the very least, it should be possible to add plugin tags with example values by clicking something.
  • E.g. single-click dedupe entries by title.
• Dark mode.
• https://github.com/lemon24/reader/issues/130
• https://github.com/lemon24/reader/issues/151
• https://github.com/lemon24/reader/issues/304
  • By default, only show commonly used filters: has enclosures (unread), important (all, unread), read (unread), random (unread). For these views, show (cached) counts.
• https://github.com/lemon24/reader/issues/313
• (maybe) https://github.com/lemon24/reader/issues/121
• Alternate default view (e.g. to only include entries from feeds tagged with main, or only up to the previous midnight – so entries appear to update once a day, as with https://github.com/lemon24/reader/issues/314).
• Metadata edit page for .mark-as-read shows a list of matching titles.
  • Better still, suggest rules based on n-grams of don't care entries.
• Hovering feed title (anywhere) should show either (non-user) title, or subtitle, or both.
• Offline articles (using service workers or some such).

[doshi-kevin]

Hey, is this issue still open and if yes could you assign it to me . I may not implement all the features mentioned but I can surely add a few.

[lemon24]

Hi, as mentioned in the overview, most of these issues will be easier to fix by/during a ground-up redesign, which sadly I do not have enough time for at the moment.

If you are interested in implementing a specific feature before then, feel free to reopen one of the closed issues, or create one if needed.

(I also feel I should warn that the web app code base is very messy / untested compared to the library.)