Eric Migicovsky still wears his Pebble. Thirteen years after he founded the wearables company and found huge success on Kickstarter<\/a>, and more than eight years after he sold the company to Fitbit<\/a>, which was then acquired by Google<\/a>, Migicovsky\u2019s watch still works. (In case you\u2019re wondering: when I saw him at CES a few weeks ago, he appeared to be wearing a white Pebble Time Round<\/a> model. But he has a box full of them at home.) It hasn\u2019t gotten a software update since December 2016, though, and he\u2019s been worried for a while that it will eventually stop getting notifications, or connecting to his phone, or run into some other show-stopping problem.<\/p>\n<\/div>\n Rather than buy another smartwatch, Migicovsky decided to try and get Pebble going again. He sold his most recent startup<\/a>, a messaging app called Beeper<\/a>, to Automattic last year and left the company in the fall. Since then, he\u2019d thought about starting a Pebble-like product from scratch, figuring it\u2019d be easier to do the same thing again a second time. \u201cBut then I was like, what if I just asked Google to open-source the operating system<\/em>?\u201d he says. It felt like a long shot, but he knew the code was just sitting dormant inside Mountain View somewhere.\u00a0So he asked. A few times.<\/p>\n<\/div>\n To Migicovsky\u2019s surprise, Google agreed to release Pebble OS to the public. As of Monday, all the Pebble firmware is available on GitHub<\/a>, and Migicovsky is starting a company to pick up where he left off.<\/p>\n<\/div>\n The company \u2014\u00a0which can\u2019t be named Pebble because Google still owns that \u2014\u00a0doesn\u2019t have a name yet. For now, Migicovsky is hosting a waitlist and news signup at a website called RePebble<\/a>. Later this year, once the company has a name and access to all that Pebble software, the plan is to start shipping new wearables that look, feel, and work like the Pebbles of old.<\/p>\n<\/div>\n The reason, Migicovsky tells me, is simple. \u201cI\u2019ve tried literally everything else,\u201d he says, \u201cand nothing else comes close.\u201d Sure, he may just have a very specific set of requirements \u2014 lots of people are clearly happy with what Apple, Garmin, Google, and others are making. But it\u2019s true that there\u2019s been nothing like Pebble since Pebble. \u201cFor the things I want out of it, like a good e-paper screen, long battery life, good and simple user experience, hackable, there\u2019s just nothing.\u201d\u00a0<\/p>\n<\/div>\n The core of Pebble, he says, is a few things. A Pebble should be quirky and fun and should feel like a gadget<\/em> in an important way. It shows notifications, lets you control your music with buttons, lasts a long time, and doesn\u2019t try to do too much. It sounds like Migicovsky might have Pebble-y ambitions beyond smartwatches, but he appears to be starting with smartwatches.<\/p>\n<\/div>\n If that sounds like the old Pebble and not much else, that\u2019s precisely the point. Migicovsky tells me over and over that the plan is not to reinvent Pebble, or AI the bejesus out of the concept, or do whatever else you\u2019d do starting a hardware company in 2025. The fact that the Pebble on his wrist still works, and still works for him, is evidence that maybe Pebble had already finished its job. \u201cWe\u2019re building a spiritual, not successor, but clone of Pebble,\u201d he says, \u201cbecause there\u2019s not that much I actually want to change.\u201d<\/p>\n<\/div>\n A lot of other things have changed in eight years, though. Google, Apple, and Samsung all now have good smartwatches that are tied tightly to their other devices \u2014 Pebble always had trouble getting access to features on iOS, in particular, and that\u2019s not getting easier. Smartwatches are currently health and fitness devices above all else, and they\u2019re getting vastly more complex and powerful in pursuit of those features. Google obviously doesn\u2019t see any form of Pebble as a threat; its best chance is to chart another path entirely.<\/p>\n<\/div>\n The biggest difference this time will be how the company itself operates. Migicovsky wrote a long blog post in 2022<\/a> explaining what went wrong at Pebble the first time and ascribed its failure in part to taking a bunch of investment money and letting it change the company. Since then, Migicovsky has made plenty of money from Beeper and during a stint as an investor at Y Combinator; his new company is his alone. Right now, it\u2019s just Migicovsky and a few part-time employees \u2014 it\u2019ll grow, he says, but not too much. \u201cThe core thing here is: sustainable.\u201d<\/p>\n<\/div>\n \u201cThey could even use it in random other hardware. Who knows what people can do with it now?\u201d<\/p>\n<\/div>\n<\/div>\n Migicovsky also hopes to be part of a broader open-source community around Pebble OS. The Pebble diehards still exist: a group of developers at Rebble<\/a> have worked to keep many of the platform\u2019s apps alive<\/a>, for instance, along with the Cobble app<\/a> for connecting to phones, and the Pebble subreddit<\/a> is surprisingly active for a product that hasn\u2019t been updated since the Obama administration. Migicovsky says he plans to open-source whatever his new company builds and hopes lots of other folks will build stuff, too. \u201cThere\u2019s going to be the ability for anyone who wants to, to take Pebble source code, compile it, run it on their Pebbles, build new Pebbles, build new watches,\u201d he says. \u201cThey could even use it in random other hardware. Who knows what people can do with it now?\u201d<\/p>\n<\/div>\n This whole project will take time, Migicovsky cautions. He only found out for sure that Google would open-source the software a few days ago, and he hasn\u2019t been able to use it at all yet. But he\u2019s already working on hardware prototypes, and he\u2019s crystal clear on what he wants the new Pebbles to be. He knows he can do it because he already did it once. The evidence is right there on his wrist. All he\u2019s trying to do is make sure it can stay there.<\/p>\n<\/div>\n<\/div>\n