@Tuco , seriously, just give em a bit of time, its literally been a week. Have you by any chance considered that they themselves might not have an answer to those bigger questions yet? I am sure they need to think such things trough and discuss them internally, considering all that a decision might entail.
Ive been an application architect & developer for almost 20 years now and I call that first week the white glove week. You know its going to have issues, people will be frustrated, and there is a good chance you lose their confidence in your system if handled poorly. It is a time of high communication; I PLAN on not sleeping for 2 or 3 days, and I respond to as many people as I can either personally or with broadcast messages addressing the common issues so people stop reporting them and I give ETAs and what we are trying to accomplish. I usually have a 24x7 conference set up for the first 48 hours so people can dial in with critical issues any time they need. These are at multi billion dollar companies, they arent small groups of people. Nothing like 1 million people downloading the game, but at a certain point scale doesnt matter, as its your end directing communication. Now, most of my stuff involves peoples ability to work and can impact revenue so its a different paradigm and criticality but at the end of the day I have found that that first week is a lot of hand holding and soothing efforts along with your dev cycles. You want cheerleaders, not critics. You get cheerleaders by making them part of the team.
Thats experience from Fortune 50 and Fortune 100 companies. What they are doing is odd. Why make a forum to talk when you don't plan on talking. Why make a feedback system that you don't plan on acknowledging. This isn't the only thread showing confusion at the process being used here and that is dangerous as people spam and create noise or they stop reporting as there is no trust that it is even being read. It doesnt take much to make a few posts and they go a long way.
