[tastefulwords]

I would advise you get started coding as soon as possible. And there's two reasons I'm giving you this advice:

(1) no "learning experience" in the world compares to actually having to do something to your app's code -- I've been doing development for 10 years, and this is basically how I "learned" everything; by actually having to do it.

(2) your idea will probably change once you start working on it; they always do.

And don't worry: it's very unlikely that someone will just decide, out of the blue, to execute the exact same idea as you. And even if they do, the thing to remember is that it's the execution that matters, not the idea itself.

[shubhodeep]

Yeah, I understand that point - but I'm still a bit unsure how to hit the ground running - you know, the initial qualms, what's the point that I start at? Do I just dive in and learn on the go? Or learn a bit, create, learn more and develop and so on.. ? Glad to have some pros provide some great advice!

[tastefulwords]

What I would do -- what I actually do do, as a matter of fact -- is dive right in and learn on the go.

Necessity is the mother of invention -- or, in our case, the mother of resourcefulness. I.e. nothing will make you learn something faster, and better, than having your website crash/not-work if that particular something isn't done right.

That being said, don't go overboard; or be overconfident. Do practice the basics, before diving head first into your new website/app. And by "the basics" I mean getting a website up and running.

Then, you take that and you run with it -- as fast and for as long as you can. There; that's the secret to startups, right there :)