• A small technical note: on the backend, Wristla uses Tesla Fleet API for commands and Fleet Telemetry to get fresher vehicle status. This approach reduces reliance on constant active polling and allows wake-ups to be handled more carefully.

  • One practical limitation I ran into with Connect IQ is the lack of shared local storage between products from the same developer. In my case, the app may already have fresh Tesla data in its own sandbox, but it has no way to pass that data to the watch face. Because of that, the watch face has to wait at least 5 minutes for its background refresh to run, even though the data is already available locally on the watch. For paired products like an app and a watch face, this feels like a real platform limitation.