Testing on real watches

Former Member
Former Member
Hello,

I have developped an application for the Garmin Forerunner 235, to control the heart rate value. I made this app for my father and tested on the watch we gave him for Christmas: https://apps.garmin.com/fr-FR/apps/c14851dd-00cb-43c8-921d-6d1e5888eea0

During development, I had some trouble making the application work on the watch, when everything on simulator was fine. For example, I never succeeded to link the real app with the Android companion app I was developping, whereas the link between the simulator and Android was fine. In the forum I was told the bug was known but hard to identify and to correct. (https://forums.garmin.com/showthread.php?315054-No-callback-from-getApplicationInfo)

Now that I do not have the watch anymore, I cannot improve my app as I cannot test on a real watch. I have another watch for my activities that is fine for me, so I do not plan to invest in a Garmin watch.

My question is:
Is there a program to lend watches, via partner shops maybe, or some other way to help developpers to test on different model of watches? Or is there a way to find other developpers around with the watch?

Thank you
  • We don't have a lending program in place, but it's perfectly fine to ask for other developers in the forum to test your app if they have the appropriate target device. A 230 is typically a good surrogate for the 235.
  • Former Member
    Former Member over 9 years ago
    Ok thank you. I'll wait to find someone with a watch to easily do some testing then. And maybe after ask other developpers to test on other watch models.
  • Former Member
    Former Member over 9 years ago
    We don't have a lending program in place, but it's perfectly fine to ask for other developers in the forum to test your app if they have the appropriate target device. A 230 is typically a good surrogate for the 235.


    Other companies have programs not for lending, but for providing developers with devices to test with. It is of huge help for the developers, and I don't think it's that much of an expense for Garmin. Especially when it is known that the simulator experience is not reliable enough.
  • I agree with this.

    With App's being free (most commonly) in the Store and no built-in monetization, the platform is mainly dependent on developers building functionality for nothing. Most of the feedback I get is from people saying about support on devices I don't own, and it hasn't been picked-up by the simulator.

    The practical option (in my view) is for Garmin provide a Developer Discount Programme on devices. This means Garmin can sell more devices to developers, get better device support and quality, and have more Apps produced.
  • We've already been discussing a developer program of some sort, but nothing is set in stone at this point. As we build this concept out, I'll be sure to raise the possibility of developer discounts.

    Remember that we do not charge anyone to be a Connect IQ developer, charge for the for the SDK, or demand fees for listing apps on the Connect IQ store. We freely offer the tools, and anyone with an interest can give it a shot. If we decided to offer a percentage discount on devices to Connect IQ developer, we'd effectively be offering a discount on devices to everyone because there's no prerequisite to become a Connect IQ developer. :)
  • I do agree completely with the point on the free SDK and free App submission; which is fantastic for adoption. So I think we're on the same point that once the platform has brought in developers, keeping them engaged could be a concern. If a developer can do something else, or maintain a free App, there may be a struggle. It will be interesting to see how many Apps stop updates after 3 months.

    On the question about discounts (and knowing who you developers are), I had thought about this. So how about having to submit an app before getting a discount or an exam?
  • It will be interesting to see how many Apps stop updates after 3 months.


    I started using Connect IQ apps from the store last March, and many things are still there, supported, and get updated when new features are available in the SDK (such as app settings, alarmCount, and notificationCount in 1.2.1)

    I know in the case of my own stuff, I've easily gone a couple months without updating some apps in the store, simply because there weren't bug reports, and I didn't have any new feature I wanted to add. But they're still supported if someone finds a bug or makes a suggestion I like!
  • Former Member
    Former Member over 9 years ago
    What I thought when I originally posted my question was maybe some Garmin partner shops could lend a watch, for a couple days or a week for example.

    So if I develop an app for a watch I own, and I test on it + I test on the simulator for other models, it could help me to test on other real models in real life. This would be especially useful if a user tells me there is a bug for a specific watch.
  • There are enough guys here with different devices that we can test for you (I personally own a fr920xt, fr630, and edge_1000). Just provide a .prg file compiled for the device, and possibly a settings file.
  • There are enough guys here with different devices that we can test for you (I personally own a fr920xt, fr630, and edge_1000). Just provide a .prg file compiled for the device, and possibly a settings file.


    920xt, vivoactive and 230 here. Welcome to send the prg and settings file like Travis said.