Summary
- Tensr wins on: putting compatible sensor sets alongside your wider strength-training history, a Free Forever local core, and open exports for your own agents. Progressor owners can use their existing sensor with suitable setups.
- Tindeq’s own app wins on: a manufacturer-provided workflow for its instrument, with iOS and Android support. Tindeq also publishes its Bluetooth interface; openness is a shared strength. Tindeq’s Progressor
- The tradeoff: this is a software-workflow choice around the same hardware. Tensr does not improve the load cell, and our documented capture-timing limitation matters when interpreting time-dependent metrics.
If you bought a Tindeq Progressor for climbing or a particular strength test, you already own the important part of a force-recording setup: the instrument. Another app does not improve the load cell simply by drawing a different chart.
Tindeq supplies its own app and publishes a Bluetooth interface for developers. Its current Progressor 200 page lists an 80 Hz sampling frequency and describes support for its iOS and Android app. That combination makes the hardware useful both within Tindeq’s workflow and as an instrument another application can communicate with. Progressor 200, Tindeq’s Bluetooth API
Tensr’s proposition is another workflow for that sensor, rather than a reason to dismiss the one you already use.
Keep the app that fits the session
If Tindeq’s app supports the assessment or training routine you want, that is a good reason to keep using it. The manufacturer has built an application around its instrument, and a consistent testing workflow has value of its own.
Tindeq’s product material describes strength assessment across muscle groups, not just climbing. The case for another application starts with the workflow you want, rather than assuming the manufacturer’s app cannot serve it.
The alternative question is whether you want the sensor’s readings inside a broader strength-training record: which movement you performed, where the set belongs in a session, and what related training you did before or afterward. That is an application-context question, not a contest over the hardware.
One instrument can be useful with different applications on different sessions. That does not mean both applications need to hold a live Bluetooth connection to it at the same time.
The load path matters more than the movement name
Consider a compatible cable or band arrangement with the sensor inline. The recording describes the external tension passing through that attachment. Keeping the arrangement consistent gives later recordings a more interpretable relationship to it.
Move the sensor to another location, change the cable routing, or alter the movement and the meaning can change. Being able to attach the instrument is not evidence that every attachment is an appropriate or manufacturer-supported use. The hardware’s specifications and intended loading still apply.
Our approach also has a clear absence: an ordinary barbell squat or bench press does not route its load through the inline sensor. Tensr cannot supply the missing force trace because the exercise is in a routine.
For suitable movements, the added record can be useful even if it begins with one repeated task. You can inspect how the force changed through the set and keep the setup and movement alongside it. You do not need to instrument an entire workout to ask one specific question.
The application has to preserve the instrument’s information
Hardware capability and recording fidelity are separate. Receiving many force values per second does not establish that an application retained their timing correctly.
Our timestamp investigation found that the Progressor supplied device timestamps that our capture paths did not carry through into the recorded timeline. That is our software’s responsibility. A different app using the same hardware can produce a different record if it handles timing differently.
The distinction matters most when calculating things that depend on elapsed time or slope. The current capture limitation remains relevant; changing the name on the chart does not repair it.
This is why our case for using an open instrument includes scrutiny of the reader. The load cell, Bluetooth protocol, application timeline, and derived calculation each contribute to the result someone sees.
The useful record survives the session
Tensr keeps local application data and supports a SQLite export containing stored records and recordings. That lets another tool inspect the data when it understands the schema and recording formats. It also leaves you responsible for keeping a copy somewhere useful.
For a Progressor owner, the practical starting point is a workflow question: does keeping a compatible set with the rest of your strength-training history help you understand it? If the manufacturer’s app already answers the question you care about, another interface may add little.
The openness is the advantage to preserve. You can use the sensor for the work it supports and choose software for the session in front of you. Tensr is one of those choices, with its own strengths and limits to examine.
