The initial slideshow referenced that Connect IQ would have access to the acceleratometer data however I see no reference to it in the current SDK docs. Is it a feature that is coming or is it something that was abandoned?
It's been abandoned for now. It's a highly requested item, but often times the requests are followed by "and can I get 2000 samples/sec so I can <insert use case here>?" and I have to go into a long rambling answer about how my bytecode interpreter won't be able to keep up with the data on the wearable. I'm hoping future versions of CIQ will have improved performance (*cough* native methods *cough*) so we can give full accelerometer access, but I don't want to provide an API that will only be a disappointment.
I'd be interested in this too. So, I'd like to be able to tell if the arm is hanging down by your side or pointing out in front. I don't need many samples per second for this.
It's been abandoned for now. It's a highly requested item, but often times the requests are followed by "and can I get 2000 samples/sec so I can <insert use case here>?" and I have to go into a long rambling answer about how my bytecode interpreter won't be able to keep up with the data on the wearable. I'm hoping future versions of CIQ will have improved performance (*cough* native methods *cough*) so we can give full accelerometer access, but I don't want to provide an API that will only be a disappointment.
This is a real shame. The right answer is to provide the best accelerometer access that is currently technically feasible. Garmin has a chance to be a leader in the fitness space but your chance dwindles every time you withhold a desired feature from the developers (and ultimately the users). You're trying to build a fitness platform, right? So are Google, Apple, and Microsoft. You can be sure they won't intentionally frustrate their developers. Microsoft already provides a Microsoft Band SDK that provides full access to all the sensors, including the accelerometer.
The initial slideshow referenced that Connect IQ would have access to the acceleratometer data however I see no reference to it in the current SDK docs. Is it a feature that is coming or is it something that was abandoned?
As a developer, Garmin's refusal to provide raw accelerometer data is a show stopper. It's unfortunate, but it makes our decision easier. We're going to focus on the Microsoft platform instead.
As a developer, Garmin's refusal to provide raw accelerometer data is a show stopper. It's unfortunate, but it makes our decision easier. We're going to focus on the Microsoft platform instead.
I wouldn't give up so fast. Grumbles from folks developing apps just might move up the priority list at Garmin. Taking your ball and threatening to go home, could just lower the priority....
I wouldn't give up so fast. Grumbles from folks developing apps just might move up the priority list at Garmin. Taking your ball and threatening to go home, could just lower the priority....
Like most developers, I don't yet have a vested interest in any of the fitness platforms. I need a platform that will provide the capabilities I need to deliver the product that I'm designing. The Connect IQ platform is lacking, the Microsoft Health and Google Android platforms are not. That's communicating, not threatening.
Apologies for not making accelerometer access available sooner. Our intent isn't to withhold features, but to provide the best experience for developers and users when a feature is made available. We do have plans to provide access to the accelerometer, but like AlphaMonkeyC had said, we don't want to give developers a handicapped feature. Instead, we've decided to wait to make it available when it can do what we expect, and what I'm sure you expect.
I understand if a developer chooses to focus their efforts elsewhere if Connect IQ doesn't meet their needs. I hope, however, that people will continue to check back with us to see whether what we're doing becomes a viable solution for their application. We're definitely not sitting still and place a lot of weight on the feedback we receive. Thanks!
I understand if a developer chooses to focus their efforts elsewhere if Connect IQ doesn't meet their needs. I hope, however, that people will continue to check back with us to see whether what we're doing becomes a viable solution for their application. We're definitely not sitting still and place a lot of weight on the feedback we receive. Thanks!
I am just checking back to see what happens with the accelerometer feature. Are there any plans to do anything in that regard? Would it be feasible with the current hardware, it would you need improved hardware? Access to the accelerometer would be the kind of feature Connect IQ needs to get some traction.
