The future of the Pebble watch is clarified (relatively)
Hi, Giktayms! You probably already know that Pebble closes, stops producing and selling watches, and sells intellectual property to Fitbit. Which, in turn, promised to maintain throughout 2017 all the necessary infrastructure for working hours in working condition. I think not only worries me a question, but what will happen to the clock after?
The answer is published on the Pebble blog for developers. And below you can read his translation.
After over the course of the week we introduced ourselves, got acquainted, mastered and merged into the Fitbit team, I would like to introduce myself to those users who do not know me. My name is John Barlow. I have been actively involved in the community since the very beginning: I am the developer of dials for Pebble, an active community moderator, a person who is extremely passionate about Pebble and supported all three projects on Kickstarter with finances. For the past year and three months, it has been a great honor for me to be part of the Pebble Evangelical Development Team, acting as a representative and advocate for developers at the company.
Now I am writing as a member of the Fitbit team responsible for the smooth and painless Pebble transition. Our mission is to support the Pebble developer community, which we have grown with love, taking care that the Pebble watch continues to work.
Fitbit made sure that Pebble software and services worked without interruption in 2017. Naturally, none of the newly-formed team seeks to “tinker” Pebble, which are actively used. Pebble SDK, CloudPebble, Timeline API, access to firmware, mobile applications, developer portal and Pebble application store are elements of the Pebble ecosystem that will continue to work during this time. Pebble application developers can still develop and update them. Users can still enjoy using the watch.
In order to preserve Pebble's functionality, we will update our mobile apps in the future and remove from them dependencies on heaps of cloud services (authentication, analytics, store, app locker, etc.). This update is expected in the coming months. It will ensure the preservation of the basic functions of Pebble even when the cloud services are closed. This will not affect the functionality.
After the update, Pebble Health will continue to work the same as now. Health API data does not depend on cloud services, it is transmitted directly to the Pebble mobile app, Apple HealthKit and Google Fit.
We are now discussing Pebble features that depend on third-party services — voice input, messages, weather, etc. — to decide whether these features will continue to work, and, if so, for how long. When we define - write here.
The Pebble community has always given its shoulder when our little team needed it and you continue to do it. We see a massive influx of developers from the community, united to keep Pebble working in the future. If you want to contribute to the common cause, look for us on these Discord channels :
#appstore
#firmware
# mobile-apps
#rebirth
Actual Pebble application developers who need help or information about Pebble's internal device can contact us. Write us on twitter @pebbledev or in the Pebble community on Discord .
And also, I want the Pebble user community to know how much depends on it. Continuing to communicate with us and share our enthusiasm for what makes Pebble special to you will help our friends at Fitbit understand how valuable your enthusiasm can be. Now, as before, we are not surprising alone.
See you soon,
John Barlow + #PEBBLExFITBIT command
→ Original article
The answer is published on the Pebble blog for developers. And below you can read his translation.
(Hello again!
After over the course of the week we introduced ourselves, got acquainted, mastered and merged into the Fitbit team, I would like to introduce myself to those users who do not know me. My name is John Barlow. I have been actively involved in the community since the very beginning: I am the developer of dials for Pebble, an active community moderator, a person who is extremely passionate about Pebble and supported all three projects on Kickstarter with finances. For the past year and three months, it has been a great honor for me to be part of the Pebble Evangelical Development Team, acting as a representative and advocate for developers at the company.
Now I am writing as a member of the Fitbit team responsible for the smooth and painless Pebble transition. Our mission is to support the Pebble developer community, which we have grown with love, taking care that the Pebble watch continues to work.
Using Pebble in 2017
Fitbit made sure that Pebble software and services worked without interruption in 2017. Naturally, none of the newly-formed team seeks to “tinker” Pebble, which are actively used. Pebble SDK, CloudPebble, Timeline API, access to firmware, mobile applications, developer portal and Pebble application store are elements of the Pebble ecosystem that will continue to work during this time. Pebble application developers can still develop and update them. Users can still enjoy using the watch.
Further development
Main functions
In order to preserve Pebble's functionality, we will update our mobile apps in the future and remove from them dependencies on heaps of cloud services (authentication, analytics, store, app locker, etc.). This update is expected in the coming months. It will ensure the preservation of the basic functions of Pebble even when the cloud services are closed. This will not affect the functionality.
Pebble health
After the update, Pebble Health will continue to work the same as now. Health API data does not depend on cloud services, it is transmitted directly to the Pebble mobile app, Apple HealthKit and Google Fit.
Pebble Smart Features
We are now discussing Pebble features that depend on third-party services — voice input, messages, weather, etc. — to decide whether these features will continue to work, and, if so, for how long. When we define - write here.
We transfer power to users
The Pebble community has always given its shoulder when our little team needed it and you continue to do it. We see a massive influx of developers from the community, united to keep Pebble working in the future. If you want to contribute to the common cause, look for us on these Discord channels :
#appstore
#firmware
# mobile-apps
#rebirth
Actual Pebble application developers who need help or information about Pebble's internal device can contact us. Write us on twitter @pebbledev or in the Pebble community on Discord .
And also, I want the Pebble user community to know how much depends on it. Continuing to communicate with us and share our enthusiasm for what makes Pebble special to you will help our friends at Fitbit understand how valuable your enthusiasm can be. Now, as before, we are not surprising alone.
See you soon,
John Barlow + #PEBBLExFITBIT command
→ Original article