Live data from Hacker News

Houndify: Add voice enabled, conversational interface to anything

houndify.com

51–53 of 53 posts

Re: Houndify: Add voice enabled, conversational interface to anything

#51
post #4

This looks extremely cool and I can't wait to try it. Bug: When scrolling down the page it is very very sluggish, using Chrome on Xubuntu 15.04.

I'm one of the developers behind Houndify. Thanks for this feedback, I'll look into it.

Just a follow up, it's fine until I click on the examples.

Re: Houndify: Add voice enabled, conversational interface to anything

#52
post #4

This looks extremely cool and I can't wait to try it. Bug: When scrolling down the page it is very very sluggish, using Chrome on Xubuntu 15.04.

I'm one of the developers behind Houndify. Thanks for this feedback, I'll look into it.

Really impressive work. Would love to play with the beta cough invite cough ;-) Looking forward to seeing this being used on some inclusive design projects.

Re: Houndify: Add voice enabled, conversational interface to anything

#53

It's already really easy to get fast, efficient access to large data sets. I don't see much value in that. It is not fast,efficient, and easy to transform natural language queries into computationally actionable ones. I would find more value as a developer if, when given a natural language query, it returned a structured query. Then I could tweak the query to conform to whatever data retrieval API I wanted. I don't t…

I am one of the developers for houndify.com, so I can answer this question for you! We actually have an api endpoint dedicated to doing this for you. At the moment we have a concept of "domains" where developers use a proprietary language to help Hound understand topics. Using our api, you could technically do this yourself, and add functionality that doesn't currently exist on the platform. You could use the hotel d…

Q1: So a domain developer gets to determine what is returned to from the API for all calls matched to that domain?

Q2: As a domain developer, where does the query-able content reside?

Post reply on HN