Kagi assistant is unusable on my iphone se3

Lees

Kagi clearly has some significant css issues on iphone SE3 running ios 16.1.1
. The settings page on the phone is unusable, and this is a longstanding unresolved ticket item on this forum.

Today i signed up for the ultimate plan and was dismayed to find that the css is completely broken on my phone. I can’t click anywhere, there are fixed elements with a z index above the inputs, it is a mess. See screen shot. There is no way for me to actually enter a query due to the formatting issues

I expected that the kagi assistant would work on a mobile phone.

Moreover, i expected that the css for the website in general would be light and compatible, and that the un-resolved issue pertaining to the settings screen (which is presumably due to a related issue with formatting as the assistant bug) would be fixed

marcel001122

Have you tried both the web and Kagi app? I going Kagi app better for assistant than web.

laiz

Hey,
I am sorry to hear you are facing issues with the Assistant on an older operating system. This was discussed at length for desktop #4726 but a similar discussion has not, to my knowledge, taken place for mobile operating systems.

First, I must point out the fact that iOS 16.1.1 is over two years out-of-date at the time of writing this message. iOS updates come with new WebKit features, some of which are leveraged by Kagi in their Assistant. I understand some users have niche uses which require sticking to an older version of an operating system. However, at which point is it still reasonable to expect their configuration to be fully supported by services, especially when iPhone SE 3 is still receiving new updates?

Regarding #4096, I know @georgee reopened the ticket following a long-awaited request of a video of the issue being posted. I'd expect it to be worked on after the holidays. I don't know if this bug report will enjoy similar priority for the reasons listed above.

Lees

Thank you for the quick reply!

I take your point, and as you suggest, updating the OS is by far the quickest solution for me. And i understand that for a startup, building new features quickly may be a priority over developing robust support for older software.

However, I strongly disagree with the timeframe you suggest about support for older versions. Yes, there is a point where support for older versions should wane, but it is absolutely not at 2 years. Let me put it a different way: this is the only mainstream web product I have ever used which breaks due to my phone operating system being just two years out of date.

Way back when I used to do web development there was a debate in designing for older systems between “progressive enhancement” and “graceful degradation”. The kagi assistant client is neither: the website is clearly just not designed for users with software that is more than two years out of date.

Considering Kagi has a small web initiative, surely there is some degree of empathy for the fact that there may be a subset of users with anachronistic sensibilities.

Besides that, there is simply no technical excuse for a client-side web app communicating with an LLM API to require the absolute newest browser features or css support. There is nothing about the assistant’s client side that should preclude it from working on a device or operating system that is 12 years out of date. I acknowledge the irony of wanting to use a modern technology with an older browser; but the truth is that the client’s browser is not the technical bottleneck.

At the end of the day, it’s your choice whether or not to support my current hardware and software setup, but i don’t think it is asking too much for the client-side website to support operating systems that are more than 2 years put of date.