<?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 Tim Slagle on Medium]]></title>
        <description><![CDATA[Stories by Tim Slagle on Medium]]></description>
        <link>https://medium.com/@tim.slagle?source=rss-bf184836a958------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*lQNb27qJKL9L9nNT</url>
            <title>Stories by Tim Slagle on Medium</title>
            <link>https://medium.com/@tim.slagle?source=rss-bf184836a958------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:03:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tim.slagle/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[Developing Zoom Marketplace Apps w/ ngrok]]></title>
            <link>https://medium.com/zoom-developer-blog/developing-zoom-marketplace-apps-w-ngrok-3a53c895bb89?source=rss-bf184836a958------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a53c895bb89</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[zoom]]></category>
            <category><![CDATA[ngrok]]></category>
            <category><![CDATA[app-development]]></category>
            <dc:creator><![CDATA[Tim Slagle]]></dc:creator>
            <pubDate>Fri, 14 Feb 2020 03:01:01 GMT</pubDate>
            <atom:updated>2020-02-14T03:01:01.332Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*00zyMuUKytolB3lhSfRFQQ.png" /><figcaption>Image Source: ngrok.com</figcaption></figure><p>NGROK is a wonderful tool for developers to use when they are building web apps and tools. NGROK allows you to create introspectable tunnels directly to localhost. Not only does it allow developers to prototype fast, but it also allows for quick tunnels from the open web to your web apps and tools.</p><p>A lot of our developers use NGROK to make developing their web apps easier, but this can come with its own set of drawbacks. Today we will be talking about how to use NGROK effectively to make sure your app remains available for your users.</p><p>Why would you use NGROK as opposed to a more traditional reverse proxy like NGINX/Apache?</p><ul><li>NGINX/Apache can be a little more complicated than needed. Sometimes you need a quick on authenticated HTTP tunnel to your app.</li><li>NGROK is very quick. It is a simple command-line tool that makes tunnels with a single command.</li><li>You are prototyping and need a quick and dirty tunnel.</li></ul><p><strong>The dangers of using NGROK for production applications</strong></p><p>NGROK is a great tool, but when you are moving to a production environment there are some things to be aware of.</p><ul><li>Without a license, the NGROK URL will expire after a short period.</li><li>A single simple tunnel is a single point of failure and can work against you if not managed properly.</li><li>It is easy to out-scale an NGROK tunnel as you grow your app.</li></ul><p>But Tim, what can we do to make sure our app remains available? I’m glad you asked! There are a few steps you can take to make sure your NGROK tunnel remains active so your users can always find and use your app!</p><ul><li><strong>Purchase an NGROK subscription</strong>. If you are going to use NGROK as your tunnel service then we highly recommend buying a license. Buying a license comes with an SLA from NGROK and will ensure you have support if something should go wrong.</li><li><strong>Don’t use auto-generated endpoints</strong>. Auto-generated endpoints can be problematic as they can be reserved by another account by mistake. Make sure to reserve a subdomain for use with NGROK so you don’t lose your tunnel.</li><li><strong>Run NGROK as a service on a cloud provider or locally in your data center. </strong>Running NGROK as a service instead of a terminal instance will make sure you can monitor and restart NGROK as needed if something should fail.</li><li><strong>Planning to scale? Support NGROK with a load balancer. </strong>Again, for all the things NGROK does well, it is never meant to scale like a true load balancer. If you plan to have thousands of requests/users on your app then implement a load balancer in front of NGROK to make sure you can scale.</li></ul><p>That’s it. You’re ready to start building on Zoom with NGROK. If you have any questions you can visit us on our <a href="https://devforum.zoom.us/">community forum</a>. Also, make sure to check out our <a href="https://marketplace.zoom.us/docs/guides">marketplace and developer documentation</a> to get started if you haven’t already!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a53c895bb89" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zoom-developer-blog/developing-zoom-marketplace-apps-w-ngrok-3a53c895bb89">Developing Zoom Marketplace Apps w/ ngrok</a> was originally published in <a href="https://medium.com/zoom-developer-blog">Zoom Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Update to Meeting and Webinar Password Account Settings]]></title>
            <link>https://medium.com/zoom-developer-blog/update-to-meeting-and-webinar-password-account-settings-9affeb207fb5?source=rss-bf184836a958------2</link>
            <guid isPermaLink="false">https://medium.com/p/9affeb207fb5</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[zoom]]></category>
            <category><![CDATA[marketplaces]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tim Slagle]]></dc:creator>
            <pubDate>Wed, 11 Sep 2019 20:54:44 GMT</pubDate>
            <atom:updated>2019-09-11T20:54:44.525Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*a4cjFzKHC60sshgaTlpw4w.png" /></figure><p>Let’s get real about the developer impact for <a href="http://zoom.us/">Zoom’s</a> upcoming change to default to requiring passwords for Meetings and Webinars.</p><p>Zoom will be updating all accounts meeting and webinar password settings on September 22, 2019, empowering administrators with more control over your account settings.</p><h4>What does this mean for developers?</h4><ol><li>Going forward if you use a join flow that requires manually entering a meetingID into the Zoom UI, those users will be prompted for a password by default.</li><li>If you use the <strong>join_url</strong> to join your users to the meeting, then nothing changes, because we already include the meeting password in the <strong>join_url </strong>when creating or retrieving a meeting from the API.</li></ol><h4>A few examples:</h4><ol><li><strong>You create a meeting/webinar with a password using the </strong><a href="https://marketplace.zoom.us/docs/api-reference/introduction"><strong>Zoom API</strong></a></li></ol><p>In this case, nothing changes. You are already familiar with creating meetings with passwords, and your payload would return with a password as part of the join URL and as a part of the payload object.</p><p>Take a look:</p><pre>{<br>“uuid”: “+zA4sJrsCpPSFOw==”,<br>“id”: 70017,<br>“host_id”: “M — AC7MZ1Q”,<br>“topic”: “Test Meeting With Password”,<br>“type”: 2,<br>“status”: “waiting”,<br>“start_time”: “2019–12–25T06:00:00Z”,<br>“duration”: 60,<br>“timezone”: “Pacific/Midway”,<br>“created_at”: “2019–09–09T22:01:36Z”,<br>“start_url”: “<a href="https://zoom.us/s/700783617?zak=XXX">https://zoom.us/s/700783617?zak=XXX</a>&quot;,<br>“join_url”: “<a href="https://zoom.us/j/700783617?pwd=Y2I0ZnJtnhRdz09">https://zoom.us/j/700783617?pwd=Y2I0ZnJtnhRdz09</a>&quot;, //join_url contains the password as a query param<br>“password”: “TestPass”,<br>“h323_password”: “XXX”,<br>“pstn_password”: “XXX”,<br>“encrypted_password”: “Y2I0ZnJtnhRdz09”, //encrypted password for building join_url manually<br>“settings”: {}<br>}</pre><p>2. <strong>You create a meeting with no password using our API.</strong></p><p>In this case, you will see that a password (a six-digit numeric code) is automatically generated for the meeting. This is where you will need to look out for the new password if you are doing a manual join instead of using the <strong>join_url</strong>. If you are using the <strong>join_url</strong>, then nothing will change for you.</p><p>Here is another example payload (notice it is almost identical to the last payload):</p><pre>{<br>&quot;uuid&quot;: &quot;+zA4sJrsCpPSFOw==&quot;,<br>&quot;id&quot;: 70017,<br>&quot;host_id&quot;: &quot;M - AC7MZ1Q&quot;,<br>&quot;topic&quot;: &quot;Test Meeting Without Password&quot;,<br>&quot;type&quot;: 2,<br>&quot;status&quot;: &quot;waiting&quot;,<br>&quot;start_time&quot;: &quot;2019–12–25T06:00:00Z&quot;,<br>&quot;duration&quot;: 60,<br>&quot;timezone&quot;: &quot;Pacific/Midway&quot;,<br>&quot;created_at&quot;: &quot;2019–09–09T22:01:36Z&quot;,<br>&quot;start_url&quot;: &quot;<a href="https://zoom.us/s/700783617?zak=XXX">https://zoom.us/s/700783617?zak=XXX</a>&quot;,<br>&quot;join_url&quot;: &quot;<a href="https://zoom.us/j/700783617?pwd=Y2I0ZnJtnhRdz09">https://zoom.us/j/700783617?pwd=Y2I0ZnJtnhRdz09</a>&quot;, //join_url contains the password as a query param<br>&quot;password&quot;: &quot;254894&quot;, //auto generated password<br>&quot;h323_password&quot;: &quot;12345&quot;, //auto generated password<br>&quot;pstn_password&quot;: &quot;12345&quot;, //auto generated password<br>&quot;encrypted_password&quot;: &quot;Y2I0ZnJtnhRdz09&quot;, //encrypted password for building join_url manually<br>&quot;settings&quot;: {}<br>}</pre><p><strong>What if you, or your customers, don’t want this change?</strong></p><p>We thought of this too! Every account will have a banner displayed letting account owners/admins know about the change and when it will take effect for them. This banner will allow you to opt-out of this change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KDpBzgLpYPq3QTY6xw-5-A.jpeg" /><figcaption>Example of banner found on every Zoom account</figcaption></figure><p>If you click the link in the banner, you will be able to decline or approve the change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L9yl8SLjC3R3RBDcBj0iQg.jpeg" /></figure><p>For more information about this change, you can also visit our <a href="https://support.zoom.us/hc/en-us/articles/360033331271">support article</a>. This will give you a better overview of how this change works and how it may affect you and your users.</p><p>That’s about it.</p><p>This change won’t affect you at all if you are using the join_url. If for whatever reason your users need to manually enter their meeting ID to join, you should start looking out for a password beginning September 22, 2019.</p><p>If you have any questions or concerns, please post on our <a href="http://devforum.zoom.us/">developer forum</a> for a quick resolution!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9affeb207fb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zoom-developer-blog/update-to-meeting-and-webinar-password-account-settings-9affeb207fb5">Update to Meeting and Webinar Password Account Settings</a> was originally published in <a href="https://medium.com/zoom-developer-blog">Zoom Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deliver Happiness]]></title>
            <link>https://medium.com/zoom-developer-blog/deliver-happiness-6abaa8745999?source=rss-bf184836a958------2</link>
            <guid isPermaLink="false">https://medium.com/p/6abaa8745999</guid>
            <category><![CDATA[developer-advocacy]]></category>
            <category><![CDATA[zoom]]></category>
            <category><![CDATA[developer-stories]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[marketplaces]]></category>
            <dc:creator><![CDATA[Tim Slagle]]></dc:creator>
            <pubDate>Thu, 01 Aug 2019 15:01:01 GMT</pubDate>
            <atom:updated>2019-08-01T15:01:01.347Z</atom:updated>
            <content:encoded><![CDATA[<h3>What We’ve Learned — Deliver Happiness</h3><p>Happy customers always lead to growth</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hW9UrJ6hmcp-HZsea0xu1Q.jpeg" /></figure><p>Delivering happiness has been a core tenet from the start here at Zoom. It isn’t just something we say, but something we live and breath every day. The value of delivering happiness follows through to our marketplace in more ways than one, but I’d like to share the major ones with you.</p><h3>Value-Based Use Cases</h3><p>When we are building out our marketplace and talking with potential partners and developers on the platform, we strive to bring value to every app. This is probably one of the most important things you can do for a marketplace. As we grow, we look to the users on our platform and see how they use the product. We use data and anecdotal data to find use cases that move the needle for each of our users, which improve their workflows and solves problems for our users.</p><p>We believe in quality over quantity of apps, and thus, we do not populate our Marketplace with apps that are of no use. We hold each app to a very high standard and make sure that they provide real value. This keeps our customers engaged and happy with our marketplace in a significant way.</p><h3>Fast and Easy Support</h3><p>Things break. There isn’t anything you can do to stop that; however, you can control how you handle them when they do break. We pride ourselves in having a team that quickly and efficiently solves problems when they arise. It is this type of support that builds trust and allows you to build communities around your app ecosystem that won’t go anywhere.</p><p>At Zoom, we use the root cause principal even when interacting with customers. When someone reports an issue to us, we take three simple steps:</p><ol><li>Find the root cause</li><li>Resolve the root cause</li><li>Mitigate for the future</li></ol><p>This simple process allows us to support our customers and developers through almost any problem. Whether that be a technical issue, platform implementation questions, or have a question about the way our ecosystem works.</p><h3>Listen to your Users</h3><p>The ability to listen to the users on your platform will make or break your ability to deliver happiness to them. Every support case, every tweet about your platform, every email from your sales team, etc., is a letter from a user on your platform telling you how they use it, why they use it, and what they don’t like about it.</p><p>We have an uncanny ability here at Zoom to put our ear to the ground and understand what our collective customer base is telling us. Whether that is developers that need more tools or customers who need a new type of integration, we are always trying to be one step ahead of their needs.</p><p>As our platform grows, we are always reminded that delivering happiness to our developers and customers is only getting more critical. We strive to be one step ahead, go the extra mile, and make sure every experience with our marketplace is a good one, and we think you should too.</p><p>In the end, if you listen, provide first-class support, and provide value, users will flock to your platform and will continue to use it for as long as it continues to provide value.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6abaa8745999" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zoom-developer-blog/deliver-happiness-6abaa8745999">Deliver Happiness</a> was originally published in <a href="https://medium.com/zoom-developer-blog">Zoom Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What We’ve Learned — Quality Over Quantity]]></title>
            <link>https://medium.com/zoom-developer-blog/what-weve-learned-quality-over-quantity-eecbfa49d2cb?source=rss-bf184836a958------2</link>
            <guid isPermaLink="false">https://medium.com/p/eecbfa49d2cb</guid>
            <category><![CDATA[zoom]]></category>
            <category><![CDATA[developer-stories]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[developer-advocacy]]></category>
            <category><![CDATA[marketplaces]]></category>
            <dc:creator><![CDATA[Tim Slagle]]></dc:creator>
            <pubDate>Tue, 30 Jul 2019 15:01:01 GMT</pubDate>
            <atom:updated>2019-07-30T15:01:01.226Z</atom:updated>
            <content:encoded><![CDATA[<h3>What We’ve Learned — Quality Over Quantity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1r41lfYuNwShN4fjqAeb5w.jpeg" /></figure><p>At Zoom, we are always striving to provide the best customer experience we can. Doing so means that we always strive for quality, and the <a href="https://marketplace.zoom.us/">Zoom App Marketplace</a> is no different. As we continue to build our marketplace, we are continually learning the importance of providing a smaller subset of apps with higher quality than letting any app onto our marketplace.</p><p>We continually hear from our customers how they like that our marketplace doesn’t have a bunch of filler apps that they have to sort through to get to the ones that add value. We have learned that having standards, being picky, and not caving to outside pressures is the best way to provide a rock-solid and consistent experience for our customers. Let’s talk about that in more detail now.</p><h3>Have Standards</h3><p>As you grow a marketplace, you must decide early on the standards to which you will hold the apps in your marketplace. This has to be done early, and the standards must be clear. This is the bedrock for how your marketplace will function and how your approval process will go. We have found that having high standards and choosing quality over quantity leads to a marketplace that has meaningful solutions that add real value to our customers. Having clear standards allows you to do the following:</p><ol><li>Deliver a consistent customer experience.</li><li>Provide a transparent and efficient approval process for developers.</li><li>Gives the team managing your marketplace autonomy and allows them to be confident in their decisions.</li></ol><h3>Be Picky</h3><p>It’s okay to be picky. Being picky about the apps that make it into your marketplace is the essential way to make sure that your marketplace adds value. Having 5,000 apps might look good, but if only 10 of them provide real value, your customers will notice. We have learned that the last thing a customer wants is a dirty and cluttered marketplace. A cluttered marketplace causes confusion and leads to your customers, ultimately being frustrated with the extensibility of your platform.</p><h3>Don’t Cave</h3><p>Being picky and having standards means you are going to have to say no… a lot. This can be hard. It is especially hard in today’s fast-moving world where you may be getting priorities from external and internal sources. As you grow your marketplace, remember that you have already decided on the type of marketplace you want to have and have (hopefully) already defined the standards you wish the apps in your marketplace to adhere to. Regardless of the source of a priority, if it compromises the integrity of the standards you defined, stand your ground.</p><p>Time and time again, I see marketplaces fail because of this. They define their standards, but partnership agreements, internal priorities, and laziness compromise the ruleset and the entire marketplace suffers because of it. Those marketplaces that don’t cave into these pressures are the ones that see the most success, and we can say it is working for us, and our customers love our marketplace because it provides a great experience every time.</p><p>All in all, we have seen that with our marketplace adhering to our standards and choosing quality over quantity leads to the <a href="https://marketplace.zoom.us/">Zoom App Marketplace</a> as a place where our customers can find apps that add value to their workflows. We are excited to share our journey with you as we grow and learn. Look out for our next article in the series next week!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eecbfa49d2cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zoom-developer-blog/what-weve-learned-quality-over-quantity-eecbfa49d2cb">What We’ve Learned — Quality Over Quantity</a> was originally published in <a href="https://medium.com/zoom-developer-blog">Zoom Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What We’ve Learned — Why Build a Marketplace]]></title>
            <link>https://medium.com/zoom-developer-blog/what-weve-learned-why-build-a-marketplace-7bb8a9126672?source=rss-bf184836a958------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bb8a9126672</guid>
            <category><![CDATA[marketplaces]]></category>
            <category><![CDATA[developer-stories]]></category>
            <category><![CDATA[zoom]]></category>
            <category><![CDATA[developer-advocacy]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Tim Slagle]]></dc:creator>
            <pubDate>Fri, 26 Jul 2019 15:01:01 GMT</pubDate>
            <atom:updated>2019-07-26T15:01:01.386Z</atom:updated>
            <content:encoded><![CDATA[<h3>What We’ve Learned — Why Build a Marketplace</h3><p>Building an app ecosystem that delivers</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nIEoRXRsVjf9C-CIvK8uEQ.jpeg" /></figure><p>Building an app marketplace has many benefits. It’s no secret that app marketplaces work. With the biggest SaaS providers in the world providing app marketplaces, there is almost no limit to the benefits an app marketplace can bring to your product. The three main benefits from our perspective are the ability to deliver value outside of your product, creating loyalty, and increasing customer acquisition. Let’s go over these now.</p><h3>Bring Value Beyond Your Product</h3><p>As a SaaS provider, we are good at providing collaboration software to our customers. It would be short-sighted and naive of us to think that we could provide all of our customer’s needs through software and deliver a great experience, so we can focus on delivering a great video conferencing and collaboration experience.</p><p>This is where a marketplace comes in. A marketplace makes it possible to extend the capabilities of what you do well and let others provide new experiences for your customers. Let’s take a look at the Zoom App Marketplace and how we leverage it to expand our customer’s experience to places we couldn’t have gone before.</p><p>One of our most requested features is scheduling; being able to schedule a meeting or provide appointment slots for people to be able to schedule time with a Zoom customer. This is where <a href="https://marketplace.zoom.us/apps/BF4eht18S3a0KTLiKM3P0A">Calendly</a> comes into play. Instead of us trying to provide an excellent scheduling experience, we empowered <a href="https://marketplace.zoom.us/apps/BF4eht18S3a0KTLiKM3P0A">Calendly</a> to build an app on our platform, and they offer an excellent scheduling experience for Zoom customers.</p><p>We also get a lot of requests for learning management system integrations. We have university and colleges that use Zoom to provide remote lecture opportunities. Using the LTI protocol and REST APIs, companies like <a href="https://marketplace.zoom.us/apps/wSUTE6PqSCar-58njr9KWg">Absorb</a> LMS can seamlessly offer learning experiences to their students.</p><p>Time and time again, we recognize how valuable it is to allow other companies to provide their expertise and solutions as integrations so we can focus on providing a great meeting and collaboration experience.</p><h3>Create Loyalty</h3><p>One of the core tenets of Zoom is delivering happiness. As we grow, we always try to deliver happiness in everything that we do. A key part of delivering happiness to our customers is providing them with a great marketplace experience. This allows us to delight our customers by providing solutions through their favorite apps.</p><p>Providing REST APIs, SDKs, and other development tools allow customers to develop their integrations even if our marketplace doesn’t already have a specific integration that they are looking for, yet. Being able to remove the barrier allows us to provide that happiness and in turn, we gain a lot of customer loyalty. Delivering this kind of happiness is a key reason to Zoom’s success, and we will continue to destroy barriers like these using our marketplace.</p><h3>Increase Customer Acquisition</h3><p>Customers today are increasing their usage of SaaS solutions. As the usage of SaaS products increases, there is a natural fragmentation of these services. It is becoming increasingly important to provide ways for each of these SaaS products to integrate with your solution.</p><p>As we work with more customers, we are becoming increasingly aware of their need to integrate all their SaaS products to increase productivity. In some cases, these types of integrations can become sticking points when acquiring a new customer. At Zoom, we work very hard to build our platform to conform to the needs of our customers, so they never have to worry about integrating their other SaaS products with Zoom.</p><p>In the end, a marketplace has a myriad of different positives, but the important thing to remember is to listen to your customers and grow with them. If you grow with your customers and listen to their needs, a marketplace is bound to be successful.</p><p>Keep a lookout for our next post in this series next week!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bb8a9126672" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zoom-developer-blog/what-weve-learned-why-build-a-marketplace-7bb8a9126672">What We’ve Learned — Why Build a Marketplace</a> was originally published in <a href="https://medium.com/zoom-developer-blog">Zoom Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zoom App Marketplace — What we learned and where we’re going]]></title>
            <link>https://medium.com/zoom-developer-blog/zoom-app-marketplace-what-we-learned-and-where-were-going-9e15882794ca?source=rss-bf184836a958------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e15882794ca</guid>
            <category><![CDATA[zoom]]></category>
            <category><![CDATA[developer-relations]]></category>
            <category><![CDATA[developer-stories]]></category>
            <dc:creator><![CDATA[Tim Slagle]]></dc:creator>
            <pubDate>Tue, 23 Jul 2019 15:01:01 GMT</pubDate>
            <atom:updated>2019-07-23T17:30:43.999Z</atom:updated>
            <content:encoded><![CDATA[<h3>Zoom App Marketplace — What we learned and where we’re going</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PfontVAZoIp85_t-gkUjiA.png" /></figure><p>At Zoom, the needs of our customers are always at the forefront of our minds, and we pride ourselves on being responsive to their requests. So when Zoom grew into a viable player in the collaboration/meeting space, a number of our users asked for connectivity into other platforms and services, such as Slack, Zendesk, and Workplace by Facebook, to have seamless end-to-end solutions. And, as usual, we responded quickly.</p><p>While we built many of the standard connectors ourselves, we quickly realized that this model was unscalable. We also noted that a number of our partners, customers, and third-party developers use our APIs/SDKs on a large scale, solving connectivity issues themselves. However, they did not have a place to publish their solutions so that other Zoom customers could discover and access them. Since a robust foundational ecosystem is <em>essential</em> for any company to survive and grow in the long run, the obvious answer was the Zoom App Marketplace.</p><p><strong>The framework</strong></p><p>We focused on developing a robust framework early on that adapts itself to accommodate the workflows and business processes around our Marketplace.<strong> </strong>The foundational framework needed many things to come together. One of our primary concerns was avoiding scaling problems, so we concentrated on creating a solid tech stack and engineering architecture. Equally important was to establish the app life cycle, with transparent workflows around the framework, such as developer flow, publisher flow, and approval flow. We also put together the end to end business/validation process, updated end-user license agreements (EULAs), and created developer-specific legal agreements.</p><p><strong>Value and security</strong></p><p>From day one, we wanted to ensure that every app published on our Marketplace created value for at least a subset of our customers (our reject rate is about 65%). But more importantly, users needed to trust these apps. Because our customers use these apps, we developed a rigorous process around security-focused testing and validation. For example, we prevent apps from pulling customer or end-user data without explicit consent and approval. Also, any collected data must be removed when they delete the app. Making sure your customers know that their data security is important to you is paramount to the success of a scalable platform. We always put our customer’s data first and encourage all platforms to do the same.</p><p><strong>Developer documentation and forums</strong></p><p>Two critical elements of any platform are developer documentation and user forums. We spent a significant amount of time identifying and evaluating tools to host our documentation, establishing developer forums, and connecting them to our marketplace framework. We tried hosting the documentation ourselves with WordPress on our servers, but it slowed us down. Moving to a third-party doc hosting platform allowed us to move faster and not have the additional hassle during product releases delivering an exceptional user experience.</p><p>The same process happened with our forum. While these changes took time as we had to refactor our docs when we moved them across hosting frameworks, we needed to create an excellent experience for our developers. It was worth the cost, however, and we highly recommend providing a public place that allows you to communicate with your developers and/or end-users openly and honestly.</p><p>We also heard from customers that we needed a clearer developer documentation structure. They were correct, and we should have done a better job from the start. Inadequate and incorrect documentation on the API semantics, interfaces, and ambiguous terminology result in more support calls and frustration that builds up. It is an excellent investment to spend time and resources on it early in the cycle. We listened to our developer’s feedback and improved our documentation. This ongoing process requires a significant investment, but we learned it is worth the time to invest in thoughtful and intelligent documentation.</p><p><strong>App validation</strong></p><p>To ensure a consistent process for app validation, we created a single method and workflow for approving all apps, whether developed internally at Zoom or by third parties, the process, and validation criteria are the same. We made sure that developers were aware of the process well in advance of the submission of their app for approval. This created a transparent workflow that allows us to deliver high-quality apps to our customers and keep our developers happy with a transparent process. While this created some friction early on, we believe that value exists within consistency because our customers demand high-quality apps.</p><p><strong>Insights</strong></p><p>We cannot emphasize strongly enough how critical it is to build the data models and dashboards to track the KPIs on how the platform performs for both developers and end-users. This type of reliable data is necessary to determine where to focus on business decisions. Even when the data is available, it must be extracted, analyzed, and visualized in real-time and on-demand. We have built these insights into our framework. The developer relations team needs to have this data at their fingertips to make data-driven decisions.</p><p><strong>Clear sample apps, case studies, libraries, and versioning</strong></p><p>We are working hard to improve in this area. While it requires significant resource commitments, it is a priority for us going forward; we have several demo apps in our Github and have started building vertical case studies.</p><p>In hindsight, we realize that we should have thought through API versioning early on in the platform development cycle because introducing a versioning scheme after the fact involves significant refactoring. The need for language-specific libraries is more and more critical as developer programs grow. Today, developers use many different languages, and providing them with libraries in their native language (NodeJS, Python, C++, etc.) is paramount to the success of any developer platform. We are focused on these areas now and will continue to focus on creating great developer tools.</p><p><strong>Monetization</strong></p><p>While the revenue aspect of the platform is not an immediate business goal for us, however, we recognize the sustainability of these resources will require monetization business models in the future. Enterprises are always looking for solutions and services that solve their problems. We have found that our largest customers crave better connectors and services that solve their problems or help them monitor their business through real-time data-hoses and pipelines.</p><p><strong>Internal Advocacy</strong></p><p>It’s essential (more so in the enterprise segments) to prepare and provide continuous training to your company’s cross-functional teams, including sales, sales engineering, customer success, and support. Once an app goes live in the marketplace, your sales and customer success teams should have clear visibility into what business problems the app solves and position these apps in customer engagements. This process should be automated through tooling — you cannot scale this to hundreds and thousands of apps with a manual process.</p><p><strong>Commitment</strong></p><p>At Zoom, we want to foster the ecosystem for our developers, who rely on us, to provide best-in-class tools and resources to build amazing third-party apps. Results will not occur overnight, so we have a multi-year commitment to creating our Marketplace and platform that delivers and supports what our community requires. To deliver a thriving marketplace, focus on your developers and end-users by providing a seamless and transparent process as possible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e15882794ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zoom-developer-blog/zoom-app-marketplace-what-we-learned-and-where-were-going-9e15882794ca">Zoom App Marketplace — What we learned and where we’re going</a> was originally published in <a href="https://medium.com/zoom-developer-blog">Zoom Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zoom Platform — connecting a standards-based endpoint to a live meeting]]></title>
            <link>https://medium.com/zoom-developer-blog/zoom-platform-connecting-a-standards-based-endpoint-to-a-live-meeting-5333998b8670?source=rss-bf184836a958------2</link>
            <guid isPermaLink="false">https://medium.com/p/5333998b8670</guid>
            <category><![CDATA[pstn]]></category>
            <category><![CDATA[videos]]></category>
            <category><![CDATA[sip]]></category>
            <category><![CDATA[zoom]]></category>
            <category><![CDATA[audio]]></category>
            <dc:creator><![CDATA[Tim Slagle]]></dc:creator>
            <pubDate>Wed, 03 Apr 2019 20:47:37 GMT</pubDate>
            <atom:updated>2019-04-03T20:47:37.979Z</atom:updated>
            <content:encoded><![CDATA[<h3>Zoom Platform — connecting a standards-based endpoint to a live meeting</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jq_-877c0bWVosM85HGWdA.jpeg" /></figure><p>There are some compelling use cases to connect a third party application to a live Zoom meeting. One of those use cases is audio transcription and archiving. While the optimal way is for your application to get the audio recording post meeting through Zoom Marketplace and process that (the recording is available after the meeting ends and you need to be on the cloud recording add-on plan), there are ways to connect to a live meeting. Before considering this option, you need to make sure that you are not impacting the end user experience — users get freaked out if they see an “app” or a bot or a phone number showing up in the attendee list and listen to the conversation.</p><p>A pre-requisite for the first option to work is to have a Zoom cloud room <a href="https://support.zoom.us/hc/en-us/articles/201363273-Getting-Started-With-H-323-SIP-Room-Connector">connector</a> license. One license represents one connection — if you have 100 licenses on your account, you can have 100 simultaneous SIP connections on that account</p><h3>Connecting directly through Zoom Room Connector</h3><p>You can add an open source SIP + RTP stack such as <a href="https://www.pjsip.org/">PJSIP</a> inside your app. Depends on how your app or platform manages the meeting scheduling workflow, you can have your app call into the meeting with the URL “meetingid@&lt;zoom SIP gateway public IP&gt;” (example: 4087654432@192.168.33.164) OR parse the invite that has the SIP meeting URL and then join that meeting.</p><p>When your app sends the SIP INVITE to join a meeting, make sure you set the video SDP m-line to zero if all you want is to receive audio from that meeting and also set ‘recvonly’ for the audio RTP connection.</p><h3>Connecting through a PSTN gateway</h3><p>Another option is for your app to “dial” into the Zoom Meeting through a PSTN gateway and into the Zoom Meeting Telephony platform without going through the CRC. This is similar to someone joining a meeting from their phone by dialing the meeting phone number and entering the meeting. You do need a SIP gateway and a service provider SIP trunk (with all other infrastructure around it to handle failover, scaling, etc.). Your application will still need a SIP+RTP stack but it connects to your local SIP gateway.</p><p>If you have further questions, reach out to Zoom Developer Relations team at <a href="https://devforum.zoom.us/">https://devforum.zoom.us/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5333998b8670" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zoom-developer-blog/zoom-platform-connecting-a-standards-based-endpoint-to-a-live-meeting-5333998b8670">Zoom Platform — connecting a standards-based endpoint to a live meeting</a> was originally published in <a href="https://medium.com/zoom-developer-blog">Zoom Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Live Streaming to 3rd party platforms — Now “Live” in Zoom Marketplace]]></title>
            <link>https://medium.com/zoom-developer-blog/live-streaming-to-3rd-party-platforms-now-live-in-zoom-marketplace-74a393f50d83?source=rss-bf184836a958------2</link>
            <guid isPermaLink="false">https://medium.com/p/74a393f50d83</guid>
            <category><![CDATA[streaming]]></category>
            <category><![CDATA[zoom]]></category>
            <category><![CDATA[developer-blog]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[videos]]></category>
            <dc:creator><![CDATA[Tim Slagle]]></dc:creator>
            <pubDate>Mon, 27 Aug 2018 19:30:30 GMT</pubDate>
            <atom:updated>2018-11-09T18:29:02.777Z</atom:updated>
            <content:encoded><![CDATA[<p>We are happy to announce that you can now integrate live streaming of Zoom meetings and webinar to any 3rd party streaming or content platforms similar to the native integration that we have done with Facebook Workplace and YouTube. The use cases for receiving the live stream from Zoom is not just restricted to expanding the audience pool. We have heard from our customers that they want to do analytics on the video stream to gauge participant engagement or extract the audio stream, perform speech to text and then analyze the speech for some use cases including predictive analytics for a sales call.</p><p>Let’s get into the details of integrating and use our platform for live streaming. The first step is to create an account level <a href="https://marketplace.zoom.us/">Zoom marketplace app.</a> Check our <a href="https://devdocs.zoom.us/">docs</a> on how to go about doing that. The streaming APIs are supported only through our marketplace through OAuth tokens.</p><ul><li>Registering for the streaming</li></ul><p>The streaming needs to be enabled on a per meeting basis. Depends on your app workflow, you can either poll our meeting APIs to check when a meeting is scheduled by a user in that account or register for the start_meeting webhook in the marketplace to get a notification on all the meetings that get started in that account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*skX1CHemW4jfjm0K.png" /></figure><p>Regardless of the method, once your app has the meeting id, you can call the Livestream API to create that stream. “stream_url” is the RTMP URL of the stream (that you will get from your streaming server such as rtmp://) and “stream_key” is the stream key that you should get from your RTMP service.</p><ul><li>Start and Stop the live stream</li></ul><p>You can use the following API to start and stop live stream from your app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/0*FiHpTB-hFTswWAHy.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9OID9x_XhEDYgVYC.png" /></figure><p>That’s it for now but one thing to note. There is an account level and user level setting that needs to be enabled by the user. There is no API for doing this now, and we will be releasing that by October. Until then, you need to ask the account admins to enable the live stream setting before you use these APIs to control the streaming.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9AsqVZYb1WZEWEDD.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74a393f50d83" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zoom-developer-blog/live-streaming-to-3rd-party-platforms-now-live-in-zoom-marketplace-74a393f50d83">Live Streaming to 3rd party platforms — Now “Live” in Zoom Marketplace</a> was originally published in <a href="https://medium.com/zoom-developer-blog">Zoom Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zoom Messaging APIs are now available through Marketplace]]></title>
            <link>https://medium.com/zoom-developer-blog/zoom-messaging-apis-are-now-available-through-marketplace-74b8ef0981fe?source=rss-bf184836a958------2</link>
            <guid isPermaLink="false">https://medium.com/p/74b8ef0981fe</guid>
            <category><![CDATA[developer-blog]]></category>
            <dc:creator><![CDATA[Tim Slagle]]></dc:creator>
            <pubDate>Tue, 14 Aug 2018 20:32:44 GMT</pubDate>
            <atom:updated>2019-06-10T23:47:32.384Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the last year, we have received some requests to open up our messaging platform to third-party apps. We had to wait a bit, as we were in the middle of developing the <a href="https://marketplace.zoom.us/">Zoom Marketplace</a> framework. Our messaging interfaces are now available for third-party apps through our marketplace.</p><p>You can create a bot, select the IM scopes, create webhooks, and test them right away! Your bot can be invoked either in a 1:1 chat or in a group chat.</p><h4>Create a new app in our marketplace</h4><p>Go to Zoom Marketplace, select building an app and <strong>enable chat subscriptions</strong>. Afterward, the <strong>command</strong> is just the name of your bot that end users will invoke from the chat rooms/channels. The <strong>Bot endpoint URL</strong> is the webhook that our platform will call back when the bot is invoked by the user. In the following example, if the user invokes the bot with “<strong>/calluber to 55 Almaden Blvd, San Jose</strong>”, your app will get “<strong>to 55 Almaden Blvd, San Jose</strong>” in the webhook “https://calluber.com/dev.&quot;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Rc06S7nhe-WmJKQq.png" /></figure><ul><li>Note that you need to provide separate webhooks for development and productions. This is part of our marketplace framework, and more info is available in our <a href="https://marketplace.zoom.us/docs">docs</a>.</li><li>You can then select specific scopes — it all depends on what other APIs you are going to use based on your workflow and use case. Just don’t get confused between <strong>imgroup</strong> and i<strong>mchat</strong>. IM group lets you control the group membership (add/remove users to specific IM groups).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-Zq156ZpGBiCUe21.png" /></figure><ul><li>Once your app is created and approved, it’s visible to all Zoom users in our marketplace to authorize and use. Once pre-approved and authorized by account admin, the bot is available across all the IM channels.</li></ul><p>More details are available in our <a href="https://marketplace.zoom.us/docs/chat-bot-api">docs</a>. As always, reach out to us on our <a href="https://devforum.zoom.us/">developer forum</a> if you have questions or need help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74b8ef0981fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zoom-developer-blog/zoom-messaging-apis-are-now-available-through-marketplace-74b8ef0981fe">Zoom Messaging APIs are now available through Marketplace</a> was originally published in <a href="https://medium.com/zoom-developer-blog">Zoom Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Webinar recording: Zoom Room automation options]]></title>
            <link>https://medium.com/zoom-developer-blog/webinar-recording-zoom-room-automation-options-59eb583d4136?source=rss-bf184836a958------2</link>
            <guid isPermaLink="false">https://medium.com/p/59eb583d4136</guid>
            <category><![CDATA[developer-blog]]></category>
            <dc:creator><![CDATA[Tim Slagle]]></dc:creator>
            <pubDate>Fri, 03 Aug 2018 01:20:09 GMT</pubDate>
            <atom:updated>2018-09-18T20:07:28.000Z</atom:updated>
            <content:encoded><![CDATA[<p>Zoom held a Zoom Rooms Integrator Training Webinar on August 2, 2018. The presentation included a section on the ZR-CSAPI that focused on Zoom Room automation, at the 0:20:45 mark. You can watch it <a href="https://success.zoom.us/recording/play/bd4DNoX64Fa4YrXAj1I_-ZThgVcnwrGA7k9BatUkS946DABFRIC-qn6SmFbiDLse?continueMode=true">here</a>.</p><p>We went over the two major options for Zoom Room integration with automation controllers:</p><ul><li>Crestron TSW page-flipping: The TSW runs the Android Zoom Room Controller, and can page-flip back to the Crestron app for environmental controls.</li><li>A custom configuration using the ZR-CSAPI, with a user experience designed by the integrator.</li></ul><p>For the fully custom option, integrators should follow this basic connection diagram:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/0*FFpGSRlVsnPr28-T.png" /></figure><p>Integrators can start now using the ZR-CSAPI version 1.0, and later make use of new 1.1 fixes and feature we have planned for Mac and Windows Zoom Rooms.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59eb583d4136" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zoom-developer-blog/webinar-recording-zoom-room-automation-options-59eb583d4136">Webinar recording: Zoom Room automation options</a> was originally published in <a href="https://medium.com/zoom-developer-blog">Zoom Developer Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>