All major smartwatch platforms which support apps on the watch also support communications between the watch app and the 3rd party companion apps on the phones. This includes Android Wear, Galaxy Gear, Garmin Vivosmart, Pebble...
We desperately need a way how to talk to phone apps. At the moment the only very cumbersome workaround is to create a HTTP server with a local URL on the device and use the fetch() API.. but two way communication is only possible through polling and in all cases this will negatively affect battery life of the phone..
I think this limitation is a great burden to very interesting use-case which are simply not possible with FitBit. For example we would really like to introduce the Ionic to several million of our Sleep as Android users.
Even without any API changes there is a super simple ways how to allows 3rd party integrations from within the FitBit app. For example on Android if a companion messages would also broadcast an intent with the parameters (target appId, name, payload..) like intent extras we are all done, this would open this platform to all the amazing on phone use-cases. Implementation time of that in the FitBit app is 1 man hour and there is no need to change the APIs!
Join us on the Community Forums!
Community Guidelines
Learn the Basics
Join the Community!
Not finding your answer on the Community Forums?
Go to the Help Site
Contact Support