Ask HN: Release app as is even if only for Android?

After several months of hard work, moonlighting in the late hours after a 9-9 schedule (Japanese firm), I've reached a goal I set for app development, which has been done using Parse for backend, AWS for data, and Android for mobile client.

In the near future, 3 months to 1 year, I plan for the following technical developments:

-Swap Parse for a custom backend for cheaper operation (let me know if you have good replacements)

-Develop app for iOS environent (no experience here whatsoever, being in Windowsland)

-Develop webapp for "the web"

-Hit MechanicalTurk (and related services) for content.

Given my current progress, and my target goal of hitting all significant mobile and web environments, what do I do from here?? As a complete noob to startups, I am in a bit of an analysis paralysis. I want to release an MVP, but also don't want to reveal it too soon. I have validated the app concepts to family, friends, and coworkers to very good reception, so I'm not entirely worried it will be a complete flop, but I'm not going to make any claims that it will be a huge hit either. But if the app is a hit ( so I'm biased ), then I feel like releasing it now would be a strategic... something. I see 2 options and their related outcomes:

1. Release for android first.

-Get initial customer feedback for the entire concept.

-If concept fails, then I won't waste time on the idea.

-Earn some money while continue working on the other targets

-Risk of concept taking off, clones overtake me by being better/faster, especially with regards to iOS space, where there is the most money to be made according to popular belief.

2. Continue developing until I hit all target items, then release

-Have app presence on all significant mobile platforms

-If app becomes popular, potential users will not be prevented by lack of choice.

What advice would you have for a poor bootstrapper. Any advice is welcome, I would appreciate any guidance on this.