<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>device on asdfasdfasdfasdfddd</title><link>https://academy.test.quriobot.com/tags/device/</link><description>Recent content in device on asdfasdfasdfasdfddd</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://academy.test.quriobot.com/tags/device/index.xml" rel="self" type="application/rss+xml"/><item><title>Custom jumps (and response) based on device types</title><link>https://academy.test.quriobot.com/how-to-build-an-advanced-bot/custom-jumps-and-response-based-on-device-types/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://academy.test.quriobot.com/how-to-build-an-advanced-bot/custom-jumps-and-response-based-on-device-types/</guid><description>If you want to create custom jumps based on the device type you will need to do the following.
Example : that will detect if you&amp;rsquo;re on a mobile device (and exit the bot or otherwise continue to Step 2).
Note: this might be helpful if, for example, you don&amp;rsquo;t want to show the Fold-out step on mobile devices
Step 1: Add a GoTo Step that uses the value of this variable ({{infoDeviceType}} in this example) and create your Response and corresponding Jump logic based on the value</description></item><item><title>Which devices and/or browsers are supported?</title><link>https://academy.test.quriobot.com/general-information/which-devices-and-or-browsers-are-supported/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://academy.test.quriobot.com/general-information/which-devices-and-or-browsers-are-supported/</guid><description>The browser and mobile OS support Quriobot is supported on all modern browsers and is built with modern techniques to run on all latest versions of browsers and devices (fully responsive so it works on any device, desktop or mobile, even within your apps) but that doesn’t mean we only support these. We make sure to continuously run compatibility checks for good backward compatibility. Generally speaking, we use a top-10 approach, which means we support the global top 10 in browsers based on usage in the last half-year.</description></item></channel></rss>