I’m honestly not sure what the problem was. I’d intended to try the pattern elsewhere — either within the same app or in a different app — but I haven’t gotten around to it yet.

As I recall, I don’t think optionals would have entirely supplanted the null object pattern in my case; there was still some inherited functionality that needed to be there even if the “null object” instance was in use (although maybe that technically violates the pattern itself).