No, it's "hard", because it requires an extension to monitor all requests to a different search enging and hijack those to perform a redirect.

This is a clever workaround by Kagi, but a glaring hole in the Safari extension API surface area.

I think there might be more to it. While it might just be me, I think Kagi could use some improvement here. I've been using Kagi with Safari on Mac for about a year, and never got the search extension to work consistently. It would sometimes give me Google, and sometimes Kagi. And sometimes it would give me one site then switch to the other after a several second delay.

Eventually I gave up and uninstalled their extension. I switched to using StopTheMadness to do the redirects instead, and am having much better luck. I did switch from redirecting Google to redirecting Ecosia at the same time, and this might be the difference, and while I'd fully agree that Safari doesn't make it easy, but I think the base problem is that their browser extension just doesn't work that well.

(If you are familiar with both, you will understand that switching _to_ StopTheMadness for a better interface is pretty high in irony!)

Hmm, fair enough. Do you think there is something Kagi could do to make this easier?

I don't know the details well enough to pinpoint the problem, but the fact that StopTheMadness is able to redirect consistently and the Kagi extension wasn't makes me think there is something they could fix to make it work better.

I have been a software engineer for almost two decades and it's taken me three tries at reading and rereading the instruction on how to set Kagi as default search on iOS, because I missed the fact that I had to allow permission to use the extension WHILE browsing google.com for it to work, as it has to intercept the query to rewrite the URL.

When all it should've been is a "custom search engine" option like Firefox does.

Calling it "unobvious" is PR newspeak for jumping through the hoops to set up a Rube Goldberg machine to do a basic search.

> I missed the fact that I had to allow permission to use the extension WHILE browsing google.com for it to work

There was a period of time when they had two apps, and I agree the old one was stupidly complicated. The new one, Kagi for Search, doesn't require this.

Like, should Apple have an open API for routing searches? Maybe. Would that get abused? Probably. Do I think Kagi should be on Apple's list? Yes. Does prioritising a 50,000-user engine into iOS's defaults create other issues? Yes as well.

I installed Kagi for Search not even a week ago, so I guess the new app is just too advanced for someone like me.

How Apple haven't already lost a massive anti-trust case is beyond me.

I've also found that the extension configuration isn't very durable. I wound up having to re-do the arcane setup process semi-annually on each device or my searches would 403. Eventually just gave up. Brave search seems to work just as well.

If I were setting up Kagi just for my self that’s probably true. But the thing preventing me from paying for Kagi is I’d want it for my household. Setting it up and supporting it on all the devices was enough for me to take a pass.