Old Android. Family iPad.
School lab PC. All in.

Every modern device. Desktop: Windows 10 and 11, macOS 11+, Linux (Ubuntu, Debian, Fedora, Mint and other modern distros), and ChromeOS. Mobile: Android 8.0+ and iOS 14+ (including iPadOS 14+). The browsers covered: Chrome, Firefox, Safari, Edge, Samsung Internet, and Brave. There is no native LiveLoop app to install on any of these platforms — the same WebRTC code path runs in the browser everywhere.

Right. LiveLoop runs entirely inside the browser using WebRTC — the same standard that powers WhatsApp Web video calls. There is no native app on any operating system, including iOS where the App Store gate stops a lot of parents and students from joining other meeting tools. You click the join link, the browser opens, you allow camera and microphone, and you are in. That's the whole flow. See instant-join for more detail on the join experience.

Yes. Entry-level Android devices running Android 8.0 or higher with mobile Chrome can host and join LiveLoop sessions. Sessions have been validated on devices like the Redmi 8, Realme C-series, Samsung Galaxy A0x, and similar budget Indian phones. The platform uses adaptive bitrate — on a device with a weaker CPU or a weaker mobile connection, video resolution is automatically lowered while audio is preserved, so the student still hears the teacher clearly.

Both work. Sessions are tested on school-issued Lenovo Chromebook carts (very common in CBSE / state-board schools that received pandemic-era device grants) and on Linux computer labs running Mint, Ubuntu, or Fedora. ChromeOS uses Chrome by default — the join experience is identical to a Windows laptop. Linux labs use Chrome or Firefox; both support every LiveLoop feature including screen sharing and breakout rooms.

Yes. The underlying WebRTC ICE restart mechanism reconnects automatically when the network interface changes — Wi-Fi to mobile data, or one Wi-Fi network to another (campus Wi-Fi to home Wi-Fi). There may be a 2–4 second freeze during the renegotiation; the session does not end and you do not have to rejoin. This matters for students on shared family Wi-Fi with frequent micro-disconnects and for teachers moving between staff room (Wi-Fi) and classroom (mobile hotspot).

No. The same set of features — mute, video toggle, screen share, chat, breakout room participation, hand-raise, polls, captions, recording for the host — is available on mobile Chrome (Android) and mobile Safari (iOS) as on desktop browsers. The layout adapts for the smaller screen; the capability set does not change. There is no separate "mobile-lite" build.

Chrome 80+ (released early 2020), Firefox 75+ (April 2020), Safari 14+ (September 2020 — covers iOS 14+ and macOS Big Sur), Edge 80+, Samsung Internet 12+. If a browser is more than five years out of date, joining may fall back to audio-only or fail entirely. Most Indian users on any device updated in the last four years are well inside the supported range. For an institution still on Internet Explorer 11, the answer is to use Chrome instead — IE is not a supported browser anywhere in the WebRTC world.

Generally the opposite. A native app runs with full access to the device's file system, contacts, microphone, camera, and often background processes. LiveLoop in the browser runs inside the browser sandbox — it can use camera and microphone only with explicit per-domain permission and cannot read files, contacts, or other apps. Media encryption (DTLS-SRTP) is the same whether you're in a browser or a native client. For full security details, see the LiveLoop security feature page.

Yes. ChromeOS Chromebooks (the most common school-issued device under Indian Smart Class and SBI-sponsored device programmes) run Chrome by default. The LiveLoop session experience on a Chromebook is identical to one on a Windows laptop — same join flow, same in-session features, same screen-share behaviour. No additional setup is needed at the device level; the school's IT admin doesn't need to install or whitelist a LiveLoop binary.

No. That is the whole point of browser-only. The parent receives the meeting link on WhatsApp or in the parent app. They tap it. Their phone's browser opens — could be Chrome, could be Samsung Internet, could be even an older Android default browser. They allow camera and microphone. They are in. No app to update, no "this version of Zoom is too old", no App Store account required. If the parent can open a YouTube video on their phone, they can join a LiveLoop PTM.