Pebble Developer Blog

Developers rejoice - we’ve released the first version of our SDK 4 developer preview! This SDK enables you to start building applications for the new Diorite platform (Pebble 2), and includes a set of new APIs for interacting with the 4.0 user experience.

In this blog post we’ll dive into the App Glance, UnobstructedArea, and AppExitReason APIs, and explain how you can use them to create great experiences for your users!

You might have noticed a bit of a buzz around Pebble today - we have officially launched our third Kickstarter campaign, and it is jam packed with exciting new products and features for developers to explore and hack on. We have been hard at work not only creating the next generation of health-focused smartwatches, but also refining what great wearable user and developer experiences look like. We are introducing an entirely new class of wearable device, and adding a modern JavaScript SDK that takes advantage of the Web APIs JavaScript developers around the world know and love.

There is a lot to take in, so we’re here to help break down what’s new and exciting for our favorite developer community!

This is a guest blog post from Kiezel's Kristof (in Belgium) and Jaron (in the US), who recently opened their KiezelPay payments platform to all Pebble developers! We're super excited to see how it will be used and adopted! You can find a list of KiezelPay Powered watchapps and watchfaces in Pebble's appstore.

KiezelPay was designed to help developers sell their apps and watchfaces for the Pebble smartwatch as easily, securely, and globally as possible. We learned a lot when we created a payment system for our Kiezel Watchfaces, and we wanted to improve that system and open it to all developers!

If you have been following Pebble in the news, you have likely seen that there have been some recent changes to the Pebble Team. We wanted to take a moment to acknowledge the #awesome work that has gone into getting our developer program to where it is today, and introduce you to the (somewhat) new faces of Pebble's Developer Relations team!

This is a guest post by Mathew Reiss, developer of countless Pebble apps including Snowy and Yahoo! Fantasy Football.

My goal with writing apps for Pebble has never been to make tons of money. Despite Snowy's success, I'm not going to go quitting my job and moving to an exotic island any time soon. However, it has been absolutely awesome making some money off my hobby. Most importantly, having paid users validates my efforts as a developer and proves that what I'm building is not just something that users want, but something that they're willing to pay for.

One of the exciting changes introduced in SDK 3.9 was support for including Multiple JavaScript Files to your projects. While this feature doesn’t allow you to run any JavaScript you previously couldn’t, it makes organizing your PebbleKit JS code a heck of a lot easier.

In this blog post, we'll look at how to refactor some exisiting JavaScript 'library code' into an actual module for PebbleKit JS, making it simpler to use and share!