Support read/unread state tracking #12

Open
josharian opened this Issue Mar 20, 2012 · 4 comments

Comments

Projects
None yet
2 participants
Collaborator

josharian commented Mar 20, 2012

No description provided.

Collaborator

josharian commented May 28, 2013

UI questions to consider:

  • Displaying state. Maybe a nice blue dot for unread?
  • Mark as (un)read. Maybe a left or right swipe, a la Reeder?
  • Mark all as (un)read. Maybe not supported, maybe support through edit menu (like download/delete all).
  • Initial state. Suggestion: All currently downloaded comics be marked as read.
  • Is this surfaced in the search interface? (I.e. can you search only read/unread comics?) Probably not?
Collaborator

josharian commented May 28, 2013

Also: How will it interact with #4 (starred/favorited comics)?

Owner

paulrehkugler commented May 28, 2013

It's reasonable to assume that starred/favorites will already have been read, i.e. the ui could reserve space for these (mutually exclusive): empty space (i.e. left padding), an unread dot, or a 'favorite' star.

Collaborator

josharian commented May 28, 2013

the ui could reserve space for these (mutually exclusive): empty space (i.e. left padding), an unread dot, or a 'favorite' star.

Works for me. Presumably the backend would store them independently, and then there'd be some kind of trumping -- e.g. stars trump unread -- with the assumption that those collisions will be very rare.

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