Capture connects to your dynamometer directly through the browser and streams force in real time, so you can run an assessment without exporting a file from anything. That direct connection uses Web Bluetooth, a browser capability that is only implemented in some browsers on some platforms. If you are on a combination that supports it, pairing takes a few seconds. If you are not, the device picker will never find your dynamometer, no matter how healthy the device is. This article is the short version of what to run.
What works
Capture works in current Chromium-based browsers on desktop and Android:
- Google Chrome and Microsoft Edge, on Windows, macOS, Linux, and ChromeOS.
- Other Chromium browsers on the same platforms (for example Opera, Brave, Arc). They share the same underlying engine, so Web Bluetooth is present.
- Chrome on Android phones and tablets. This is the one mobile platform where live Capture works.
Keep the browser reasonably current. Web Bluetooth support has been stable for years, but an old build can carry pairing bugs that a recent one has fixed.
What does not work
- Safari, on macOS and iOS, does not implement Web Bluetooth. The picker will find nothing.
- Firefox does not implement Web Bluetooth on any platform.
- iPhone and iPad, in any browser. Every browser on iOS and iPadOS is required to use Apple's WebKit engine underneath, and WebKit has no Web Bluetooth. Installing Chrome or Edge from the App Store does not change this, because those apps are WebKit wrappers on iOS, not the Chromium engine. There is no iPhone or iPad configuration that supports live Capture today.
If your only tablet is an iPad, you have two options: run Capture from a nearby laptop or an Android tablet, or use file upload instead. Upload takes a recording your device or its own app produced and runs it through the same signal pipeline and the same metrics as a live capture. You lose the live curve during the effort, not the analysis.
Permissions and connection
- The site must be served over HTTPS for Web Bluetooth to be available. The hosted app already is, so this only matters if someone points you at a non-secure copy.
- The first time you open the device picker, the browser asks for permission to use Bluetooth. Grant it. If you dismissed it earlier, you may need to re-enable Bluetooth access for the site in the browser's site settings.
- Bluetooth must be on at the operating system level, and on Android the browser also needs Location permission, because scanning for nearby Bluetooth devices is gated behind it on that platform. Granting Location does not share your location with the app; it is the permission Android happens to attach to Bluetooth scanning.
A reliable clinic setup
The most dependable arrangement for a busy clinic is a laptop or Android tablet running current Chrome or Edge, kept within a few feet of the patient during the effort. That machine pairs once per session and holds the connection across pages, so you are not re-pairing between Capture and IsoForge.
What to do next
- If the picker is not finding a device you know is on, the problem is usually advertising state or distance rather than browser support. Work through When a device won't pair or stays disconnected.
- If you are setting up a machine for the first time, open Capture and confirm the picker appears at all. If it does, your browser supports Web Bluetooth and the rest is device pairing.