-
-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Community Feedback Request: Rich content response objects #21
Comments
I'd actually be tempted to send HTML snippets to the client, it's much more lightweight and most things support HTML rendering. |
Thinking in terms of iOS or Android clients, or say an embedded device with a small screen, the latency pulling in all of the css and js dependencies to render might hold up the show significantly, however its worth testing rendering it in a webview and seeing how long it takes. |
I was thinking simpler than I think you're planning. HTML more along the lines of |
@patrickjquinn I'm leaning more towards using images now. I think that might be the best approach. When responding currently there's: {
text:"response text",
url:"http://example.com",
silent: true
} With URL and silent being optional. Maybe we should add an optional image tag to responses? |
Hi Guys,
So i've been giving some thought to the best way to return 'rich content' such as weather cards, news etc and have come up with a partial solution that I would like your feedback on.
Basically, we generate a html card with the weather forecast say on the server (for example in the weather skill), then render that to a canvas and finally a png file and rend that along with the response. That way we can have rich responses that can rendered on any client, be that web or native, by simply rendering the image.
Does anyone have any feedback on this?
The text was updated successfully, but these errors were encountered: