A Wristed Development
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.
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!
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!
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.
- All Posts
- At the Pub
- Beautiful Code
- Down the Rabbit Hole
- Freshly Baked