Tag: Rust

  • Whoop alternative: Open-source app kills expensive subscriptions

    Whoop alternative: Open-source app kills expensive subscriptions

    Key Takeaway

    – Goose is an open-source app that pulls health data from a Whoop 5.0 tracker entirely offline, bypassing the subscription.
    – It operates locally on iOS using SwiftUI for the interface and Rust for processing Bluetooth data packets.
    – The project is a raw, pre-alpha proof of concept with lag, iOS-only support, and no compatibility with older Whoop models.
    – An alternative is Google’s Fitbit Air, a subscription-light competitor to Whoop.


    Hardware subscription fatigue hits a boiling point

    Consumers are increasingly tired of buying a premium piece of technology, only to find that there own biometric data is locked behind a mandatory monthly paywall. We saw this friction recently when Oura Ring users began looking for subscription-free workarounds to access there data, and now the movement has arrived for screenless fitness trackers.

    Whoop’s business model under fire

    The primary target this time is Whoop. From it’s inception, the company has built its business model on the idea that the wearable is useless without an active subscription. If you stop paying the monthly fee, the device on your wrist essentially becomes a paperweight, leaving customers frustrated with there lack of control.

    An open-source challenger emerges

    However, an independent developer named Bennet is challenging that paradigm with an open-source project called Goose, which aims to see just how much utility can be squeezed out of the tracker without giving Whoop another dime. Announced recently on X, the project is a raw, pre-alpha proof of concept. It is far from a polished consumer application, but it successfully achieves the unthinkable: it pulls and displays health data directly from the wearable entirely offline.

    How the app bypasses the paywall

    I had a look at the GitHub files, and the app eliminates the need for external servers by operating as a local-first application. When the fitness band transmits data, the app uses standard Bluetooth connection protocols on your phone to intercept the raw data packets right out of the air, giving users back there own information without ongoing fees.

    Technical architecture and performance

    To handle this constant stream of data without melting your phone’s battery, the project uses a hybrid architecture. The user interface is built using SwiftUI, giving you a clean dashboard for tracking sleep, strain, and recovery metrics. Meanwhile, the heavy lifting of parsing and decoding those raw Bluetooth packets is handed off to a high-performance backend written in Rust. The two sides communicate locally on the device, ensuring your health data never leaves your phone, which is a big win for privacy.

    Limitations and current state

    Now, while the achievement is impressive, the project is still a developer’s playground rather than a viable alternative for the average user. Because the code is unoptimized, early builds suffer from quite a lot of processing lag. The app is also currently built exclusively for iOS devices, meaning Android users are locked out for the time being. There’s also no support for older hardware, and the app only works with the latest Whoop 5.0 model. If you don’t feel like trying out the app, Google recently launched Fitbit Air, a direct competitor to Whoop that doesn’t rely heavily on subscriptions. There’s also a Google Health premium subscription if you need more information.

    • Goose is an open-source project that bypasses Whoop’s subscription.
    • It uses Bluetooth to intercept data from the wearable directly.
    • The app is currently only available for iOS and Whoop 5.0.
    • Performance issues and processing lag are present in early builds.
    • Google’s Fitbit Air offers a subscription-free alternative.
    Sources
  • Debian APT Requires Rust Toolchain from May 2026 for Legacy Ports

    Debian APT Requires Rust Toolchain from May 2026 for Legacy Ports

    Key Takeaways

    1. Debian’s APT tool will begin using Rust-based code by May 2026, creating a dependency on the Rust toolchain.
    2. The change aims to improve memory safety and long-term maintainability of Debian’s core components, with potential impacts on architectures lacking Rust support.
    3. Community reactions are mixed, with some viewing the change as a careful improvement while others worry about compatibility issues for older architectures.
    4. The integration of Rust aligns with broader trends in open-source software aimed at enhancing security and reliability in low-level applications.
    5. Discussions among developers highlight concerns about long-term support for niche architectures, affecting strategies for hardware testing and specialized development.


    Debian developers have announced a significant change in the core package manager of the project. A message from long-time contributor Julian Andres Klode shared on the official Debian developer mailing list states that the APT tool will start using Rust-based code no sooner than May 2026, which will create a hard dependency on the Rust toolchain.

    Aiming for Safety and Maintainability

    This change aims to enhance memory safety and ensure the long-term maintainability of one of Debian’s key system components. Klode mentioned that this update will mainly impact architectures and derivative distributions that lack a functioning Rust toolchain. He cautioned that ports that cannot support Rust might need to be discontinued if compatibility issues aren’t resolved in a timely manner.

    Community Reactions and Concerns

    The announcement, reported by Linuxiac and broadly discussed in Reddit’s r/Linux community, has been characterized by users as a careful, step-by-step improvement instead of a complete overhaul. Some users pointed out that legacy ports such as m68k and SH-4 will likely remain unaffected, as they are no longer officially supported by Debian. The news has also made its way to X (formerly Twitter), where developers and open-source advocates have engaged in similar conversations about Debian’s gradual incorporation of Rust-based components.

    Aligning with Open-Source Trends

    Integrating Rust into APT fits within a broader trend in open-source software, as major Linux distributions and kernel subsystems increasingly adopt Rust to bolster security and reliability in low-level software applications. This transition is also projected to influence build environments, CI pipelines, and driver packaging processes across embedded and industrial platforms where Rust has not yet been integrated into the default toolchain.

    Klode expressed that the project must adopt modern tools instead of trying to fit new software onto outdated hardware platforms. This viewpoint has sparked conversations among port maintainers about long-term support and sustainability.

    Mixed Feelings in the Community

    Discussions within the community have shown a mix of optimism and skepticism. Some users appreciate the emphasis on safety and modernization, while others voice worries over compatibility issues and the possible discontinuation of older architectures.

    For hardware testers and Linux maintainers, this transition could reshape long-term support strategies, especially for niche architectures that continue to be utilized in benchmarking, retrocomputing, and specialized hardware development.

    Source:
    Link