Etiquette

When you want to stop maintaining something, do you just leave it to slowly fade into obscurity, actively delete it, or something else? 

And why did you choose to do it that way?

  • Yet another option is to make the two apps the same.

    Really trying to avoid that!

    For one of my DataFields, a user so liked the concept and wanted to be able to store different settings for his short runs, long runs, interval sessions, recovery runs etc. that I ended up with a multisport version, four single sport versions and a spare one for CIQ1 users... When I need to do an update it is, believe me, a very tedious task. Disappointed

    You will doubtless tell me there is a better way to manage discrete settings profiles (and I would love to hear it), but until 3.2 (I think) there was no way to edit DataField settings from the watch. (Not to mention the memory impact of each additional setting.)

  • There isn't a perfect way out. You are going to have to "pay" something to get out (you just need to figure out what the "least expensive" option is).

    Making the two apps the same has to be easier than having two different apps. It also could be a step to killing off one of them.

    It seems like the only (major) difference between all those versions is the name.

  • Even if it's only being used by 5 people in the world, no reason to remove it if it has no impact to you.

    The problem is that if you leave it in the store, more people will download and complain or ask for new features. I had a handful of apps in the store and I don't have any time to maintain them. The easiest solution was just to remove them.