[kazinator]

I've hardly missed a day since starting AnkiDroid some four or five years ago? The reviews have dwindled down to single digits per day in all decks where I do not add new material.

(I don't use the desktop Anki, by the way; I used it briefly for doing some editing on decks.)

Tha said, AnkiDroid could use a vacation feature. How vacation mode could work would be simply by rescheduling all cards, delaying them by the vacation amount (14 days or whatever). Thus, no cards are due for the next 14 days, and on day 15, the same cards are due that would have been due day 1 (no "snowplow" accumulation). It would probably help if the app generated a notification a day before vacation ends.

It's incredible that neither the author of the original Anki, nor the authors of the AnkiDroid clone, recognize the value of a vacation.

[simbyotic]

Not what you have in mind, but you can use the Load Balanced Scheduler to ease the pain of missing a few days: https://ankiweb.net/shared/info/208879074

But the vacation idea is great, I'm sure someone could make an add-on to implement it.

[kazinator]

The vacation idea needs to be in the core application.

A simple toggle: "pause Anki". Here are my requirements:

- in the paused state, the review UI is entirely disabled. You cannot review anything.

- when you toggle out of the paused state, Anki calculates the number of days since the pause, and delays all cards in all decks by that many days.

- pausing and resuming on the same day has no effect since the days delta is zero; the UI just becomes enabled.

- For the purposes of the delta calculation, a day is the study day (e.g. 7 a.m to 7 a.m), not the midnight-to-midnight calendar day. If you pause at 11:45 p.m. and resume at 1:15 a.m., that's a no-op since that's the same study day.

- since resuming is potentially a time-consuming operation that destructively manipulates the database, unpausing comes with some yes/cancel prompt, except in the no-op case.

[simbyotic]

There's a lot of things that should be in the core app but aren't I'm afraid.

I've started to think of it like node: A slim core with an expansive userland in the form of add-ons.