<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aza Tulepbergenov on Medium]]></title>
        <description><![CDATA[Stories by Aza Tulepbergenov on Medium]]></description>
        <link>https://medium.com/@azatulep?source=rss-627020b59957------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*1KEidqvvc5e6gt_e.jpg</url>
            <title>Stories by Aza Tulepbergenov on Medium</title>
            <link>https://medium.com/@azatulep?source=rss-627020b59957------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 04:18:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@azatulep/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Catch errors earlier in development with the new Actions on Google linter]]></title>
            <link>https://medium.com/google-developers/catch-errors-earlier-in-development-with-the-new-actions-on-google-linter-acd04c526ad1?source=rss-627020b59957------2</link>
            <guid isPermaLink="false">https://medium.com/p/acd04c526ad1</guid>
            <category><![CDATA[actions-on-google]]></category>
            <category><![CDATA[google-assistant]]></category>
            <category><![CDATA[eslint]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Aza Tulepbergenov]]></dc:creator>
            <pubDate>Tue, 16 Jul 2019 20:46:10 GMT</pubDate>
            <atom:updated>2019-07-16T20:46:10.092Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, we’re launching the Actions on Google linter for Node.js. The linter performs compile-time checks and alerts you when a webhook builds a response that doesn’t follow the <a href="https://developers.google.com/actions/assistant/responses">documented requirements</a>. Those include having too many chat bubbles (text responses), or lacking a response. This saves you time during development by ensuring that your code adheres to response building requirements — without needing to deploy and test your webhook.</p><p><strong>Why use a linter?</strong></p><p>As my colleague Leon mentioned in “<a href="https://medium.com/google-developers/debugging-common-actions-on-google-errors-7c8527378d27">Debugging Common Actions on Google Errors</a>”, errors like</p><pre>“MalformedResponse: &lt;error details&gt;” </pre><p>can come up frequently during testing.</p><p>Consider this code that implements a simple intent handler:</p><pre>app.intent(‘my_intent’, (conv) =&gt; {</pre><pre>  conv.ask(‘first chat bubble’);</pre><pre>  conv.ask(‘second chat bubble’);</pre><pre>  conv.ask(‘third chat bubble’);</pre><pre>});</pre><p>It produces the following MalformedResponse error when a user triggers <em>my_intent</em>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oDjRoO6Vhww_3ih-" /></figure><p>The simulator returns this error because there are three chat bubbles in the webhook response. Per the <a href="https://developers.google.com/actions/assistant/responses#simple_response">documented requirements</a>, this constitutes a malformed response.</p><p>In general, I’d like to point out two things:</p><ol><li>Malformed response errors are common</li><li>They are raised at runtime</li></ol><p>Malformed response errors arise when responses don’t follow the requirements listed in the Actions on Google <a href="https://developers.google.com/actions/assistant/responses">Responses documentation</a>. The documentation lists the specifications for various types of responses (like Rich Response, Visual Selection Response, and more). As conversations get more complex, it becomes more likely to overlook a MalformedResponse error.</p><p>To help automate this process, you can use the Actions on Google <a href="https://www.npmjs.com/package/eslint-plugin-actions-on-google">linter</a>. The linter scans your code for missed requirements based on the Responses documentation. This allows you to catch issues with your webhook before deployment. You can find a full list of support rules in <a href="https://github.com/actions-on-google/actions-on-google-linter-nodejs#supported-rules">actions-on-google-linter-nodejs</a> on GitHub.</p><p>The linter is currently implemented as an <a href="https://eslint.org/docs/developer-guide/working-with-plugins">ESLint plugin</a> for Node.js developers, providing you with a familiar and consistent environment. It follows the standard patterns and architecture established in the ESLint community.</p><p>The linter produces the following output when checked against the code for <em>my_intent</em>:</p><pre>$ ./node_modules/eslint/bin/eslint.js .</pre><pre>4:3 error At most two simple responses are allowed actions-on-google/at-most-two-simple-responses</pre><p>The linter gives us both the error and the line number of the failing code.</p><p><strong>Distribution and installation</strong></p><p>The linter is distributed via <a href="https://www.npmjs.com/package/eslint-plugin-actions-on-google">npm</a> and the source code is available on <a href="https://github.com/actions-on-google/actions-on-google-linter-nodejs">GitHub</a>. You can read through the <a href="https://github.com/actions-on-google/actions-on-google-linter-nodejs#installation">installation instructions</a> for how to set it up in your project. I encourage you to try the linter in your projects and submit pull requests to improve the rule coverage of the linter.</p><p><strong>Linter details</strong></p><p>Each rule works with an abstract syntax tree (<a href="https://en.wikipedia.org/wiki/Abstract_syntax_tree">AST</a>) created by Espree, the default ESLint parser.</p><p>This tool processes the AST and identifies places where you make Actions on Google Node.js client library calls that correspond to building responses. Such nodes are roots of subtrees containing enough information to spot violations. Violations include which types of responses and in which order are being built.</p><p>To simplify the process of parsing client library calls, we also developed abstract functions that classify simple responses, helpers, and client library calls. Those functions are reused by the rules, and make it easier to create your own rules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OtXdKcw6J-lnhFMsfQ0HGQ.png" /></figure><p><em>Thanks for reading! To share your thoughts or questions, join us on Reddit at </em><a href="https://www.reddit.com/r/GoogleAssistantDev/"><em>r/GoogleAssistantDev</em></a><em>.</em></p><p><em>Follow </em><a href="https://twitter.com/ActionsOnGoogle"><em>@ActionsOnGoogle</em></a><em> on Twitter for more of our team’s updates, and tweet using #AoGDevs to share what your working on. Can’t wait to see what you build!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acd04c526ad1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-developers/catch-errors-earlier-in-development-with-the-new-actions-on-google-linter-acd04c526ad1">Catch errors earlier in development with the new Actions on Google linter</a> was originally published in <a href="https://medium.com/google-developers">Google Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Actions on Google: I/O recap]]></title>
            <link>https://medium.com/@azatulep/actions-on-google-i-o-recap-1f05b75286f2?source=rss-627020b59957------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f05b75286f2</guid>
            <category><![CDATA[actions-on-google]]></category>
            <dc:creator><![CDATA[Aza Tulepbergenov]]></dc:creator>
            <pubDate>Mon, 05 Jun 2017 21:43:11 GMT</pubDate>
            <atom:updated>2017-06-05T21:43:11.194Z</atom:updated>
            <content:encoded><![CDATA[<p>Google I/O took place 2 weeks ago. It was packed with developers, <a href="https://greenido.wordpress.com/2017/05/03/google-assistant-talks-at-io-2017/">sessions</a>, announcements and good weather at Shoreline Amphitheatre. Backtracking one week from I/O, I was celebrating my first day as an intern at Google.</p><p>Joining Google Developer Relations, one week before I/O was like hopping onto a supersonic train. Everything was moving fast, and I could feel the excitement among Dev Rel folks who also enjoyed the ride. I first attended I/O last year as a GDG organizer. Being behind the scenes will definitely be one of the highlights of my internship; I got to see the amount of effort and commitment for excellence that goes into putting event of such magnitude.</p><p>At I/O 2017, one of my favorite announcements was centered around the Google Assistant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/0*ZJgNFEdquE89Dlg7." /></figure><p>We announced that Actions on Google are now extended to mobile devices (iOS and Android). This means you can reach a much larger user base and engage them in new ways. For more information, please check <a href="https://developers.google.com/actions/">actions.google.com</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*H4ZRIO_EmS7X_kHXE8tFrA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*HccxlU2BFvob3Dn5tYPGjA.png" /></figure><p>We’re also excited to have released:</p><ul><li><strong>Rich responses on surface-enabled devices</strong></li></ul><p>Engage user with cards, lists, carousels and suggestions on screen-enabled devices</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*m5WArRIDUbfD4s7MeTbgtQ.png" /></figure><ul><li><strong>Support for transactions</strong></li></ul><p>Assistant apps now allow starting and completing purchases</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*_Tnymuw-5uk3yKZA6tp9Fg.jpeg" /></figure><ul><li><strong>Actions on Google console</strong></li></ul><p>Centralized location where you can monitor and test all of your Assistant apps</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*T2iln4pJ2kyd0MpE." /></figure><p>It’s going to be interesting to see what new applications you will build for this emerging platform. If you wish to learn with code, please check the two codelabs that <a href="https://medium.com/@greenido">Ido Green</a> wrote:</p><ol><li><a href="https://codelabs.developers.google.com/codelabs/your-first-kids-action-on-google/index.html?index=..%2F..%2Findex#0">Animal jokes</a> — This is a 101 codelab that shows you how to work with api.ai and create a nice bot that tell you funny animal jokes. If you want to get the source code — It’s all in this <a href="https://github.com/greenido/animal-joker">Animal joker repo.</a></li><li><a href="https://codelabs.developers.google.com/codelabs/your-first-action-on-google-with-webhook/index.html?index=..%2F..%2Findex#0">Your First App for Assistant With Webhook — Bitcoin Info</a> — This codelab is taking you to the next stage, with the ability to call your server (and logic) using a webhook.</li><li>You can also copy the agent and the webhook code from this <a href="https://github.com/greenido/bitcoin-info-action">bitcoin-info repo</a></li></ol><p>Additionally, you can watch our step-by-step<a href="https://www.youtube.com/watch?v=ZvyrvowZ4wQ"> video tutorial </a>about how to build your app for the Assistant.</p><p>Also, watch the recording of all Actions on Google sessions from I/O 17:</p><p><strong>VUI:</strong></p><ul><li><a href="https://www.youtube.com/watch?v=0PmWruLLUoE">Finding the Right Voice Interactions for your App</a></li></ul><p>Imagine trying to read a website through a straw… mentally processing an audio signal feels a lot like that. In our new era of computing where advancements in conversational UIs and artificial intelligence are enabling users in new ways, it’s easy to be tempted to take an existing visual-based app or GUI and simply “convert it to voice”. But while voice brings with it the potential for speed and simplicity, hands-free experiences can become overly complicated easily when based on another mode of interaction. Get the scoop on what types of use cases transfer well to voice interactions and why.</p><ul><li><a href="https://www.youtube.com/watch?v=oOLo071Pj1U">In Conversation, There Are No Errors</a></li></ul><p>When building a Conversation Action for the Google Assistant, consider that so-called “error events”” don’t have to be treated as edge cases. Instead, these can become opportunities to forge meaningful exchanges that leverage users’ mental models of how everyday conversations unfold. This talk will frame a new way of approaching fallback and repair, in which so-called errors become organic turns in the dialog. We will provide design tips for your action logic to allow the conversation to move forward naturally.</p><ul><li><a href="https://www.youtube.com/watch?v=pz8EQHMRr6Y">PullString: Storytelling in the Age of Conversational Interfaces</a></li></ul><p>While the medium may change, the story remains the key element in engaging audiences. Come learn from the storytelling masters at PullString how they apply the learnings from over a decade working at Pixar to the new medium of conversational interfaces.</p><ul><li><a href="https://www.youtube.com/watch?v=wuDP_eygsvs">Applying Built-in Hacks of Conversation to Your Voice UI</a></li></ul><p>As you gear up to build great Conversation Actions for the Google Assistant, find out how to leverage one of the principles that practically defines what it means to be “conversational” — our ability to take mental leaps, to draw inferences, to be informative, to feel like we’re making progress. Conversation is systematic, but to the surprise of many technologists, this conversational principle actually defies the rules of formal logic. So come find out the non-literal truth of everyday back-and-forths; take advantage of this principled, built-in “hack” of spoken language; and delight your users with the intuitive ease of everyday conversation.</p><p><strong>API.AI:</strong></p><ul><li><a href="https://www.youtube.com/watch?v=K4v_QnngRdg">Building Rich Cross-Platform Conversational UX with API.AI</a></li></ul><p>API.AI helps developers build unique conversational experiences for their products, services and devices. It provides a toolset for designing interactions with users and a powerful natural language understanding engine to process user requests. By using API.AI, developers can build actions for Google Home, develop and launch chat bots or add voice to their robots. In this session we will explore how to use API.AI to design, build and analyze advanced conversational UX that may work across different platforms.</p><p><strong>Development:</strong></p><ul><li><a href="https://www.youtube.com/watch?v=Y26vvxCb3zE">Building Apps for Google Assistant</a></li></ul><p>The Google Assistant’s mission is to help users get things done in their world. This session will explain how to plug into the Google Assistant services ecosystem. We’ll cover everything from understanding the business use case and high level user interface design to implementation and growing usage. By the end of this session, you should have a better understanding of the Assistant service ecosystem and how to get started. Particularly, presenters will show how to use Transaction API, add rich experience to mobile by using suggestion chips and cards.</p><ul><li><a href="https://www.youtube.com/watch?v=fw27RFHP2tc">Defining Multimodal Interactions: One Size Does Not Fit All</a></li></ul><p>Multimodal interactions are coming to life on a wide range of surfaces and operate on a set of rules defined in your interaction model. But the tenets of a multimodal interaction vary wildly depending on whether you’re designing for a mobile device, a TV, a car, etc. We’ll delve into some of the things you need to consider when building a model for various surfaces.</p><ul><li><a href="https://www.youtube.com/watch?v=NDI0H9F08n8">Home Automation with the Google Assistant</a></li></ul><p>Come learn how to use the Actions on Google platform for home automation integrations. You will walk away from this session with the skills necessary for the Google Assistant to control your smart home devices.</p><ul><li><a href="https://www.youtube.com/watch?v=By972_gh9DY">Getting Your Assistant App Discovered</a></li></ul><p>If an action speaks in the forest and no one hears it, did it make a sound? The focus for this talk is discovery — we want users to be able to find the awesome Actions on Google experiences you’ve built. We’ll talk about triggering, directory listings, submissions, and overall best practices for getting your experience discovered by Google Assistant users.</p><ul><li><a href="https://www.youtube.com/watch?v=LlgMcJBnNN8">Transactions with the Google Assistant</a></li></ul><p>Users are turning to the Google Assistant to help with more real world tasks like scheduling appointments, booking services, and shopping. Enable your users to make purchases and set appointments with the Actions on Google platform. This talk will follow concrete examples, detailing elements like payments, user authentication, and order lifecycle.</p><p>There were many other interesting announcements at I/O; I would encourage you to read more about them <a href="https://medium.com/ben-and-dion/i-o-2017-invented-w-others-be392b4ab413">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f05b75286f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>