I understand that Apple doesn’t really make this very clear to general users, but iOS and macOS remain very different ecosystems. macOS still has the much fuller frameworks. If you have a fairly simple app (not necessarily in terms of the underlying code base but in terms of how a user interacts with it, such as, for example, Maps) it is entirely possible to have near parity across platforms. In other areas, this isn’t possible. The TextKit, on which Scrivener relies, is far more basic on iOS and does not have access to a lot of the more complex things that Scrivener on macOS does. Also, iOS has no “outline view”, which is what Scrivener uses for the binder and outliner on macOS. On iOS you have to take an entirely different approach for that sort of thing, in large part because of the touch interface. And of course, the existence of a menu bar on macOS makes it possible to add a whole bunch of niche features that don’t need icons anywhere.
That’s not to say that Scrivener for iOS isn’t overdue an update in certain areas; it is.
I certainly haven’t been resting on my laurels, but it’s become more difficult than ever to talk about future plans. With Windows v3 still not ready, we can’t talk about future plans for macOS or iOS without upsetting Windows users. And with Apple users torn between wanting something simpler and iCloud-supporting or maintaining all of the existing features (mutually exclusive options), we’re sure to upset a bunch of users no matter what route we take. But just because there won’t be any major announcements or releases related to iOS or macOS this year doesn’t mean I have my feet up!