Start writing about the topic before you launch. Presumably if you're passionate enough about the space to spend N months slinging code you can at least write a few pages about it. (I need to be better at this.)
Why didn't you do this with AR? (Not being critical, just curious, because I remember you being a bit stealthy about AR pre-launch (of your demo, at least).)
Also, how would you respond to those that wouldn't want to do this for fear of "giving away their idea"?
Is just another case of being needlessly protective of an idea that is, in and of itself, fairly worthless? Or is the trick to write to about the problem generally and not your specific solution?
Something I've been thinking about lately: What if your product is merely a tool? Say, it's useful in solving a real problem, but it isn't central to any particular workflow. For example, OCR software. It can save massive amounts of time, but I can't imagine what I'd write on the topic. Am I just not being creative enough?
You are not being creative enough. Here's a list of blog post titles for you:
- OCR application(s) in forms
- OCR application(s) in vehicle registration plates
- OCR in archive digitization
- OCR in business card scanning
- OCR in mobile industry
With the simple formula of your product plus application fields you can generate hundreds of posts.
Also, how would you respond to those that wouldn't want to do this for fear of "giving away their idea"?
Is just another case of being needlessly protective of an idea that is, in and of itself, fairly worthless? Or is the trick to write to about the problem generally and not your specific solution?