Pebble Developer Blog

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.

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!

For those that don’t already know, the RePhone smartstrap kit was part of a highly successful Kickstarter campaign by Seeed Studio to create the world’s first open source and modular smartphone. Part of their campaign was to create a smartstrap kit for Pebble Time that integrates with RePhone modules such as GPS, NFC, and external batteries. This is the first commercial smartstrap project I’ve managed to lay my hands on, and it’s awesome!

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.

This is a guest post by Dries Oeyen, developer of the Pebble app Commute and Rockstar of Belgium's Pebble Developer Meetup, PebbleBelgium.

Hello everyone. I'm Dries Oeyen and I live in Belgium, a tiny country in Europe. In case you're wondering what Belgium is like: in the morning on weekdays, it looks roughly like this:

The time has almost come for Pebble Classic and Pebble Steel to get firmware 3.x!

This is great news for users who get access to all the improvements and fixes since 2.x, as well as new features such as timeline, Quiet Time, no more eight app limit, Standby Mode, and last but not least one new color (gray)!

But let us not forget about Basalt and Chalk app developers, who also have a lot to get excited about - a huge new user base of Aplite watch wearers!

This blog post aims to help developers using SDK 2.x features and APIs to migrate their apps to a single 3.x codebase. As well as bringing compatibility to all older watches when they upgrade to firmware 3.x, these changes will also serve to remove a lot of complex and ugly conditional code that has needed to exist in the meantime. Let's fix some apps!

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.