Be aware of the annoyance factor of very frequent releases. It's one thing to update your web app daily, or even more often, so that users automatically see whatever small changes you've made since the previous release. But if a user has to take some action, however small, to install new updates, frequent updates quickly become tiresome.
I've encountered apps that seem to need constant updates on both iOS and Android, and it leaves the impression that the software is of low quality. Changes from one version to the next are often so small that they're hard to notice, so as a user I assume that all those updates are mostly bug fixes. And if the changes are noticeable, it makes the app feel less predictable, less familiar.
I'd say that if your app isn't solid enough to make it available for at least several weeks, consider waiting to release until it is. I know that sometimes bugs aren't discovered until after release, and of course you should fix significant ones ASAP, but if that happens more than once in a while you should look at ways to improve your testing process.
Another way to look at it is that every time you release a new version of your app, you're saying "Hey! Look at this!" If you do that too often users who might have been impressed by all the new stuff you added between version 1.0 and 2.0 will instead be bored by the minimal differences between 1.9.6 and 1.9.7.
A better approach is to design your app so that you can update content as often as you like without updating the app itself. If you know that you might want to change the app's appearance around various holidays, for example, build your app so that it can download themes from a server instead of updating the app before and after the holidays.