Technical Requirements for Pear Deck

Overview

This article covers all of the known technical requirements for making sure Pear Deck works optimally at your school or site. Most of the time, Pear Deck works automatically! In this article you can read through the following categories:

  • Supported Devices and Browsers
  • Accounts
  • Permissions
  • Cookies
  • Network Infrastructure and Firewalls

Supported Devices and Browsers

We actively support the latest versions of Chrome, Firefox, Edge, and Safari users. Pear Deck works great in these browsers, on all kinds of devices, including:

  • Chromebooks, laptops, and desktops, including Mac, PC, and Linux
  • Android devices, including phones and tablets
  • iPhones, iPods, and iPads. Please note: The Pear Deck for Google Slides Add-on is not supported on these devices, so you won't be able to add Interactive Questions to your slides. But you can still start a Pear Deck Session from Pear Deck Home, and students can join a presentation from joinpd.com, on these devices.

Accounts

Pear Deck requires that all users, including teachers and students, use either a Microsoft Office 365 or Google account. You may use an individual account. Typically, schools and organizations have implemented Google Apps for Education or Office 365 Education. In order to install the Pear Deck application from the Chrome Webstore or Apps Marketplace, a Google Domain Administrator must allow users to install Chrome Applications.

Permissions

Pear Deck will require different permissions based on your user type.

For a teacher/presenter, Pear Deck requires permissions in order for you to create, save, and share your Pear Deck files. Whether you sign up for Pear Deck with Google Drive or OneDrive, we'll need access to do the following:

  • View your files
  • View your presentations
  • View and manage files and folders that you have opened or created with the Pear Deck app
  • Add Pear Deck to your Google Drive or OneDrive

For a student/participant, joining a Session requires permissions to identify you to the presenter and save your responses.

Cookies

Pear Deck uses some third parties that require cookies to operate. We expect to set cookies from:

  • peardeck.com
  • google.com
  • youtube.com
  • login.microsoftonline.com

Click here to learn about allowing cookies.

Network Infrastructure and Firewalls

Pear Deck requires that all devices in a classroom maintain an internet connection (i.e. stable WiFi). In some cases, network and connectivity problems may persist and require further troubleshooting which may include the whitelisting of the underlying services used by Pear Deck. Please contact help@peardeck.com if you believe this may be a problem on your network.

The following domains, in bold, should be allowed through your firewall:

*.peardeck.com

This serves our main website, several supporting services, and static files like images and javascript.

*.squarespace.com
Squarespace powers peardeck.com.

*.firebaseio.com

This is what we use for all realtime communication during class.

*.googleapis.com, *.google.com, *.googleusercontent.com, *.gstatic.com

We use these to talk to Google.

*.s3.amazonaws.com

We use it to store images shown on student computers.

*joinpd.com

This is the student Join URL.

 

Optional: notify.bugsnag.com

We use this to collect extra information if something happens to go wrong.

Optional: *.hubspot.com

We use this to provide help to teachers in the app so they don't need to email us. We don't use it with students.

 

We will try to make requests to some additional domains for analytics and error reporting, but those services aren't necessary to operate Pear Deck.