DevicePrep™

About us

Our Journey

We’re building a faster way to troubleshoot device problems so you can focus on the conversation, not your settings.

Our founding story

DevicePrep started with a simple frustration: the same preventable device issues kept derailing calls. A muted mic. A webcam picked up by the wrong app. Bluetooth stuck in the wrong mode. The “can you hear me?” loop before every meeting.

We built DevicePrep to replace guesswork with a repeatable workflow: test what your browser can see, confirm what’s actually happening, and then apply fixes that you can validate immediately.

From a checklist to a diagnostic toolkit

What began as a pre-call checklist became a set of fast, browser-based tests for microphone, camera, speakers, keyboard, mouse, screen, and network health.

The goal is speed and clarity: you should be able to answer “Is the device working?” in seconds before you open Zoom, Google Meet, Teams, or any other meeting app.

Driving confidence through browser-first tools

Most DevicePrep tools use standard browser APIs (like WebRTC and Web Audio) to show live signals and device details. Your browser will always ask permission before accessing your microphone or camera.

We design for privacy and simplicity: core checks run locally in your browser, and the UI emphasizes clear next steps over technical jargon.

Maintaining trustworthy fixes as settings change

Operating systems and meeting apps change constantly, so “the right fix” needs ongoing review. We keep guides step-by-step, verify settings labels across platforms, and add validation steps inside DevicePrep tools whenever possible.

Our editorial team treats troubleshooting like a product: every step should be clear, current, and testable.

Read the editorial policy.

What makes DevicePrep different

Instead of generic advice, we try to make troubleshooting measurable. Many DevicePrep tools produce a copyable report so you can share evidence with IT or support without guessing.

  • Test-first: start with a browser-based check so you know whether the device is detected and permitted.
  • Fix in layers: browser permissions → OS privacy → app device pickers (Zoom/Teams/Meet).
  • Validate: re-test after each change so you can see exactly what improved.
  • Privacy-first: you control prompts; core signals are processed locally.

Need help? Use the contact page to generate a structured support request (with space to paste tool reports).

Directors & Contacts

DevicePrep is run by a small team of editors and builders. For support, feedback, or corrections, email [email protected] or use our contact page.

Adrian Reyes
Adrian Reyes

Microphone & Audio Troubleshooting Lead, DevicePrep

Writes and maintains DevicePrep's microphone troubleshooting guides, covering OS permissions, device routing, Bluetooth mic profiles, and browser-level audio diagnostics across Zoom, Teams, and Google Meet.

Nikhil Desai
Nikhil Desai

Webcam & Video Diagnostics Lead, DevicePrep

Owns DevicePrep's webcam and camera troubleshooting content—covering driver refresh, privacy toggles, browser camera permissions, and video quality diagnostics across Windows, macOS, and meeting apps.

Simone Park
Simone Park

Network & Connectivity Diagnostics Lead, DevicePrep

Builds and maintains DevicePrep's network diagnostic tools—Ping Test, Upload Speed Test, and Network Test—and writes the guides that help users fix latency, jitter, packet loss, and bandwidth issues before video calls.

Kendra Holt
Kendra Holt

Speaker, Echo & Device Compatibility Lead, DevicePrep

Leads DevicePrep's speaker and echo troubleshooting content and cross-browser device testing—ensuring audio output guides, the Speaker Test, and the Echo Test work reliably across browsers, assistive technologies, and the real-world hardware people bring to calls.

Want to learn more about how we work? Meet the team.

Join our community

DevicePrep is for anyone who needs confidence before a call: remote workers, students, interviewers, creators, and support teams. If you have an idea for a new test or a fix that should be added, we’d love to hear it.