If your working on an big update but don't want to give the impression of inactivity, write a blog post about it so that your customers can see that you haven't been hit by a bus.

Other than that, I push fixes/updates as soon as they are available and tested.

Severe emphasis on the and tested part. Lots of people out there have the one-line-fix mentality where they think fixing one line can't POSSIBLY break the code. Pushing changes that break your app are, to put it lightly, not desirable.

Edit: And please don't push an update just for the sake of pushing an update, there is nothing wrong with your app not having been updated in awhile if it isn't riddled with bugs. I frequently work on more than one line of development at once, if I'm implementing a feature and someone files a bug report, because I'm the only developer I put the feature on hold and fix the bug.

If your working on a big update but don't want to give the impression of inactivity, write a blog post about it so that your customers can see that you haven't been hit by a bus.

Other than that, I push fixes/updates as soon as they are available and tested.

Severe emphasis on the and tested part. Lots of people out there have the one-line-fix mentality where they think fixing one line can't POSSIBLY break the code. Pushing changes that break your app are, to put it lightly, not desirable.

Edit: And please don't push an update just for the sake of pushing an update, there is nothing wrong with your app not having been updated in awhile if it isn't riddled with bugs. I frequently work on more than one line of development at once, if I'm implementing a feature and someone files a bug report, because I'm the only developer I put the feature on hold and fix the bug.