[jdg]

I built the first version of Boxcar (http://boxcar.io) in a weekend -- because I was bored. Started on a Friday, submitted to Apple the following Sunday evening.

Since then we've grown to 1M+ users and have delivered 2B+ push notifications. We're a team of 4 now.

For mobile apps, your tools are basically decided for you already. Eclipse for Android, Xcode for iOS. The goal of an MVP is to keep things as stupidly simple as possible. Use external APIs if they already exist, use services like Parse, etc, to give you a leg up.

MVP is less about code and more about results. If you can get away with no coding at all, that's the ideal situation. :-)

[ajaxguy]

Seems to be an impressive app. So, when you say a weekend, you got that MVP from inception to live app? Normally, ideas are spontaneous and it will take some time to get the right feel of it. So how did that happen with your boxcar?

Yes, you are right for the basic tools like Eclipse and XCode. But to integrate different product apis, like Parse/Nodejs it would already need a groundup knowledge to use them in your app. This is where I am lagging behind. I want to know how do you manage these kind of situations.

I belive this process is more of a progressive manner than a complete solution at one go.

Sincerely, it would really inspire me to read such kind of posts here and believe I am way too far from the fellow hn'ers.

[dotpavan]

Nice advice! One finds 2 paths I guess- to focus on the medium (code, framework, etc) or on the results for a MVP.. once the MVP gets enough traction, then even rewriting the whole app is not bad as long as we know the idea has potential.

[vijayr]

upvoted for "If you can get away with no coding at all, that's the ideal situation. :-)"