Pebble Watch software is now open source

📝 Discussion Summary (Click to expand)

The three most prevalent themes in the Hacker News discussion are:

1. Scrutiny Over the "100% Open Source" Claim

Many users debated the meaning and accuracy of the claim that Pebble software is now "100% Open Source," focusing on the presence of non-free binary blobs required for certain hardware features (like the heart rate sensor).

Supporting Quote: One user, critical of the headline, stated: "Then say 'Pebble Watch Software written by Core Devices Is Now 100% Open Source', or 'Pebble mobile app open sourced' (that seems to be the major actual change?), or something like that. The thing they've actually done should be commended, but that doesn't mean ignoring that they've chosen to make a claim in the headline that isn't actually true." (yjftsjthsd-h)
Supporting Quote: Countering this, another user argued that the non-free components are optional: "If they are not mandatory it's 100%. Otherwise according to your standard, Debian is not 100% free software either." (darkwater)

2. The Fallout and Resolution of the Rebble Conflict

There was significant discussion regarding the recent public dispute between Core Devices (Pebble revival team) and Rebble (the community maintaining the original watch ecosystem), with most users viewing the recent announcements (especially the open-sourcing of the app) as a positive resolution favoring community flexibility.

Supporting Quote: One user offered praise for the compromise enabled by the new strategy: "Love to see this! I personally find this incredibly exciting. There is a major death of hardware out there that is user-respecting and hacker-friendly, and it warms my heart immensely to see such committments." (freedomben)
Supporting Quote: Another user reflected on Rebble's reaction: "It seems like Rebble (the board) really overplayed their hand." (infotainment)

3. High Value Placed on Repairability and Longevity (Especially Battery Life)

Users expressed strong excitement about physical design choices that promote longevity, particularly making the battery user-replaceable by utilizing a screwed-on back cover, contrasting this with the sealed designs common in modern wearables.

Supporting Quote: A user affirmed their purchasing decision based on this feature: "I'm excited that the back will screw off so we can replace the battery. I'm curious about waterproofing. Will that hold?" (apparent)
Supporting Quote: Another user noted the appeal of tangible hardware features over software optimization: "I can never go back to a 2 day battery life for a watch, even if my 5 year old iPhone technically can’t make it through half a day of use…." (krabizzwainch)

🚀 Project Ideas

Firmware/App Repository Aggregation Service (F-Droid for Wearables)

Summary

A centralized service and accompanying open-source companion app that allows users to browse, install, and auto-update third-party Pebble apps and watchfaces from multiple, independently hosted repositories (like Rebble's or custom user repos).
Solves the fragmentation and reliance on a single entity for the app ecosystem, directly addressing the community desire for resilience and openness following the Core Devices/Rebble situation.

Details

Key	Value
Target Audience	Pebble 2/Time 2 owners, community developers, open-source advocates concerned about app store centralization ("infotainment: Hoping this can open the door for some kind of 'F-Droid for Pebble'").
Core Feature	Multi-feed application repository client built into the companion mobile app, supporting automated builds/updates from source where possible.
Tech Stack	Mobile App (Kotlin Multiplatform, leveraging the existing Core Devices KMP app structure), Backend/Repository indexing service (Go or Python for robustness and simplicity).
Difficulty	Medium
Monetization	Hobby

Notes

HN commenters explicitly desire an "F-Droid for Pebble" ("infotainment").
Core Devices explicitly introduced multi-feed support, making this the logical next step for community-driven resilience.
This project positions itself as the necessary neutral layer between device manufacturers and various community storefronts (Rebble, Core).

The "FOSS-Minimum" PebbleOS Recompilation Toolkit

Summary

An automated, scriptable toolchain that takes the newly open-sourced PebbleOS source code and compiles it down to a functional firmware image excluding all known non-free/binary blobs (HR sensor, Memfault, Speech API).
Directly targets the debate over the "100% open source" claim by providing users with a guaranteed, auditable, FOSS-only firmware build, proving the "core stack" is usable independently ("yjftsjthsd-h: Then say 'Pebble Watch Software written by Core Devices Is Now 100% Open Source'").

Details

Key	Value
Target Audience	Security purists, FOSS activists, users who distrust third-party/optional proprietary components ("bayindirh: ...branding it as 100% Open Source is not.").
Core Feature	Automated build scripts (Makefile/CMake wrapper) that conditionally link/exclude proprietary libraries and provide a verification hash for the resulting firmware image.
Tech Stack	Build Toolchain (GCC/Clang for ARM Cortex-M targets), Shell scripting for automation, Documentation outlining the trade-offs (e.g., "You lose HR tracking").
Difficulty	High (Requires deep embedded toolchain knowledge and maintaining dependency excision across updates).
Monetization	Hobby

Notes

It validates Core Devices' claim that the core stack works without blobs, while simultaneously catering to users who demand 100% FOSS compliance.
Solving the firmware blob issue is a recurring, complex topic on HN, signaling high engagement potential for a pragmatic solution.

Wearable Repairability Documentation & Gasket/Component Subscription Service

Summary

A comprehensive, iFixit-style documentation hub specifically for the Pebble Time 2 and other modern repairable hardware, focusing on procedures like battery replacement, button repair, and waterproofing best practices.
Complemented by a subscription service that provides pre-sourced, correctly specified replacement components (e.g., specific gaskets, replacement screws, replacement non-HR PCBs).
Addresses user excitement over repairability ("apparent: I'm excited that the back will screw off so we can replace the battery") while mitigating waterproofing concerns ("erohead: that gasket... should be reusable, but nothing's guaranteed").

Details

Key	Value
Target Audience	Current Pebble Time 2 owners, users who value longevity and repairability ("ortusdux: I really like the look of the Pixel watch 4's approach to this").
Core Feature	High-quality, step-by-step photo/video guides combined with an integrated subscription model for consumables needed during maintenance.
Tech Stack	Documentation Platform (Headless CMS or Static Site Generator like Hugo/Jekyll), E-commerce integration (Stripe/Shopify for the subscription component).
Difficulty	Medium
Monetization	Hobby

Notes

Addresses the tangible hardware concerns raised: battery serviceability and maintaining water resistance.
Taps into the broader HN sentiment regarding planned obsolescence and the desire for user-serviceable hardware ("bredren: I see a future where FOSS designs for consumer products compete with commercial releases").