This is a really good point. Allowing other browsers (rather than just reskins of Safaris internals) would solve a lot of the issues. They would need access to a large number of iOS APIs that aren’t typically available to native apps. The majority of end users assume iOS allows multiple browsers simply because they can install something called Chrome or Edge.

This is a good example of a general communication issue, specific technical reasons of why Apple chooses not to implement major features (or prioritize them for development) is something that we all want. A roadmap for each Safari release similar to chrome's https://www.chromestatus.com/features which includes ALL proposed features with the current status, links to discussion with indications of priority, scheduling dates and if Apple does not want to develop a specific feature a link to a technical discussion should be included.

Web Share 2 with files may have been implemented in iOS 15 https://bugs.webkit.org/show_bug.cgi?id=198606

The reason I suspect that notifications for iOS is being held back and that no-one on the Safari team has thus far talked about it publicly is that a significant number of Apps could then operate outside of the AppStore. iOS notifications have been requested every year for the past 12 years and there hasn’t been any response. Communication is the problem that we have, but it maybe anti-competitive business goals that sit behind that.

This of course is problematic as your getting blocked for releasing an App for core functionality that should already exist. Obviously your provides lots of functionality for some users.

While we’re at it, edit functionality here to fix mistakes would be nice :)