@Diordna,
Thanks for the thorough walk-through and your thoughts! Let me give a few of my own.
About speed on WOW and others
We wrote PhoneMyPC to provide a 'default' experience that would let you see your PC "as is." That means high-resolution, deep color, etc. This approach has come ramifications, first amongst which is the simple axiom "The more pixels you are looking at, the slower it will be."
It seems obvious, but consider this: if you want to play a game or watch a movie, nothing you do can show you more than 480x854 pixels (on your Droid), because that's the device's native resolution. But, you CAN control how many pixels are captured from the PC screen to fill that box with.
Let's say you have a 1280x1024 monitor.
When you watch a full-screen movie or play a game in full-screen, you will zoom out on your phone so you can see the whole PC screen. Each time PhoneMyPC wants to update what's on your phone, it must gather every changed pixel in that whole 1280x1024 area, shrink it to the proper 480x854 size, compress it and send it to your phone.
On the other hand, if you resize your window on the PC to something nearer 480x854, then PhoneMyPC only needs to capture that many pixels (maximum), does not need to shrink it, and then compresses and sends to your phone.
The end result in both cases is a Droid screen full of PC pixels, but the second approach can be much faster. So in general, run videos and games in smallish windows, similar in size to the screen on your phone.
Finally, network bandwidth is more impactful than any other metric on performance. The good news is that we chose the technologies for PhoneMyPC in light of the fact that they work "well" today, but all major carriers near-term roadmaps show the adoption of 4G, LTE and technologies that could push the current 1 Mb/s speeds well over 10 Mb/s, and PhoneMyPC will be radically faster then.
Broken WIFI
Your report here is odd. I wonder: did it work at all when on WIFI?
I can think of two possibilities:
1) If it didn't work at all on WIFI, they could be blocking the port we need to connect to our servers. This will be fixed in the next release (by using a port that is open nearly 100% of the time).
2) If it worked sometimes, but crashed too, this is almost certainly just a flaky network combined with our bugs. We know our code is not robust when the network is not, and we have many improvements to this for the next release. At a minimum, PhoneMyPC should slow down, or give you a warning, but the current release prefers to crash.
Our work
We are! We worked. Then we shifted to harder. Then hardest, and now we've just stopped sleeping, abandoned our families and we're "one" with our development systems.
Okay, not really, but we really are putting forth 110% effort, and will have another release out soon, then at least two more to follow quickly.