Google Health Adds an In-Progress Workout Card
Google has announced a Google Health workout card in version 5.13, addressing a visibility gap for automatically tracked exercise on Fitbit Air. The update began rolling out on November 20, 2026. Its confirmed features are specific: show that tracking is underway, let users end it, and provide a workout summary.
That distinction matters for a wearable without a display. Automatic tracking removes the need to start every session manually, but users still need reassurance that recording has begun. A quiet device becomes frustrating when its companion app also leaves the current workout unclear.
Google is addressing that tension through software rather than changing Fitbit Air’s hardware. Pixel Watch and Fitbit Edge provide an alternative with information on the wrist. The question now is how much this phone-based addition improves the experience without making users expect capabilities Google has not announced.
What the Google Health workout card actually changes
According to Google’s 5.13 release details, the new card appears on the mobile app’s Today screen. It applies to automatically tracked exercise from Pixel Watch, Fitbit Air, and Fitbit Edge.
Google describes a card that confirms active tracking and offers a way to stop it and receive the session summary. Both Android and iOS are included. The company says distribution will proceed in phases over the following week, depending on carrier and device.
The confirmed change gives users visibility and an ending control for a workout their device has already detected.
Automatic activity detection means the wearable recognizes exercise without requiring someone to begin recording manually. That convenience creates an interface problem. If the device makes the starting decision, the person wearing it needs some way to inspect that decision.
Consider a walk that starts as an ordinary trip outside and becomes a deliberate exercise session. Someone relying on automatic detection might reasonably want confirmation that the tracker recognized the activity. A visible session indicator answers that immediate question without requiring a completed workout record.
The ending control addresses a different moment. A person can finish exercising while the device continues deciding whether the activity has stopped. Giving the user an explicit way to close the session makes that decision available to them.
Those examples explain the feature’s potential value; they are not claims about tested behavior. Google’s announcement establishes the intended controls. It does not establish how quickly detection appears, how the card behaves during interruptions, or how consistently it works across devices.
The distinction between an app update and a device update also matters. This announcement concerns Google Health version 5.13. Readers should not assume that an older wearable firmware release, or a previous app version, already includes the same behavior.
Likewise, a rollout announcement does not mean every compatible phone receives the feature simultaneously. During phased distribution, different users can encounter different availability without either experience disproving the announcement.
The Google Health workout card therefore represents a concrete addition with a limited, understandable scope. It makes an active recording easier to identify and gives the user a direct route to its conclusion.
What it does beyond that requires closer examination, especially because the complaint that drew attention to the update includes more than basic tracking status.
Fitbit Air’s missing screen makes the app accountable
Google introduced Fitbit Air on May 7, 2026, presenting its screenless design as a way to keep the wearable discreet. The company positioned the phone app as the place to explore information when users want it.
That arrangement shifts responsibility between the device and its software. The wearable can remain unobtrusive because the phone supplies the interface. But the phone experience must then cover moments when information becomes necessary, including during exercise.
Removing the wrist display increases the importance of showing the right information at the right moment in the companion app.
The immediate pressure falls on Google’s product design. Fitbit Air’s appeal depends partly on requiring less interaction. Yet a person should not have to interpret silence as evidence that everything is working correctly.
There is a practical difference between choosing not to look at information and being unable to find it. The first supports a quieter experience. The second introduces uncertainty precisely when the user decides that checking matters.
For a casual walk, that uncertainty might be a minor annoyance. During a deliberate workout, it can become more distracting. Someone who wonders whether a session is recording has to spend attention resolving a question the product created.
A visible indicator offers reassurance without requiring a dense dashboard. That makes it a logical addition to a product built around minimal interaction. The app can acknowledge the current activity while leaving deeper analysis for later.
The stopping control also gives the wearer more authority over an automated process. Automation handles a routine decision, but the person retains a way to intervene. That balance is useful when the system’s interpretation and the user’s intentions diverge.
This does not mean every screenless tracker needs to reproduce a smartwatch interface on a phone. A crowded screen would introduce its own problems. The more useful standard is whether someone can answer the immediate question that brought them into the app.
For Fitbit Air, those questions include whether recording has started and whether the session can be ended deliberately. Google’s announced card addresses both. Questions about exercise intensity, pace, or changing performance require additional information.
The update’s significance therefore comes from its placement in the experience rather than its visual size. A small component can resolve a recurring uncertainty if it appears where users already expect current information.
That is also why this change matters beyond owners who frequently inspect workout statistics. People who prefer minimal interaction still benefit from clear confirmation when they choose to check.
Google’s challenge is to preserve Fitbit Air’s quiet character while making the app responsive to those occasional, intentional checks.
Automatic tracking still needs a visible handoff
The central tension is between automatic recording and visible user control. A system can reduce effort by recognizing exercise itself, but that convenience becomes harder to trust when its current state stays hidden.
A workout has several distinct moments. Someone starts moving, the device identifies activity, the app communicates what is happening, and the user eventually reviews a record. Each transition raises a different question.
The useful mechanism here is a handoff from automatic detection to an activity the user can inspect and end.
The new card occupies the space between detection and the final summary. That space matters because a completed record answers a retrospective question. It tells someone what the system captured after the activity has concluded.
An in-progress indicator answers a present-tense question. It tells the person that tracking is happening now. Even without detailed measurements, that information can remove doubt about whether the device recognized the session.
An ending control then connects the current activity to the eventual record. The person no longer has to rely entirely on the system’s judgment about when recording should finish. They can declare that the exercise is over.
From a design perspective, this is a meaningful form of transparency. It exposes the state of an automated process without requiring the user to manage every part of that process.
However, transparency has layers. Knowing that recording is active differs from knowing what measurements the device is collecting. Both differ from knowing how accurately the final record represents the exercise.
The announcement addresses the first layer and provides a control over the session’s endpoint. It does not, by itself, establish improvements in measurement accuracy or detection speed. Those remain separate questions.
This separation helps explain why a seemingly modest app component can matter without changing the underlying sensing technology. Better access to a system’s state can improve usability even when the measurement process stays the same.
It also prevents an exaggerated interpretation of the update. A visible session does not automatically imply a complete live training interface. The card’s presence and its contents need separate evaluation.
For people who rely on automatic recording, the strongest outcome would be a predictable relationship between activity and acknowledgment. They begin exercising, later check the app, and find an understandable account of what the device is doing.
The opposite experience would weaken the benefit. An inconsistent indicator would make people investigate the interface itself, replacing one uncertainty with another. That is an evaluation criterion, not evidence that the feature currently behaves inconsistently.
The same reasoning applies to ending a workout. A clear control should produce an understandable result, so the person knows the session has closed and where its record belongs.
This is the standard against which the update deserves assessment: whether automatic tracking becomes easier to understand and supervise during an ordinary workout.
A phone card and a wrist display solve different problems
Fitbit Air’s software improvement does not erase the distinction between a screenless wearable and a watch. It changes what a person can inspect on the phone, while a wrist display changes where that inspection happens.
Google itself describes Fitbit Edge as offering on-wrist guidance. Its product positioning places Edge between Fitbit Air’s minimal design and Pixel Watch’s broader capabilities.
Apple offers another established reference. Its workout progress views let Apple Watch users inspect measurements during exercise, including elapsed time, distance, pace, and heart rate.
The relevant comparison is access during exercise: checking a phone and glancing at a wrist create different experiences.
For someone walking with a phone readily available, opening an app can be an acceptable way to check recording status. For someone whose phone remains in a bag, that same action requires a more deliberate interruption.
A treadmill creates another possible context. A phone might already be positioned nearby, making its screen accessible. During another activity, reaching for it might be inconvenient. The usefulness of the interface depends partly on where the phone is.
These are differences in interaction, not evidence that one category universally serves people better. Someone can value a wearable’s lack of a screen while accepting occasional phone checks. Another person can prioritize immediate access to workout information.
The new card strengthens the first arrangement if it makes those occasional checks clearer. It does not remove the physical step of accessing the phone. That remains a consequence of the hardware choice.
Nor does a watch comparison require pretending that every device offers identical measurements or exercise features. The narrower point is sufficient: information available on the wrist has a different access cost from information available in a companion app.
For Google, this creates a product boundary worth maintaining clearly. Fitbit Air should have a complete, understandable experience for its intended use. More visible hardware can still offer advantages for people who want frequent feedback.
The card therefore should not be evaluated as an attempt to turn Fitbit Air into Pixel Watch. A better question is whether it removes an unnecessary weakness from the screenless experience while preserving its basic character.
This also limits what can reasonably be inferred about competitive pressure. The announcement does not demonstrate that customers are switching between brands or that another company must respond. No verified adoption evidence establishes those outcomes.
The direct pressure is on Google to make its own minimal interface feel dependable. Apple Watch provides a useful reference for immediate feedback, rather than proof of a new competitive contest.
For readers choosing between these approaches, the distinction is practical. Decide whether the occasional confirmation available through a phone matches the way you exercise, or whether wrist-level information is central to the experience.
Tracking confirmation is not confirmed live workout data
The original complaint has an important second layer. A person might want confirmation that exercise is recording, but also want to inspect changing measurements during the session.
In his November 20 coverage of the in-progress workout card, 9to5Google’s Ben Schoon described wanting access to workout progress. His examples included heart rate and steps during walks and treadmill exercise.
Schoon also said the exact appearance of the new card was not yet known to him. That qualification limits how confidently anyone can describe the resulting experience.
Google’s announced controls address recording visibility, but the available description does not establish a live metrics dashboard.
This is the main reason to treat claims that the complaint is completely fixed with care. The announced feature answers whether a device is tracking exercise. The broader complaint also asks what is happening within that exercise.
Those are related needs, but they are not interchangeable. A status indicator can be useful even when it provides no changing measurements. A person seeking detailed feedback can still find that insufficient.
The Google Health workout card should therefore be described through its confirmed functions. It indicates an ongoing automatically detected session and provides a way to finish it. Additional claims need evidence from the actual interface or more detailed documentation.
That includes claims about live heart rate, steps, distance, pace, or elapsed time. None should be inferred merely because those measurements would make sense in the available space.
The same restraint applies to the card’s layout. Without verified evidence, there is no basis for describing particular buttons, colors, charts, animations, or arrangements. An imagined interface can easily become a false expectation.
There is also no announced basis for assuming a lock-screen presentation or a persistent notification. The documented location is the app’s Today screen. Other surfaces would require their own confirmation.
Detection behavior deserves equal caution. The presence of an in-progress card does not establish that workouts are recognized immediately. It does not quantify delays, identify every supported activity, or prove consistent behavior under every condition.
Similarly, a stop control does not establish the presence of pause, resume, or editing functions within that card. Those are distinct interactions. Readers should not have to discover the difference after updating.
A careful account can still recognize the improvement. Explicit status and user control are useful additions on their own. Their value does not depend on presenting them as a broader set of capabilities.
The fairest reading is that Google has announced a meaningful response to part of the screenless workout problem. Whether it satisfies the complete complaint depends on what users can actually see and do.
That uncertainty is narrow enough to test through ordinary use. It calls for observations of the shipping feature, rather than speculation about what a future revision might include.
The next test is the workout experience people receive
The announcement creates a clear sequence for evaluating the update. Availability comes first, the shipping interface comes next, and repeated use establishes whether the experience holds together.
The strongest evidence will be a consistent journey from detected exercise to visible status and an intentionally completed session.
First, watch whether the phased rollout delivers the feature across the announced Android and iOS versions. Early differences in availability are compatible with a staged release. Persistent confusion after distribution would raise a different question about access and communication.
This signal establishes whether people can evaluate the feature at all. A release description provides the intended behavior, but the benefit begins when eligible users receive it. Availability should be distinguished from satisfaction.
Second, watch what the card actually displays. Verified screenshots and detailed observations can establish whether it provides only tracking status or includes additional workout information. This is the evidence needed to assess the broader visibility complaint.
If changing measurements appear, they would support a stronger conclusion about during-workout usefulness. If the interface remains limited to confirmation and stopping, its contribution should be described within that narrower scope.
Either outcome can still represent progress. The difference affects who benefits most. Someone seeking reassurance about recording has a different requirement from someone monitoring performance throughout a session.
Third, watch the complete experience during repeated, automatically detected workouts. Useful observations should connect the appearance of the activity, the ending action, and the resulting summary. An isolated screenshot cannot establish how those transitions behave.
Consistency would strengthen the argument that Google has made automatic recording easier to supervise. Repeated uncertainty about the current session would weaken it, even if the card looks clear when it appears.
These are more informative signals than broad claims about the future of wearable technology. They connect directly to the friction that prompted interest in this release. They also avoid inventing a product roadmap.
The update does not need an industry-changing narrative to justify attention. It targets a familiar problem: a device can be collecting information while giving its owner too little understanding of the current activity.
For Fitbit Air, resolving that problem would support the original hardware choice. A quiet wearable works better when its companion software responds clearly at the moments someone chooses to engage.
For readers following the rollout, focus on the workout experience you receive rather than the promise implied by a headline. Check whether an automatically detected session becomes visible, whether its ending is understandable, and whether the resulting summary matches your expectations. Treat any additional measurements as features to verify, not assumptions to carry forward. If recording confirmation was your main frustration, this release targets that need directly. If you wanted continuous workout feedback, inspect the actual interface before deciding the problem is solved. The Google Health workout card has a clear purpose; the useful next step is determining how completely that purpose matches the information you need while exercising.



