HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
google
pebble
C2025–2025
google / pebble

pebble

This is the latest version of the internal repository from Pebble Technology providing the software to run on Pebble watches. Proprietary source code has been removed from this repository and it will not compile as-is. This is for information only.

12Distinct people
15Mentions
0Explicit recommenders
5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This is the latest version of the internal repository from Pebble Technology providing the software to run on Pebble watches. Proprietary source code has been removed from this repository and it will not compile as-is. This is for information only.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week15 dated mentions

Observed mentions: 2025-01-27 20:03:22 UTC to 2025-08-09 07:24:11 UTC. Weeks start Monday, UTC.

0510152025-01-27 00:00:00 UTC to 2025-02-03 00:00:00 UTC (exclusive): 14 mentions; 3 submissions, 11 commentsJan 272025-02-03 00:00:00 UTC to 2025-02-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-10 00:00:00 UTC to 2025-02-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 00:00:00 UTC to 2025-02-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-24 00:00:00 UTC to 2025-03-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-03 00:00:00 UTC to 2025-03-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-10 00:00:00 UTC to 2025-03-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-17 00:00:00 UTC to 2025-03-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-24 00:00:00 UTC to 2025-03-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-31 00:00:00 UTC to 2025-04-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-07 00:00:00 UTC to 2025-04-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-14 00:00:00 UTC to 2025-04-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-21 00:00:00 UTC to 2025-04-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-28 00:00:00 UTC to 2025-05-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 282025-05-05 00:00:00 UTC to 2025-05-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-12 00:00:00 UTC to 2025-05-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-19 00:00:00 UTC to 2025-05-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-26 00:00:00 UTC to 2025-06-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-02 00:00:00 UTC to 2025-06-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-09 00:00:00 UTC to 2025-06-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-16 00:00:00 UTC to 2025-06-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-23 00:00:00 UTC to 2025-06-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-30 00:00:00 UTC to 2025-07-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-07 00:00:00 UTC to 2025-07-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-14 00:00:00 UTC to 2025-07-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-21 00:00:00 UTC to 2025-07-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-28 00:00:00 UTC to 2025-08-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-04 00:00:00 UTC to 2025-08-11 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 4

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 272025-01-27 00:00:00 UTC2025-02-03 00:00:00 UTC14311
Feb 32025-02-03 00:00:00 UTC2025-02-10 00:00:00 UTC000
Feb 102025-02-10 00:00:00 UTC2025-02-17 00:00:00 UTC000
Feb 172025-02-17 00:00:00 UTC2025-02-24 00:00:00 UTC000
Feb 242025-02-24 00:00:00 UTC2025-03-03 00:00:00 UTC000
Mar 32025-03-03 00:00:00 UTC2025-03-10 00:00:00 UTC000
Mar 102025-03-10 00:00:00 UTC2025-03-17 00:00:00 UTC000
Mar 172025-03-17 00:00:00 UTC2025-03-24 00:00:00 UTC000
Mar 242025-03-24 00:00:00 UTC2025-03-31 00:00:00 UTC000
Mar 312025-03-31 00:00:00 UTC2025-04-07 00:00:00 UTC000
Apr 72025-04-07 00:00:00 UTC2025-04-14 00:00:00 UTC000
Apr 142025-04-14 00:00:00 UTC2025-04-21 00:00:00 UTC000
Apr 212025-04-21 00:00:00 UTC2025-04-28 00:00:00 UTC000
Apr 282025-04-28 00:00:00 UTC2025-05-05 00:00:00 UTC000
May 52025-05-05 00:00:00 UTC2025-05-12 00:00:00 UTC000
May 122025-05-12 00:00:00 UTC2025-05-19 00:00:00 UTC000
May 192025-05-19 00:00:00 UTC2025-05-26 00:00:00 UTC000
May 262025-05-26 00:00:00 UTC2025-06-02 00:00:00 UTC000
Jun 22025-06-02 00:00:00 UTC2025-06-09 00:00:00 UTC000
Jun 92025-06-09 00:00:00 UTC2025-06-16 00:00:00 UTC000
Jun 162025-06-16 00:00:00 UTC2025-06-23 00:00:00 UTC000
Jun 232025-06-23 00:00:00 UTC2025-06-30 00:00:00 UTC000
Jun 302025-06-30 00:00:00 UTC2025-07-07 00:00:00 UTC000
Jul 72025-07-07 00:00:00 UTC2025-07-14 00:00:00 UTC000
Jul 142025-07-14 00:00:00 UTC2025-07-21 00:00:00 UTC000
Jul 212025-07-21 00:00:00 UTC2025-07-28 00:00:00 UTC000
Jul 282025-07-28 00:00:00 UTC2025-08-04 00:00:00 UTC000
Aug 42025-08-04 00:00:00 UTC2025-08-11 00:00:00 UTC101

What Hacker News says

15 sources
Still "daily driving" my burgundy[0] Pebble... hoodie/fleece! (It's impressive quality company swag.) @erohead, when you're at the stage of needing a kick-ass RePebble SDK developed & supported again[1], you know where to find me. :) lol @ the FAQ: "Aren’t you the guy who screwed this up last time?" Also, while looking through the repo, I'd totally forgotten the alphabetically ordered fast-food themed release code names which included the "Kiwiburger" (a global chain's local product that contains neither the bird nor the fruit) that I now wonder how many people it confused. :) The "Kiwiburger" code name release also happened to coincide with the inclusion of "Simplicity" (a watch face I designed & implemented) as one of the standard faces shipped with each Pebble watch by default. I was particularly proud of the inclusion of "Simplicity"-
Read the rest
-especially when Engadget subsequently said it was "...sure to make minimalists happy" which was what I was aiming for. (I seem to recall it also gave me the opportunity to say "Hey, I designed that watch face!" when I saw a Pebble watch on display at an airport duty free store once. :D ) Anyway, I should probably get this memoir off to the publishers[3]. :) ---- [0] Oh, sorry, apparently it's cranberry. :) [1] I helped develop & support the very well-received initial SDK that enabled "Hacker Backers" and others to create their first Pebble watch faces & watch apps. It was quite an experience to be working on the SDK remotely from New Zealand[1a] and then have the initial public SDK release immediately covered by the likes of TechCrunch[1b], The Verge[1c] and Engadget. (An SDK! :D ) There was a lot of pent-up interest/demand for the SDK so it was really great to see how excited people were when they successfully implemented their first watch face or (later) watch app. In many/most cases this was the person's first experience of anything approaching "embedded" programming--there was a lot of effort put into removing as many barriers from the development experience as possible, so it was really rewarding to see people succeed. (Initially the process still required a locally installed embedded development environment, so even with all the effort invested to reduce barriers it still wasn't a simple process but turns out people were really motivated. :) It also turned out that I was really motivated to script/automate & simplify the process simply to avoid having to write documentation covering a more manual process. :D ) It was also super cool to see people then develop other (particularly web-based) tools to enable people with even less technical experience/skill to still create e.g. a custom watch face with their favourite sports team logo or the family dog featured on it. I mention all this in part to reminisce and in part to convey some of what the mood around Pebble was at the time for those who may not have been around *cough* nearly fifteen years ago and were wondering what (part of) the "big deal" was... An early version of the SDK documentation is archived here: https://web.archive.org/web/20130415083512/http://developer.... [1a] via this HN Jobs post IIRC: https://news.ycombinator.com/item?id=4132957 [1b] https://techcrunch.com/2013/04/12/pebble-watchface-sdk-now-a... [1c] https://www.theverge.com/2013/4/15/4228700/pebble-tetris-clo... [2] https://github.com/google/pebble/blob/3b927684809fba173ee540... [3] Okay, one last note: interesting to observe it was suddenly a lot more difficult to find Pebble/SDK related links from ~2012/2013 due to the amount of coverage the PebbleOS/RePebble announcements seem to have received. Read into that what you wish. :)
In We're bringing Pebble back
For visibility (via comment by 1337shadow @ https://news.ycombinator.com/item?id=42848245): ---- > Instead, we took a more direct route - I asked friends at Google (which bought Fitbit, which had bought Pebble’s IP) if they could open source PebbleOS. They said yes! Over the last year, a team inside Google (including some amazing ex-Pebblers turned Googlers) has been working on this. And today is the day - the source code for PebbleOS is now available at github.com/google/pebble (see their blog post). https://ericmigi.com/blog/why-were-bringing-pebble-back ----
In Google open-sources the Pebble OS
Unfortunately, as mentioned in another comment, the Bluetooth stack is apparently one of the items that is not included in the source release[0]: Some parts of the firmware have been removed for licensing reasons, including: [...] - The Bluetooth stack, except for a stub that will function in an emulator [...] Which suggests that the Bluetooth stack wasn't entirely of their own making, so perhaps any of Pebble's own additions were too intertwined (e.g. gave away too much Bluetooth stack vendor proprietary API info) to be easily separated? [0] https://github.com/google/pebble/blob/3b927684809fba173ee540...
In We're bringing Pebble back
> Instead, we took a more direct route - I asked friends at Google (which bought Fitbit, which had bought Pebble’s IP) if they could open source PebbleOS. They said yes! Over the last year, a team inside Google (including some amazing ex-Pebblers turned Googlers) has been working on this. And today is the day - the source code for PebbleOS is now available at github.com/google/pebble (see their blog post). https://ericmigi.com/blog/why-were-bringing-pebble-back
In Google open-sources the Pebble OS

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.