You just have to be sure you don't eliminate the customer support with documentation, and then not ever fix the problem. I think it's better to feel the pain in

You just have to be sure you don't eliminate the customer support with documentation, and then not ever fix the problem. I think it's better to feel the pain in the short run, and have a better product in the long run. This reminds me of another thing we do - when we make new apps, we don't provide a manual to the beta group. We make one after the fact, but we want to get feedback from users as if there are no instructions. Your product is awesome btw. We use it in two apps, and plan to add it to a third soon.