Browser Compatibility

Koji works in all modern browsers for text-based interviews. Voice interviews have stricter requirements due to the real-time audio technologies involved. This guide covers what works, what has limitations, and how to get the best experience.

---

Quick Compatibility Table

---

Recommended Browsers

Google Chrome and Microsoft Edge are the recommended browsers for Koji. They provide:

• Full support for text and voice interviews.
• Reliable microphone access and echo cancellation.
• Consistent WebSocket performance for real-time voice streaming.
• Excellent developer tools for debugging embedded integrations.

If you are sharing interview links with respondents, suggesting Chrome or Edge in your invitation message helps ensure a smooth experience.

---

Browser-Specific Notes

Google Chrome

Chrome is the most tested and best-supported browser for Koji. All features work as expected. Keep Chrome updated to the latest version for the best experience.

Tip: If you experience microphone issues in Chrome, check that no other tab or application is using the microphone. Chrome sometimes has difficulty sharing the microphone between multiple tabs.

Microsoft Edge

Edge is built on the same Chromium engine as Chrome and offers identical functionality. All Koji features, including voice, work fully in Edge.

Mozilla Firefox

Firefox supports all Koji features, but voice interviews occasionally experience:

• Echo cancellation issues. Firefox's echo cancellation is less aggressive than Chrome's. Respondents using speakers (instead of headphones) may experience echo during voice interviews.
• Microphone selection. When multiple microphones are connected, Firefox may not always select the preferred one. Check Firefox's input device settings if the wrong microphone is active.

For the most reliable voice experience, we recommend Chrome or Edge over Firefox.

Apple Safari (Desktop)

Safari on macOS supports text interviews fully. Voice support has improved in recent versions but still has some limitations:

• WebSocket reliability. Safari's WebSocket implementation can be less stable than Chromium-based browsers for long-duration voice sessions.
• Microphone permissions. Safari requires both browser-level and system-level microphone permissions. See Voice Interview Not Working for setup instructions.
• Version matters. Safari 16+ has significantly better audio support than earlier versions. Update macOS to get the latest Safari.

Safari (iOS)

iOS Safari has unique audio handling that affects voice interviews:

• Audio autoplay restrictions. iOS requires a user gesture (tap) before audio can play. Koji handles this, but it means the first interviewer response may require a tap to hear.
• Background behavior. If the respondent switches to another app during a voice interview, iOS may suspend the audio session. Returning to Safari usually resumes it, but the experience can be disrupted.
• Microphone access. iOS prompts for microphone permission per-site. If the respondent denied permission, they need to go to iOS Settings > Safari > Microphone to re-enable it.

For respondents on iOS, text-mode interviews generally provide a more reliable experience than voice.

Brave Browser

Brave is Chromium-based and supports Koji well. However, Brave's shield settings may block WebRTC connections used for voice. If voice does not work in Brave:

1. Click the Brave shield icon in the address bar.
2. Ensure Fingerprinting protection is set to standard or disabled for the Koji domain.
3. Alternatively, add app.getkoji.com to Brave's exception list.

---

Embed Widget Compatibility

The embed widget works in all supported browsers with these considerations:

• iframe sandbox. The embed widget requires that the host page does not apply overly restrictive iframe sandbox attributes. The minimum required permissions are allow-scripts, allow-same-origin, and allow-forms.
• Microphone in iframes. For voice interviews in the embed widget, the iframe tag must include allow="microphone". Without this attribute, the browser blocks microphone access inside the iframe regardless of the user's permission settings.
• Third-party cookies. Some browsers block third-party cookies by default, which can affect session management in the embed widget. If you encounter issues, check the browser's cookie settings for the Koji domain.

---

Mobile Browser Considerations

Mobile browsers generally work well for text interviews. Voice interviews on mobile have additional considerations:

• Network quality. Mobile networks can have higher latency and more packet loss than Wi-Fi, which affects real-time voice quality.
• Battery impact. Voice interviews use more battery than text due to continuous microphone input and audio processing.
• Screen size. Koji's interview interface is responsive, but smaller screens mean less visible conversation history. The experience is still functional but more compact.
• Notifications. Incoming calls, notifications, and other interruptions can disrupt voice sessions on mobile. Suggesting "Do Not Disturb" mode in your interview invitation helps.

---

Minimum Requirements

For any browser to work with Koji, it must support:

• JavaScript ES2017+ (async/await, Promises)
• WebSocket API (for real-time features)
• Fetch API (for HTTP requests)
• CSS Grid and Flexbox (for layout)
• Web Audio API (for voice interviews only)
• MediaDevices API (for microphone access in voice interviews only)

Any browser released in the last three years supports all of these. If you are using a very old browser version, update it to the latest release.

---

Enterprise and Restricted Environments

In corporate or enterprise environments, browser capabilities may be restricted:

• Group policies. IT-managed browsers may block microphone access by policy. Check with your IT team.
• Proxy servers. Corporate proxies can interfere with WebSocket connections. Koji needs direct WebSocket access to its voice servers.
• Content filters. Network-level content filters may block certain domains. Ensure app.getkoji.com is allowlisted.
• Managed Chrome profiles. Chrome Enterprise profiles may have extensions or settings that affect Koji. Try in an unmanaged profile or incognito to diagnose.

---

Checking Your Browser

If you are unsure whether your browser supports Koji:

1. Navigate to the Koji login page.
2. If you see a compatibility warning, your browser may not be fully supported.
3. If everything loads normally, your browser is compatible.

For voice specifically, try starting a voice interview. The browser prompts for microphone permission — if it does not, your browser may not support the required audio APIs.

---

Next Steps

• Troubleshoot voice issues
• Learn about the voice interview experience