Automatic camera optimization across different phones
MedCam does not need a static list of every phone model. That would quickly become incomplete as devices and browser versions change. Instead, it asks the active browser for camera features and gently requests a suitable preview. No phone model is certified by this guide.
What is actually adjusted?
- Preview negotiation: first request a rear-facing high-quality feed; if unavailable, try more flexible camera constraints or a basic video stream. Browser permission is always required.
- Hardware controls: show zoom and torch only if reported; optionally request continuous focus, exposure and white balance if listed as supported, then verify settings when visible.
- Low-power protection: where available, coarse RAM and CPU hints may favor a lighter preview and smaller processed copy. Original accepted image bytes remain unchanged.
- Real workload: reduce preview-analysis frequency when processing becomes slow; hidden pages pause readiness and Auto Capture.
- Screen: mobile, tablet, desktop-site mode, rotation, browser zoom, touch and accessibility preferences drive responsive layout. A browser cannot always identify a phone's physical display size.
- Fallback: if browser camera access fails, users can take a photo using the device's camera app or upload an existing photo; hardware capabilities cannot be manufactured by a webpage.
Example phone and tablet families — NOT a compatibility certification
These are illustrative manufacturers/product families, not an exhaustive list of models and not tested-device claims. MedCam uses the same capability-based approach for other brands and future phones.
| Device families (examples) | What MedCam checks | When features are unavailable |
|---|---|---|
| Apple iPhone, iPad | Safari/browser permissions, video frame dimensions, available camera settings | Native camera app + supported image upload |
| Samsung Galaxy A/S/Z/M; Google Pixel; Motorola Moto/Edge; Nothing Phone | Actual camera facing mode, resolution, constraints, memory hints where exposed | Basic preview, manual capture or device camera |
| Xiaomi, Redmi, POCO; OnePlus, OPPO, Realme, vivo, iQOO | Browser capabilities and camera track settings, not the brand name | Use a supported full browser or native camera |
| Huawei, HONOR, Lenovo, ASUS, Sony, Nokia/HMD | Active web engine, permission, optional camera controls | Disable unsupported hardware buttons safely |
| Tecno, Infinix, itel; ZTE, nubia; TCL, Alcatel, Meizu | Live API, preview resolution and upload/encoding support | Device-camera/file input where available |
| Windows/macOS/Linux laptops; Android/Windows tablets | Viewport, webcam enumeration, browser and USB camera support | Upload a photo from another camera |
Why model numbers cannot guarantee clear medical photographs
Two devices with the same name can have different browser, camera-driver and OS versions, permissions, lighting conditions or lenses. A phone's highest advertised megapixel count does not guarantee a sharp web-camera frame. The only reliable check is the actual captured image and whether all clinically relevant labels and frames remain readable to the receiving clinician.
Run a private test on your device
- Open Browser Self-Test on the actual phone/browser.
- Review the local API results; choose Test camera only if you want to grant permission.
- Check the detected preview resolution and available continuous-focus, exposure and white-balance modes. Missing values mean the browser did not report them.
- Capture a non-patient sample using Manual and Auto modes. Check framing, tiny details and camera switching.
- Try JPG download and native Share. A file appearing in the share sheet does not prove it was delivered to a doctor.
- Record browser/OS version, test date, lighting and observed failures without personal health data. Repeat after major browser updates.
Film-specific cautions and patient safety
X-ray and CT/MRI film sheets may need even backlighting; ECG paper benefits from visible fine grid lines; ultrasound images require legible annotations and measurements. Auto Capture is an experimental visual heuristic and may not trigger on some valid scenes. It does not recover lost anatomical details or certify diagnostic quality. Manual Capture and original-image preservation remain essential.
Technical references
For the meaning and limitations of these browser APIs, see MDN camera permissions and constraints, track capabilities, actual settings, and approximate memory hint. No advertising or analytics code may access local medical images in the current prototype.