I tend to agree with most of the other commenters - don't fall into the "I need a technical person because I can't do it myself" mantra. Build something, anythi

I tend to agree with most of the other commenters - don't fall into the "I need a technical person because I can't do it myself" mantra. Build something, anything, to get off the ground. Learn as much as you can, by yourself. This will also help you manage and monitor technical work later on and woo technical co-founders potentially (who rarely like to work with non-techie types). Like others have said, ideas are a dime a dozen. Execution is what matters. Most apps nowadays can be (rudimentarily) recreated over a weekend - it's likely that almost nothing you are doing is so revolutionary that is should be considered a state secret. If you are THAT worried, it could be a sign of insecurity in your ability to execute on the idea, not the threat of losing the idea itself to someone else. Keep that in mind. Think of it this way, the Twitter technology itself was not exactly revolutionary and there were literally thousands of copycats after it launched, but their execution is what set them apart and helped them gain the traction they needed.