Pebble Developer Blog

I am thrilled to announce that, as part of SDK 3.13 and Pebble Tool 4.3, we have launched our own packaging system: Pebble Packages!

Happy leap day! Today is a once-every-four-years day of bizarre date-related bugs, and thus an opportune moment for us to introduce our latest developer feature: app debugging in the emulator! This gives you a powerful new way to hunt down errors in your apps.

In SDK 3.9 we will introduce a new feature to the Pebble SDK: the ability to cleanly use multiple JavaScript files in the PebbleKit JS app portion of your project.

With the upcoming release of firmware 3.8 on Pebble and Pebble Steel, and the associated SDK 3.8, we have decided to redesign how image resources work in Pebble apps.

I am pleased to today announce that version 4.0-rc4 of the pebble tool is now available. The key new feature is a new paradigm for dealing with firmware and SDK versions. This makes it much easier to deal with differing SDK versions, or to test code on multiple (emulated) firmware versions.

A note: while the tool is now at version 4.0, the SDK, firmware and mobile apps will not be following. Pebble tool versioning is now completely independent of the rest of the Pebble ecosystem.

This is another in a series of technical articles provided by the members of the Pebble software engineering team. This article describes some recent work done at Pebble to develop a Pebble emulator based on the QEMU project (QEMU, short for Quick EMUlator, is a generic, open source machine emulator and virtualizer).

We're thrilled to announce the latest addition to CloudPebble: a Pebble smartwatch emulator!

CloudPebble today gains significantly enhanced support for code completion, as well as inline syntax checking and the ability to "go to definition".

Check it out!

Today we released SDK 2.6.1, which includes support for background workers. This enables great activity tracking apps like Misfit and Jawbone's Up to keep counting in the background — and you can use them too! Head over to our background worker guide and read through the API documentation to find out how.

We have also added APIs for direct access to the framebuffer, and to retrieve information on the watch, including its color and firmware version.

Browse through the release notes for full details.

We are pleased to announce that we will soon be automatically updating apps installed from the Pebble appstore. We believe this will be a significant improvement to your ability to get your work into the hands of your users, as well as to the user experience.

However, as developers, you need to make sure that your app is ready for these updates. In particular, you will need to make sure that your app conforms to our new version numbering, and that it can tolerate persistent storage left over from old app versions.

Today we're adding a new feature to CloudPebble that will make it easier than ever to build your watchfaces and watchapps! The new UI Editor will let you graphically build the user interface for your C app; you can then use the generated C to build anything you like.

To help make your Pebble development experience even better, CloudPebble can now display the API documentation for any function directly in the editor view.

We now have an even easier way for you to deploy apps to your watches! No longer will you have to launch the app, turn on the development server, and type in your IP address. Instead, you now simply need to select your phone from a list.

It's now even easier to get started with Pebble development or prototype new ideas!

CloudPebble recently gained support for building Simply.js projects – which means you can now write, build and install simple apps entirely in JavaScript and inside your web browser.