Some mobile browsers appear to now ignore a URL like address, if no schema is explicitly specified (e.g. https://). In these cases, the browser attempts to search using the default search engine. Google typically prioritizes a result containing the URL, but Kagi does not - increasing user friction (typing schemas is always annoying on mobile).
Ideally, Kagi would, through a result or a "quick answer", provide a link to the "likely-URL" query.
So, for example, I needed to link a Plex account to a TV. I was prompted to navigate to plex.tv/link (which Kagi auto-completed). When entering this into the address bar, the browser (Firefox in this case), attempted to search for plex.tv/link using Kagi. Kagi did not return any results for plex.tv/link, but rather, results for plex.tv.
Maybe the UI would look something like this:
