1. Continued income from it (people aren't going to continue to buy it if the bad reviews keep coming in).
2. You keep/improve your reputation. If your software isn't working well for any reason at all, it can give a bad reputation to the person/company attached.
3. You increase the chances of a good buy-out in the future, over what it would currently bring now.
We all know it can be difficult to get traction on a project, not to mention paying users. You already have proved this one can get both.
Thanks for advice. The main issue is that I have better traction/reviews/revenue on another app, and the work required to get #2 and #3 on your list would seriously detract from the attention I could give to that other app.
There have been a few times where I've followed that exact logic to fix it up, spent a weekend or two on it, and gotten pulled away again. The software has reached a size where it's hard (mentally) to switch back and forth between it and my other app.
The other issue is that now that I have more experience doing Mac development, I'm starting to see that it's not a simple matter of bug-fixing. Some significant development would be needed to bring it up to the same level of polish as my other app, and in the meantime I'm concerned it's detracting from my App Store reputation.
You get 3 benefits:
1. Continued income from it (people aren't going to continue to buy it if the bad reviews keep coming in).
2. You keep/improve your reputation. If your software isn't working well for any reason at all, it can give a bad reputation to the person/company attached.
3. You increase the chances of a good buy-out in the future, over what it would currently bring now.
We all know it can be difficult to get traction on a project, not to mention paying users. You already have proved this one can get both.