(Request) Calories from Garmin Connect widget

In order to do this legally, the developer would need a license to access the Garmin Connect API. There is a $5000 fee to apply for access to this API, and the request can be denied.

From my perspective, you'd have to pay $5000, or be able to guarantee approval of my request and guarantee that I'd make $5000 back in sales for any resulting products.

Travis

Travis,

Hey thanks for providing some insight! So are most of the apps in widgets in the Connect IQ "App Store" faced with similar price structures? Or is it because of the specific information that would need to be pulled in? I suppose I sort of assumed any info from the device (in my case the fenix 3) or from Connect was open to pull from. How does garmin expect to attract developers to the platform as it doesn't seem you can charge for the apps/widgets on there....that's more of a rhetorical question. I don't know much bout software development but am intrigued by the "magic" you developers do.

Guess I'll just have to keep hiking and eat till I'm full....
Oh and by the way, if I ever become a wealthy man, I'm going to send you the $5k and ask for that widget!

Well, developers are free to monetize their ConnectIQ applications, they just have to figure out how to do so outside of the app store.

A developer could create a service where users get an account, and each account has a list of application tokens that the user has paid for. Every application created by the developer would have an application token, and when the user starts the application, the user and application tokens are sent to the service, which can verify that the given user is authorized to use the given application. I don't think it would be incredibly difficult to get something that working, I just don't think it would be easy to be sure users aren't gaming the system, and that I'm not leaking user data out into the internet.

I made another thread about this as a request. Ideally the Connect API should provide the information available in the Connect App on the mobile via an API call or simply provide some new models which reflect the Connect APP view for the watch to consume.

This would solve a number of issues such as device synchronisation (i.e. I use my 510 for bike riding, Fenix for everything else), sleep information, actual calorie usage (i.e. myfitness pal integration reflected on watch). etc etc.