Day 35. The questions I asked on here, and what they changed. @boringdev77 answered the first one on Aug 24 and named LinkedIn: every notification arrives, none of them are for anything that could not have waited a week. That is a notification nobody taps and nobody swipes away, which a tap-versus-dismiss ratio cannot score at all. It is the reason silence counts in Doorman. A row nobody touches becomes an answer once it is old enough. LinkedIn got measured and the number went under his comment: 50.0 percent, 18 arrived, 12 got a decision, 6 opened. @ThorCommerce asked for a reboot test with notifications already queued, on the grounds that held rows survive a reboot but the alarm has to be registered again. Answering that put a claim from the code into public: that Doorman declares no boot permission. Checked against the installed build on Sep 18, that was wrong. The push SDK merges RECEIVE_BOOT_COMPLETED in. The comments that said otherwise are corrected, and the reboot check goes into the device test script. @BestAppAwards asked how Restore looks to someone who already paid. It has three outcomes and three different sentences. Found, and the Doorman is switched back on. Nothing on the account, which points at the Play account, since paying from a second Google account is the usual reason. Play unreachable, which says nothing has changed. A network error must never read as you never paid. Thanks to the three of you. The rest of the asking produced nothing, which is also worth saying. Whether you would publish your own notification numbers: zero replies on 29 views. Which apps should never be held: zero on 15. The never-held list got built from categories and system roles instead, and that question is still open. #BuildInPublic