public class WorkoutManager

Starts and tracks workout recordings.

Obtain one from Health.getWorkouts(); it is never null.

Check what the platform will actually do for you

Two capabilities that are easy to conflate, and that this API keeps separate on purpose:

• isLiveSessionSupported() – the OS runs a real session, keeping the app alive while it records.
• isSensorCollectionSupported() – the OS also gathers heart rate and energy into that session by itself.

Both are false on every platform in this release. No port implements an OS-owned session yet, so every workout is recorded: the framework keeps the clock and the rollup, and persists what you feed it when the session ends. That is exactly the flow Google documents for Android phones, and it is why these are queryable facts rather than assumptions – code that branches on them today keeps working unchanged when a port starts answering true.

Where the second is false, a workout records only what you feed it. Building a UI with a live heart-rate readout without checking would produce an app that works on a watch and shows a permanent dash on a phone.

WorkoutManager workouts = Health.getInstance().getWorkouts();
workouts.startSession(new WorkoutConfiguration()
        .setActivityType(WorkoutActivityType.RUNNING)
        .setLocationType(WorkoutLocationType.OUTDOOR))
    .onResult((session, err) -> {
        if (err != null) { Log.e(err); return; }
        // startSession() only builds the session; this starts the
        // clock and moves it to RUNNING, and until it is called
        // addSamples() and end() fail with SESSION_STATE.
        session.start();
        if (!session.isLive()) {
            status.setText("Recording - connect a strap for heart rate");
        }
    });