I'm sure you and your team are well versed in everything to do with Timmy, but please understand that no-one else has any idea what you are talking about. Uh-huh. I see a lot of lightning. That's a nice slideshow you put together there. Very impressive. I might look at the source to see how you did it. WTF is Timmy?
Imagine I pointed you to a link called Michael Evolved, with a nice slideshow and music, telling you that now, Michael is moving to the Next Level! Sign up now for the Michael private beta! You visited the link. You gave it several minutes of your attention. You have no fucking idea what it is talking about. You'd be posting the exact same thing back to me. Who, or what, is Michael? Who knows! Maybe ask Timmy!
By the way, are you angry or something? I don't understand why you are pissed off like that.
There's such a thing as releasing too early. If the idea is not fully developed, and or its architectural ramifications still being explored, releasing early can trap you and make it far more difficult to evolve your concept.
If you're absolutely sure of what you're doing, what you want it to look like, how it will work, and you're just building gradually towards this well-defined final goal - great, release early and get users on board.
But if you're not sure, don't! Once you get a few users who trusted you and put their time into your project, no matter if it was free or not, you can't just walk away. Well maybe you can but I can't.
When you release something, you ask users to commit to your project. It's unfair to do that unless you're equally committed.
I'm a big fan of private betas, where you can flesh all this stuff out before asking strangers to put their time into your app. Very private betas, if need be - just you. Release early and often - to yourself. Maintain a runnable state at all times. Use your app intensively, eat your own dog food, evolve it that way. I like this kind of advice, not 37Signal's cookie cutter platitudes.