Suggestion 1
As of today, if you fall behind on your reading schedule, you have the option to read over everything today, or to "catch-up," which means ignore the readings you missed and simply read today's reading.
My suggestion is for Logos to implement a smarter catch-up algorithm. This algorithm would consider the readings that have been marked as finished as such, but the ones that haven't to be calculated forward. Meaning, if you have read 20 pages and have 20 pages to go, and at a pace of a page a day you missed 10 days, you'd need to read 2 pages a day from now on in order to "catch up" and finish by the end date you decided upon.
Even better would be to be able to catch up within the next week or so for longer plans, meaning you'd read 5-10 more verses a day for a week, or 3-4 more pages a day for a period of time, in order to "catch-up" with your reading and get back to your normal schedule.
Suggestion 2
My second suggestion is for a more tailored approach to reading plans. For instance, while Thursdays are pretty busy for me, Sundays are very relaxed. So while I can read 30 pages a day every day, I can only read 10 pages on Thursday, but can read up to 50 pages on Sunday. So in this case, the user would be able to input what days are regular (1x), "heavier" (perhaps counting 1.2-1.9x the regular reading), and lighter reading (say 0.2-0.9x). In theory this is not hard to design, but I am not sure about the particulars of Logos' database.
_____
Would love to read your thoughts on this.
