Pebble Mega Update - July 2026 | rePebble Blog
TL:DR;
Pebble Time 2 Shipping Status
Pebble Software Updates
PT2 - Issues You’ve Reported
Pebble Round 2 Production Update
Index 01 Production Update
#Pebble Time 2 Shipping Status
Since we started mass production in late March, we’ve built over 23,000 Pebble Time 2 watches. We’re over 80% of the way through fulfilling all the pre-orders we’ve received! But that means there are still some ultra patient folks who haven’t received their watches yet. If you’ve placed an pre-order for PT2 and haven’t received it yet (including Batch 6 - August), here’s when we expect to ship your watch out:
Pebble Time 2 - Black → July 31
Pebble Time 2 - Red → July 31
Pebble Time 2 - Grey → July 28
Pebble Time 2 - Blue → July 28
Coincidentally, this means that we’ll be ‘in-stock’ with no wait very soon! If you’ve been holding off placing an order because you didn’t want to wait, now is the time to jump on it. This won’t last forever - first-come first serve. As soon as the current inventory is sold out, we’ll be back in pre-order mode waiting for the next shipment.
Order today on rePebble.com/watch.
Major props to our three person customer support and logistics team! Claudio, Trevor and Colin have answered thousands of your questions and helped ship watches safely onto your wrist in 93 countries. Have a question? Please check out our Help site first. If that doesn’t have an answer, please email us at [email protected].
Want an extra Pebble charger? shop.repebble.com now carries accessories - full selection of straps coming soon.
#Pebble Software - Progress and Roadmap
Over the last 6 months, the core four person Pebble software team built and shipped a metric ton of new Pebble open source software! Our improvements were centered around these areas:
Battery life
We’ve (well, mostly Gerard 🙂) worked extraordinarily hard over the last few months, optimizing and reducing power consumption in PebbleOS. As predicted, we boosted the median battery life of Pebble 2 Duo from 17 days (last summer) to over 30 days. Pebble Time 2 median is currently around 21 days - more improvements in the works here too! The biggest consumers of power are backlight, watchfaces with a lot of animations and health tracking. If you want to ‘hypermile’ your Pebble, try switching to a low-animation watchface and the new Battery Saver backlight mode (Settings → Display → Backlight).
Apps and SDK
T ogether with the Moddable team, we’ve published several Pebble SDK updates introducing new features like:
Touch Screen API (Calculator on your wrist anyone?)
Speaker API (useful for tuning your guitar, or feeding your Tamagotchi)
RGB Backlight API (try it in this wild little app Chinese Toy Phone)
Apps can now determine how they were quick launched (ie by single press, long press)
Alloy (native JS apps)
FFI - run C code within Alloy JS apps (similar to Android NDK) and js debugger
A bunch of new JS APIs
pebble build --debug now defines PBL_DEBUG and launches XSBUG, a powerful JS debugger
Developers in the Pebble community have created 2,120 apps and watchfaces for Pebble Time 2 and Pebble Round 2 already!
Index 01
The first version of all Index 01 functionality is up and running inside the Pebble mobile app. Don’t have an Index 01 yet? You can check out how it works and try the software interface in the Pebble app, just go to Settings → General → Enable Index feed.
All the main features are in, including syncing to iOS Reminders, Obsidian, Google Tasks, Calendar, Android music control, MCPs and sending recordings or transcriptions to your own server or app via Webhook. Optional encryption (you own the keys) protects optional cloud backup. And of course, it’s all open source (github.com/coredevices/mobileapp). We even built a little webapp that you can use to access your Index information from anywhere → index.rePebble.com. Watch the podcast or read the blog post to learn more.
Stability
Thanks to helpful bug reports from y’all, we’ve made hundreds of small improvements to PebbleOS and the Pebble mobile app. Please keep it coming!
I’ll dive into one specific (and ultra technical) topic - reverse PPoGATT (Pebble Protocol over GATT). Quick history: during the first Pebble era, we configured the Pebble mobile app to expose a PPoGATT service, as means to work around the lack of IPC between iOS apps. This setup is the opposite of how Bluetooth accessories normally connect to phones and caused a number of weird problems! Also this setup blocks us from using iOS AccessorySetupKit (ASK), which is a prerequisite for us to implement the new Notification Forwarding feature (EU only) that will finally enable you to reply to notifications. Enabling ASK is going to be tough - our iOS app must either use ASK or not, meaning that we need to upgrade the recovery firmware on all Pebble watches in the field to reverse PPoGATT before we can switch ASK on. Anyways, we have the first piece of the puzzle in...