For a long time, the general consensus among Wear OS watch users was that the platform wasn’t all that good. Stutters, slowness, weird bugs, frequent disconnects from the phone, and the absence of a properly-integrated fitness and health service were among the chief reasons for that thinking. Not to mention Google’s on-again-off-again relationship with the platform, with updates one day and neglect the next.
Then the Google-Samsung partnership and the Galaxy Watch 4 happened, signaling Google’s long-term commitment to Wear OS on an abstract level and the platform’s not-so-suckiness on a concrete level. It was one of the first examples that watches running Google’s software could actually be smooth, responsive, and competitive against the best of the best smartwatches.
The foundation for an agentic control plane in life sciences includes four levels of capabilities working together: Infrastructure provides the […]
How teams are building on Snowflake Postgres The Snowflake Online Feature Store is just one example. Companies across the globe […]
Before the spark In early 2025, Snowflake’s marketing organization probably looked pretty similar to its peers in the tech space […]