Skybolt, I'm not sure I understood this. Can you expand a bit further.
In the new dispatches model, you get a congrats dispatch when you level up. It would be nice if tapping that dispatch brought up the glory page again so you could screen shot it. A future feature.

The initializing screen could use some work. The biggest issue is that Android freezes the UI thread as it is drawing other pages (getting ready to render the map, menu, etc) so a progress bar in our initial design looked bad because it started to draw, then froze. The rotating hexagon seemed to cause less panic when it stopped spinning.

1. the google map control isn't super awesome
2. this was to facilitate searching for Atlantis. Adding texture to the water helped know you were panning, but we will keep looking for alternatives
3. We have worked on this text quite a bit, still not perfect
4. Blog post coming today
5. I've toyed with the option of having an alternate launch display that you could select from settings. Let cool, and more static for the hard core.
6. QONQR Blue was designed with the goal of having color theme packs (skins) players could buy to customize their scope. It may never happen, certainly not soon, but that was one of our design goals.

yes the public rooms have different behavior. There are no room topics or membership to manage. You also can't post pictures (right now only works on web) in public rooms. We could do a better job of making the difference more obvious by adding a "public room" "private room" header.

We have leader and capture to be added to the launch wheel on the bug list (feature). We may also make it so tapping the zone information in the lower left/right may also jump right to leaderboard. That is harder to do since it skips a page in the current navigation (launch wheel), but could be an option.

That is only supposed to happen if we somehow got into a state where there was a popup with no children. It is safety code that should never fire. We'll double check to see if this is still a problem. Hopefully it is already fixed in the code that hasn't be released yet.