Deleting App

I've never removed an app from the store, but what I believe happens is that if a user has it installed, it just stays installed. It just can't be installed by others, or if a current user uninstalls it, they can't get it back.

But I'll say, with it being one user, have you considered just reporting that user? There's a link in the "Contact Developer" emails to do so.

I know for me, I've gotten emails complaining about how I need to fix "my" servers, etc... And I just respond in a friendly manor...

A friend of mine that also does CIQ asked about some issues he was seeing from users with a 235 just today, and I wonder if there might be something going on in the FW. A few days back I had a user contact that had random reboots on his 235, to see if one of my apps being installed (but not running) might cause it. I pointed him at this thread: https://forums.garmin.com/showthread.php?366653-Forerunner-235-keeps-crashing-after-firmware-update-7-1

I totally get it .. and I have been there too (I had one user that was a plain *** .. gladly I am sure, he uninstalled my app), and why I am slowly leaving Garmin (for Apple) cause honestly for free .. some people are disrespectful and rude.

However .. at the same time, there are some wonderful users out there who do appreciate what we do. But myself .. I have made $2 and I sometimes ask why am I taking the effort.

Garmin needs to monetize their store (eventually).. it is just that people expect free. So .. it will be a very hard hill to climb, but if you are an Apple user in particular you are used to being raped bare of all your money.

Like Jim, I have never deleted an app .. though I have thought about just deleting them all and not letting the door hit me on the way out. But I do love Connect IQ personally and that is 50% why I do it. Being honest, this is a lot about me .. and how I am able to use the apps I create. The other 50% is for the nice people.

If I could say one thing ... you will get over the one ***, I did even though at first it really bothered me what he said. Some people just do not get it, you will never prevent the occasional ***** no matter where you go.

If you delete the app it will stay on the device, that's what happened when the Dive Computer was removed from the store.

If you want to force the users to eventually delete your app the best way to approach would be to update your app to do nothing or just display a message 'deleted'

But indeed people can be a real pain, everyone who publishes apps faces them... unfortunately. Try to focus on the people that do appreciate your efforts Chris.

Thanks for the great responses.

I've been very apologetic to the user, as I understand their frustration at loosing an activity. However this hasn't helped and now they've now continued to leave very negative feedback and started criticising other features.

It's also one of those issues out of my control. If the App crashes on pressing back, and then reboots the device; with no logs I can't do much apart from report to Garmin (which I've done).

I have reported them, but this isn't the first time over the 2 years I've been building Apps for the platform, and nothing happened from Garmin last time, and I guess I've had enough now.

I just don't think Users appreciate, the Apps are developed and provided for free, and expect that I am sat in some large house with my Ferrari from the profits I've made!

I like the platform, and the fact that I can build and release Apps for free. However it's this part of the development that is a problem, as the user expectation is so high.

Cheers
Chris

One issue that I didn't think of when deleting an App is that the FIT contributor data that was collected with the App will no longer be displayed in Garmin Connect for any workout collect with the App.

I used to have separate data fields for each device, but then when the build exclude functionality came out, I was able to reduce to 1 Data Field for all devices but this required that it be a new Data Field instead of a revision. I deleted the old data fields to help prevent confusion and clutter on the App store.

Now Moxy data for the old data fields no longer shows up in Garmin Connect. It's still in the FIT file so it can still be shown in other services like WKO4.

It would be nice to be able to Archive or Obsolete an App instead of having to delete it.

I can confirm that when an app is removed from the store, it is retained on a user's device until they choose to remove it via GCM or GE.

Regarding Chris's issue, we looked at it earlier this week and passed it on to the device teams to investigate further. We have a few ideas about what's happening, and it appears to be something in firmware.

I hate to see people throw in the towel over a bad experience, but I understand the frustration in situations like this. I encourage everyone to move beyond the trouble and continue to publish great apps. As a Garmin employee, of course I have an interest in seeing Connect IQ succeed, however I also do this work because I enjoy it (as do the other members of the Connect IQ team). It's gratifying to see individuals using the stuff we've made in new and creative ways that enrich the lives of others. Although I realize everyone cannot attend, we do plan to discuss promotion and monetization of Connect IQ apps at the upcoming developer conference. We know it's something a lot of people are interested in, and we want to respond to that interest in the best way possible.

Thanks to all of you that have contributed to Connect IQ by writing and publishing apps, even if you decide it's not a good fit for your purposes!

Thanks Brandon for the positive words.

I do agree, that a single angry user, should not put developers off. However it does (speaking from experience), and it makes me question why I develop for ConnectIQ. You will always get more negative feedback, as people are more likely to complain than praise in these situations. The worst ones are the negative reviews which say 1 star “love the app, and would give it 5 stars with this feature”!! On dark nights, where you have other priorities (like your own paid profession) dealing with an angry user is the last thing you want. I also still believe, these users feel they have a right to complain, as the feel we make lots of money from it, or do it full-time – which without an income is not possible.

I am glad to hear the conversation about monetization is happening, as this could help. I would also like to highlight again the point I raised a couple of years ago on the forum about gamification. I think there is an option for developers to be rewarded with discounts or access. I love Garmin, and buy a lots of their devices, which ultimately get used for testing – however I pay the same as the general public.

Cheers
Chris

Love that idea. Point awarded based on the number of downloads giving discounts towards new watches that can be used for testing.

A developer discount would be very nice. I totally agree .. that some users are just aggressive in their demands, and I also believe that some feel that we are paid by Garmin to do what we do.

For example .. I just bought 2 straps for my Vivoactive HR and the bill .. $120, pretty steep. I wanted them right away, as a device that I cannot wear is pretty useless. A discount would help lessen the blow. I do not live in the US, the land of cheap consumer goods .. thus this issue. I would love a monetized store, as it would help with the feeling of being taken advantage of by users.

I know some make things like special features etc for paid users .. but I am not that excited to go there, but maybe that is what it takes but I believe that few are willing to pay anyways.

For multi devices, see if you can find someone that has a device different than what you have, that doesn't have what you have. When one has an issue on a device they don't have, the other can help with sorting it out on the real watch (and verify fixes). It's not something you want to make use of all the time, but can help in a pinch.

Also, I've had some really helpful users, where I can send them a sideload that's a debug build (sometimes with some Sys.println() info) that help with fixing things on a watch I don't have.

When it comes to Garmin helping get devices to developers, don't know if you saw this post!

https://forums.garmin.com/showthread.php?368578-Who-wants-a-FREE-fenix-5-(not-a-joke)