The smartwatch world has moved on from Pebble. Apple and Samsung dominate wrists now, offering colour screens, health tracking, and ecosystem integration that make the original e-paper pioneer feel quaint. But for a devoted community, Pebble never died. It just went into maintenance mode, kept alive by Rebble, a volunteer group that stepped in when the company folded in 2016.
Now there’s a conflict brewing between Rebble and Core Devices, the new company founded by Pebble’s original creator, Eric Migicovsky. On the surface, it looks like technical disputes over server access and data rights. Dig deeper, and it’s really about control, respect, and fundamentally different visions for what Pebble should become.
The Accusation That Started Everything
Rebble went public with serious claims: Eric had violated agreements by scraping their app store infrastructure. The implication was clear: Core Devices was stealing community work to build a competing service.
Turns out, that wasn’t accurate. Eric had built a tool to index watch faces so they’d be discoverable in the new Pebble app he was developing. He wasn’t duplicating infrastructure or attempting to replace Rebble’s services. He was trying to ensure users could actually find content when Core’s new watches shipped.
Rebble saw unusual activity in their server logs and assumed malicious intent rather than asking what was happening. When Eric provided screenshots and detailed explanations showing his actual purpose, the narrative fell apart. The initial accusation, however, hasn’t been retracted. It remains pinned in community spaces, shaping perceptions despite being demonstrably wrong.
That matters. Public accusations carry weight, especially in tight-knit communities. Leaving a debunked claim uncorrected starts looking less like an honest mistake and more like deliberate positioning.
Volunteer Maintenance Versus Commercial Reality
Here’s where things get complicated. Rebble deserves genuine credit. They maintained app store access, kept services running, and preserved functionality for thousands of watches that would otherwise have become expensive paperweights. That work was volunteer-driven, sustained by donations and enthusiasm rather than profit.
But volunteer maintenance and commercial hardware production operate on different timescales and incentives. Eric is manufacturing physical products, which requires capital investment, supply chain management, and controllable software infrastructure. You cannot run a hardware company if critical backend services are controlled by an organisation with different goals and no financial stake in your success.
Rebble contributors seemingly expected their years of work would translate into permanent involvement with Pebble’s future. Some discussions suggest they thought they were building towards a new watch business together, rather than simply maintaining legacy hardware. When Eric moved forward with Core Devices as his own venture, that felt like betrayal.
From Eric’s perspective, he offered to pay Rebble for app store access and collaborate where it made sense. That apparently wasn’t sufficient. Rebble wanted assurances about ongoing relevance that Eric couldn’t provide whilst trying to run an actual company.
The Moderation Problem
Community platforms are supposed to be neutral ground, but the Pebble subreddit became part of the problem. Rebble’s accusatory post got pinned immediately. Eric’s detailed response, complete with evidence contradicting the scraping claims, took two days to receive equal treatment.
Some moderators are Rebble contributors dealing with personal issues, which explains delays. But in fast-moving online discussions, 48 hours might as well be a month. Pre-orders were cancelled based on incomplete information. Core Devices took reputational damage before their side of the story gained visibility.
First impressions spread faster than corrections. That’s not unique to this situation, but it’s frustrating when moderation structure contributes to imbalance.
What Both Sides Actually Want
Rebble wants assurance they won’t become irrelevant. After years keeping Pebble alive, having Eric potentially make them redundant feels dismissive of their contribution. They’re also concerned about what happens if Core Devices fails. Who picks up the pieces then?
Eric wants to build something sustainable without being held hostage by an organisation that doesn’t share his commercial objectives. He needs control over the services his products depend on. That’s not unreasonable when you’re shouldering financial risk.
Neither position is inherently wrong. The problem is they’re incompatible without significant compromise from one side or the other.
Technical Solutions Nobody’s Considering
The frustrating part is that workable technical solutions exist. Core could ship with Eric’s infrastructure by default whilst allowing advanced users to point their watches at Rebble’s services instead. That preserves choice without forcing either party to control the other.
Alternatively, Eric could build his own app store from publicly archived Pebble data and simply move on. More work upfront, but it eliminates ongoing drama and gives Core complete independence. Given how this has played out, that’s looking increasingly likely.
The real barrier isn’t technical. It’s ego and control. Both sides feel disrespected, both have legitimate grievances, and neither wants to be the one who backs down.
Where This Likely Ends
Based on similar conflicts in other tech communities, reconciliation rarely happens without one side decisively winning or both deciding the fight isn’t worth continuing. The collaborative middle ground everyone theoretically wants requires trust that’s been thoroughly damaged.
Eric has the resources and motivation to bypass Rebble entirely. Building replacement infrastructure costs time and money, but it’s achievable. That fragments the ecosystem into old Pebble (Rebble-maintained) and new Pebble (Core-controlled), which serves nobody’s interests long-term but might be the only viable path forward.
Rebble could continue serving existing watches whilst Core handles new hardware, but that requires both parties accepting diminished influence over their respective domains. Nothing in the public discussions suggests that appetite exists.
The Broader Lesson
This isn’t really about Pebble. It’s about the recurring friction between open-source community work and commercial ventures built on similar foundations. Volunteer maintainers deserve respect and recognition. But respect doesn’t automatically translate into business partnership, especially when the person taking financial risk needs operational control to succeed.
The community is caught in the middle. Many people paid Rebble subscriptions over the years and appreciate their work. Those same people also want new hardware and properly maintained software that doesn’t require workarounds. Both groups have earned support, but right now they’re undermining each other.
What should have been a celebratory moment, bringing Pebble back after years in limbo, has turned into a public dispute that benefits nobody. The winners, if there are any, will be Apple and Samsung, who continue selling smartwatches to people who might have considered something different.
Hopefully cooler heads prevail. But having watched similar conflicts play out elsewhere, that rarely happens without one side decisively winning or both exhausting themselves. We’ll see which path Pebble’s community takes.
