WIP on 'austin' branch. Right now, it pulls the last updates in 24 hours, and then matches against the library, and sends a notification for all chapters.
Considerations/TODO:
[x] Figure out background cycling details
[x] Skip cache, always use newest data
[x] Include updated chapter number in notification
[x] Allow user to disable
[x] Don't alert if user already read latest (i.e. Naruto updates from ch. 700 to 701, and user already read 701)
[ ] Check for updates on wifi only
Probably not implementing:
[ ] Allow user setting for update frequency?
[ ] Play with notification copy text? e.g. "3 new chapters available", "
[ ] What happens if multiple updates happen at once?
[ ] Don't alert if user isn't caught up (i.e. Naruto updates from ch. 700 to 701, but user is on 650)
WIP on 'austin' branch. Right now, it pulls the last updates in 24 hours, and then matches against the library, and sends a notification for all chapters.
Considerations/TODO:
Probably not implementing: