惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
V2EX
量子位
博客园 - 司徒正美
IT之家
IT之家
V
Visual Studio Blog
Apple Machine Learning Research
Apple Machine Learning Research
博客园_首页
Google DeepMind News
Google DeepMind News
Last Week in AI
Last Week in AI
Microsoft Security Blog
Microsoft Security Blog
T
Tailwind CSS Blog
aimingoo的专栏
aimingoo的专栏
GbyAI
GbyAI
Vercel News
Vercel News
B
Blog
大猫的无限游戏
大猫的无限游戏
D
DataBreaches.Net
小众软件
小众软件
罗磊的独立博客
博客园 - 叶小钗
雷峰网
雷峰网
Martin Fowler
Martin Fowler
Hugging Face - Blog
Hugging Face - Blog
WordPress大学
WordPress大学

Lobsters

CIFSwitch: a non-universal Linux local root vulnerability RIPE NCC session fixation: poaching logins with an Atlas probe GNOME 2.20 but its Web Components Agentic Search for Context Engineering – Leonie Monigatti Garnix is shutting down [not OC] akashina.tngl.sh/jjc Concerning Emacs (and Jazz) Nitpicking the shell history scene in ‘Tron: Legacy’ What's cooking on SourceHut? Q2 2026 The tenth OpenPGP email summit Package managers that package package managers Clojure on Fennel part three: parsing WordPress at 23 Finding Miscompiles for Fun, Not Profit GitHub - creusot-rs/creusot: Creusot helps you prove your Rust code is correct. Announcing Rust 1.96.0 | Rust Blog A Love Letter to Neovim sqlite AGENTS.md Am I a Bad Friend? CSS vs. JavaScript • Josh W. Comeau Erlang Ecosystem Foundation - Supporting the BEAM community A brief note about slot access cost in Common Lisp Keyboard latency probe Rethinking the GNOME clipboard issues Back to the Building Blocks’ Building Blocks Tech Notes: Theseus: translating win32 to wasm Fast is better than slow Content-addressed Rust builds (or, what kache actually caches) Intent to Prototype: Embedding API Canada’s Bill C-22 and the security cost of collecting more data
Making pebble apps in 2026
Mar Bartolome · 2026-05-08 · via Lobsters

‘Member Pebble? It was one of the first smartwatches in the market, and in my personal opinion, the only one that got the concept right: it was minimal, efficient, and tinker-friendly. People could program apps for it, just like with a smartphone. Pebbles were so popular back in the day that the company died of success: took up too much investment, and ended up being bought by Fitbit, who officially discontinued the project in 1016.

The community around Pebble was naturally disappointed, to the point that a group of enthusiasts (who called themselves “the Rebble Alliance”), found a way to keep their watches alive by building their own replacement of the online services and app store, and scraped all of the existing watch apps and faces before the official ones were shut down. But ultimately, our devices ended up dying of old age.

Then last year, Pebble’s original author announced that they were resurrecting the project: and there was much rejoicing! Production took a while, but as of today you can buy a brand new Pebble watch. And whatsmore: they imported all of the old archive of apps and faces rescued by Rebble into the new app store, which are still compatible with the new watches. A success story in digital preservation!

Recently, there was a official app-making contest which served as the perfect excuse to build a couple of apps ourselves.

Neko watchface on a pebble watch

One of the apps we've build: a Neko wristmate

Neko wristmate

Mar built a watchface (ie, an app whose purpose is to run as the main display of the device) featuring an animated Neko screenmate mascot, alongside the time and date. The Neko will play around for a bit, and fall asleep after a while. It will wake up on a tap event (eg, when you tap the watch or do a wrist-turn movement).

Neko watchface screenshot

80% battery charged

Javi built an app that triggers on charging, and will notify the user when the charge level reaches 80%. This way you can choose to interrupt the charge before reaching 100%, which is useful for preventing long term battery capacity degradation.

80% battery app screenshot

Implementation details

Pebble apps used to be non-trivial to build back in the day. They need to be coded in C, and although the SDK provides a lot of helpers, building something minimally complex (eg, with animations, or interactions) was cumbersome and error prone.

Today this process is a lot easier if you enlist your AI agent of choice as a helping hand. We’ve built ours using Claude and the official Pebble-development skill.

Even if you use a clanker for the heavy lifting, it’s a good idea to manually go though the official tutorial first, which helps you familiarize with several low-level pebble concepts that ure useful to know when designing your apps.

An important point to consider is that there are a lot more Pebble models now that there were back in the 2010s, each with different characteristics. For example: different screen resolutions, colored or black-and-white displays, or the newest model even has touch support. The SDK designates each of them as a platform with a codename (see the relevant docs).

In our case, we initially created our apps with our watch model as the target platform (flint for Pebble 2 Duo), and afterwards added tweaking for others, with the help of Claude. You can use the provided emulators in the SDK to test how it would look in each different platform.

More than just apps

Pebble is under very active development at the moment, so the landscape is changing very quickly with new and exciting capabilities. There’s a cloud IDE with integrated SDK and emulators, new models with touch capabilities and compatible with apps developed in JS, and there’s a companion smart-ring that is currently in the works.

But the best part of it is that this time absolutely everything is open sourced, even the firmware and hardware schematics. This is great news, as it allows the community to get involved in ways other than simply writing apps, but also guarantees that this time pebble will not go away as easily as before, even if the Core Devices company ceases its operations.

We’re very excited about the Pebble comeback and their new direction, and if our time allows we’ll continue to develop more apps for the platform in the future.