![automute app automute app](http://www.autocommute.com/images/ocs/sd/IMG_2223c.jpg)
![automute app automute app](https://www.droidapp.nl/wp-content/uploads/2016/02/HERE.jpg)
(Your domain is the name you chose for your account. env.local file with your own Daily domain and Daily API key, which can be found in the Daily dashboard. The fitness demo is in the /custom/fitness-demo directory.įrom the fitness demo’s directory, you can copy over the sample environment variable file like so: mv env.example. You’ll need to fork our examples monorepo, which has a large collection of different Daily use cases/features (it’s worth checking out!) To start, let’s get the demo running locally: Once we’ve covered how those buttons work, we’ll then add an auto-mute feature ourselves so instructors can get started as soon as they join. In today’s tutorial, we’ll look at Daily’s open source examples repo, which has a fitness demo with “Mute all cameras” and “Mute all microphones” buttons included. Adding an auto-mute feature when the instructor starts a class.Adding “Mute all” buttons for student microphones and cameras.Today, we’ll focus on a couple specific muting features to help instructors get their students focused: In our first fitness series post, we introduced our new fitness demo app and linked to a bunch of relevant existing tutorials to get the basic feature set built out.
#AUTOMUTE APP HOW TO#
To help support our fitness customers, we’ve put together this tutorial series on how to get the most out of your Daily fitness app. Over time and through conversations with customers, we’ve learned that there are several features that are pretty specific to fitness apps. Recently at Daily, we’ve been thinking more about how to support specific app use cases, like fitness apps with real-time video. This is part two in our fitness use case series on how to build a custom Daily fitness app.