Add a mobile Kagi app with quick search widget for Apple and Android
That "coming soon" tag is one of the best pieces of news I've received today
Can anyone from the Kagi team confirm if the plan is to apply to Google's DMA Search Choice Screen, so we can get this as a search option in Pixel phones in Europe? I assume it may not be possible to apply before the app is actually published in the Play Store, but I'd be eager to know what your plans are.
Thanks!
I hope that a day we will have Orion browser on Android too,an assistant which can let us ask with voice any prompt.
Please, Kagi team
I personally would also like a 1x1 widget that just starts the assistant maybe even with voice recog immediately (something that could be set in the settings)
- Edited
VMX Yes, we definitely want to apply to Google's DMA Search Choice Screen. But we'll need 5000 app installs to be eligible. Please install and share it with your network and help us meet that criteria
https://play.google.com/store/apps/details?id=com.kagi.search
FYI - we'll announce the official release of the Kagi Android app with our changelog today.
Thibaultmol this is planned
Little feedback on the app:
The login fields doesn't prompt for password managers:
- Edited
Love the new app! Would be great if the keyboard was open when the search window open from the widget. See screen recording here: https://photos.app.goo.gl/GqezzSEnjQEKjh7W9
Have to click the field to open the keyboard.
In the European Union, users can choose their search engine on the Pixel Launcher (Google Pixel phone) and use something else than Google.
We can choose in a list of installed search engines, however Kagi is not listed here even if the Kagi Android app is installed.
See: https://www.android.com/choicescreen/dma/searchengine/
- The Kagi app is installed
- On the Pixel Launcher, long press the search bar, settings
- Kagi should appear in the list of search engines
kadir I don't recall, but I believe my password manager (https://github.com/PhilippC/keepass2android) refused to automatically attempt to fill because it detected the origin as null (an origin I've never seen before).
For example, for logins that are just a web page, the origin is the domain of the web page. For apps that do native logins, the origin is the app id.
That said, I can't reproduce with the latest release of my password manager/kagi - so maybe something was fixed on one of the sides?