Several General Questions

1) Covered in the "How to publish" section in the PDF in the doc directory of the SDK. Looks like browsing and installing apps will be handled through the Connect App.

2) This is all I know: http://developer.garmin.com/connect-iq/what-you-can-build/ I believe the point with the data field type is that they works like ordinary data fields and can be added on any data field page.

3) Now. Just add <iq:product id="fr920xt"/> . See https://forums.garmin.com/showthread.php?146383-Connect-IQ-1-1

4) Yes. I believe the "Comm" sample app in the API shows that. The APIs also allows generic requests to web services through the Garmin connect app.

5) The SDK currently includes some support for drawing standard things like menus and standard looking data fields.

6) http://www.slideshare.net/Garmin/garmin-connectiq-announcement slide 34, linked from http://developer.garmin.com/connect-iq/overview/ . Basically through companion apps and webapps.

- HOW AN APP BECOMES A LAW

1. You create the app. I would suggest testing on the product you want to run on.
2. When you are ready, you use the &#8220;Export Application Package&#8221; to make an IQ file. This packages the app for every device you choose to support.
3. You upload the IQ file to the app store
4. After Garmin approval it appears on the store.

- I'd like to think the programmer's guide (doc\Monkey C Programmers Guide) goes into a lot of detail about the app types. Data fields will have limits - they have the least amount of Toybox access because there will be multiple running. They do have access to the same data that regular data fields do though.

- We put out an SDK with a 920 last week - you can get the 0.1.1 SDK from the API manager in the Eclipse plug in. You have to add the 920 as a product you support in your product properties (Properties | Connect IQ)

- The best way to get FIT data from your app is through the Connect SDK. You can send data to a smart phone using the Toybox.Communications module. See the Comm sample for details.

- We are adding a few more native widgets that give you the device look and feel in your app. Those will be coming in November.

- All content on the app store will be free to the end customer. The idea with monetization was that developers would monetize the solution, not just the watch app. If your watch app requires a phone app to work, you can monetize via an in-app purchase from your phone app, or by directing Garmin customers to your app from our app store. If your app talks via the JSON API to a web service, you can monetize your web service. If you make a sensor that can talk to Connect IQ via ANT, then you can drive sensor sales through the app store. The Pebble app store takes a similar model.

Cheers,

-Alpha Monkey

5) For some of these apps or data fields being developed, will developers have to develop the graphical user interface for the screen? For example let's say I develop a new data field for a user to select, will it default and use the 920 graphics or do I need to develop those graphics?

To expand on this question, there are two classes that can be used to implement a data field. They are DataField, and SimpleDataField. A DataField will get a draw context and must draw its own graphics. A SimpleDataField will provide only a value, and the system will draw the value for you using the native graphics.