So you have had an idea for the next Twitter or Facebook app. The idea is like rocket fuel! Your personal brain is full of ideas to tweak and twist your concept, capture your user base, monetize your audience, to realise your dream from notepad to server.<p>You've invested endless sleepless nights building a rock solid scaleable backend - But your desperate to take that step and get your app live. To get your web-services responding, and your cloud filling with rich-user data.<p>You ponder your big move. If your idea is to really grab it's audience the UI has to be slick, right? Rich in Ajax and CS5 like sweet tasting ginger on a firm cheesecake. But of-course you could just sprinkle the ginger once your live - right?<p>After-all an app is not something that is complete, it’s something that is evolving. Twitter did it. Why hold back? Why keep it under the hood when a small base of users could start testing your app-model and giving you feedback. Right now.<p>If you were super smart you could just launch a mobile service. The UI is much simpler reminiscing sites way back before Ajax and CS5. And when you dig deeper in thought, phone users are a large target in your audience. That would get a solid UI out and running in a flash, and your beta users could really evaluate your IDEA,rather than how it does it. Comparing your mobile site on and even par to the likes of Facebook and Twitter. And while that’s getting feedback you can get the screen version live, in all it‘s glory.<p>Or on the other hand you could just hold back. Go to work on the sweet tasting ginger that tops your cake. Build your super slick interfaces, driven by that rocket fuel that has powered you this far.<p>You ponder your move. What do you do. Build the mobile site as a Beta launch tester, as a product to tease investors and on-lookers. Or hold back with your idea. Bite your tongue, endure your heart pounding and push on until you have the Ajax Ginger sprinkled beautifully over cheese cake?<p>Thoughts please…