Feedback on the new Quick Answer experience

Thibaultmol

marc-eu what do you not like about the current experience on desktop?

kvnmlm

fxgn no it is not on my desktop. it gets worse regularly.

fxgn

kvnmlm I just tried it on desktop and it's exactly the same it's been for the past 2 years before the redesign

kvnmlm

fxgn At this very moment on desktop I get completely different stuff from a few weeks ago:

Text which says continue in assistant which does nothing cause no longer a link, I occasionally used previously but now it does nothing, likely cause of the junk which follows.
3 questions to help me query back. Save these for my grandmother, this is burning real estate on my page. I don't need prompt help. I'll go further, if you are savvy enough to use Kagi, you don't need prompt help ever. And as always Kagi could all all this junk as opt in settings so I never have to visit this forum EVER.
A big dialog box for me to put more text into. If I haven't decided I need to continue an assistant discussion this is more wasted screen real estate. Get rid of this junk unless I"ve indicated I want to continue in assistant beyond my quick answer.

I'll stop but the changes just before all this junk to the links attached to the output suck bad too. I am now realizing that I'm at the bottom of a thread for mobile grumbling about desktop. Apologies. I know I need to move on but I loved this thing until they started "improving" it.

jibbitt

Thanks for fixing this - it is much better now reverted.

I was slightly surprised to see the actual citation links from the summary in the collapsed 'view more' section but, on reflection, I think this works quite well - especially considering you get the little tooltip-style links that appear if you tap the inline footnote number.

The 'view more' expansion also seems to solve multiple problems. It still includes the follow-up questions and chat input, but in a non-intrusive way. If I want to dig deeper into my search I can, but it's inconspicuous when I'm using it for literal quick answers. If I do want to expand my AI usage on a specific question, it's all right there.

I think you have done a good job with this revert (and compromise), and it is very encouraging to see you listening to feedback.

I think people are sick of having 'AI' thrust upon them in general, but most people find LLMs useful to different extents for varying purposes. As long as you continue to give users options in this respect (and let them completely ignore it if they want) I think people will mostly be happy.

Luis

kvnmlm 1. was an oversight, it will be made clickable in the next release.

Regarding 2. and 3. the "Continue in Assistant" option is already positioned at the bottom of the Quick Answer once expanded. On desktop, you can use q to expand or collapse the Quick Answer, and this preference is saved for your next searches.
If a user wants to continue exploring their query in the Assistant, it's unclear how requiring an extra click to expand that section in the Quick Answer adds value. Do I understand correctly that the follow-up questions and the prompt box are not useful to you?

kvnmlm

Luis Oversite ? wow, testing is lacking just a wee bit I'd say.

On my desktop, a q to expand or collapse does nothing. I really wish it did. What you describe sounds useful cause if this is all hidden I'd be much happier. Just start using "opt-in". Stop messing with results and we are not in this mess. Feature creep in search and ads are why we are Kagi customers.

I liked the single click to move on to continue my discussion with the most of the time wrong assistant. If it works I NEVER have to click and expand. I'd like to see this over helping it take a second shot. It generally doesn't work so sometimes I want to click and go further. I don't need Kagi's assistance with next queries. My grandmother might like it but she doesn't use Kagi.

So, give me results as you have to date. Stop assuming I want all this added junk. If you see a serious need for these extra things make them opt in. It is bad enough I can't turn on always try quick answer first and half to type in a question mark every time I query.

Koolkat

Thanks for listening to feedback and reverting 🙂 . Works great.

Thibaultmol

kvnmlm testing is lacking just a wee bit I'd say.

I helped test things, just assumed it wasn't supposed to be link ... just a header... didn't see it as a bug.
About the q keyboard shortcut: I think it does work on some systems/browsers but doesn't for me either, we'll get this fixed.

I would suggest you make a seperate kagifeedback about the ability to turn off certain parts of the search ui (like the follow up questions and such). (this way we'll be able to follow up better).
These new features aren't junk to most people, but I understand if you don't want it, so feel free to make it a seperate post so we can properly track that request.

kvnmlm

Thibaultmol "I assume..." like I said this isn't professional testing. Basic automated regression testing would have flagged this defect with zero human opportunity for failure and experienced tester would know the product, its key features (like in every result 18 zillion times a day) AND specific changes made in the release they are testing. So disappointed.

"I would suggest you make a seperate kagifeedback about the ability to turn off certain parts of the search ui (like the follow up questions and such). (this way we'll be able to follow up better)." - Not my job, I'm a customer. It is Kagi's job to do this not mine. Disappointed again. The fact we are here shredding the changes is a gift to you. You or someone needs to comb this treasure trove of information in these threads and make the product better. If I couldn't track the defects and improvements in my own software product.....I'd be soon looking for work.

I pay for better than this.

Last thought, you are here and reading users inputs. THIS is greatly appreciated.

Koolkat

Luis the follow up question text entry box on quick answers, doesn't work after pressing enter, on the new implementation, it brings up an error on the assistant page.

Luis

Koolkat I can't reproduce, what browser are you using?

Koolkat

Luis works perfect in edge. In firefox I'm experiencing the issue, the url below

Kagi.com/assistant/null?q=hello world&profile=ki_quivk.

Works there too.

Edit: It's if there's an ampersand & in my original query, surprisingly

Luis

Koolkat could reproduce, thank you for the help!

fxgn

kvnmlm Basic automated regression testing would have flagged this defect

How is automated regression testing supposed to work when completely redesigning a part of the frontend? Old tests related to that part will be completely inapplicable either way

Koolkat

kvnmlm that's a bit unfair/dramatic. You gave feedback they listened. The end.

kvnmlm

fxgn Same code, moved around needs the same test. If you shit can the full set of regression tests (which no one does cause they are painful to create), you create a set which matches the new redesign. Either way, it gets covered. It did not. The line is identical, it is a link to a URL, the test is trivial and identical. No one is paying attention. This kind of mistake does not slip through mature software organizations. It should never have gotten past review without the test to go with it. A test set for the result page is pretty easy and even easier if you don't keep adding stuff to the page. Either way, you don't ship shit you don't test. Period.

InternetChunk

I want to be able to turn it off in the settings - I don’t want to see it

kvnmlm

Koolkat funny. i just replied to someone indicating because there was a redesign you can't use the same test. this is incorrect AND I did add they are not testing what they are shipping. not dramatic. statement of fact. if you work in software you don't ship or even integrate code you haven't tested. software 101.

Luis

Hey all, thank you for your feedback and reports. This thread has been very useful and has now served its purpose. Going forward, please contine sharing any new feedback in a new thread. Thanks! 🙏

« Previous Page