Pebble Developer Blog

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.

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.

In October, we gave developers access to the microphone in the Pebble Time via our new Dictation API, and almost instantly we began seeing awesome projects utilising speech input. Voice recognition is an exciting new method of interaction for Pebble and it has created an opportunity for developers to enhance their existing applications, or create highly engaging new applications designed around the spoken word.

Speech-to-text has been integrated with Pebble by using the Recognizer cloud service from Nuance, a leading provider of voice and language solutions.

Starting with Pebble Time Round, we are moving towards communicating with Bluetooth Low-Energy only. This means there are some updates to PebbleKit iOS to support this. Here are the major changes and steps to take to support the new BLE connection.

What's New

• Companion apps have dedicated, persistent communication channels
• Start mobile apps from Pebble
• 8K AppMessage buffers
• Swift support