> It installs, opening it is a simple message saying I need to enable it in Safari settings. Strange, but ok.

I’ve made several Safari extensions for iOS, and they all have to do this.

Apple provides no API for an app to enable its own Safari extension. It also has no public API on iOS to deeplink to the Settings page for enabling the extension. You just have to tell users where to go and hope they don’t get lost.

(There is an API on macOS to quickly open Safari extension settings. It’s nice! Maybe they’ll add it to iOS someday.)

▲

MortyWaves 8 days ago | parent [-]

Does an app for that even need to exist? Why can’t extensions be a standalone thing in the store?

	▲	duskwuff 8 days ago \| parent \| next [-]
		> Why can’t extensions be a standalone thing in the store? 1) Because then you need a whole parallel set of processes for configuring, updating, and uninstalling those things, distinct from the existing processes for apps. And you need to make that process accessible to users who may be used to everything being an app. 2) A nontrivial number of browser extensions on iOS are part of standalone apps anyway, like password managers or bookmarking tools. It'd be very strange to have both app-with-browser-extensions and browser-only-extensions, or to require some extensions to be installed and updated in tandem with a companion app for expected functionality.
	▲	saagarjha 8 days ago \| parent \| prev [-]
		Because Apple's distribution model centers around everything being bundled as an app