I read the original question as asking why Google didn't add Flash onto its interface. I suppose it might be possible to replace their current JavaScript functions with Flash bytecode, but given the lengths they go to already to compress their JavaScript, I'd be surprised if the benefits there would be worth the trouble, not to mention any possible costs they might end up with due to migrating to Flash. (Browser support, version changes...?)
| AMF is also generally smaller than JSON or XML.
I kinda recalled Gmail (for instance) not using XML, but I dumped a session through Firebug to make sure. They're using their own (very simple) data format, and I doubt that AMF, or SOAP, or anything else could beat it, short of using actual data compression on both server and client side (and, again, probably not worth it).
Crawling through the Gmail code and data only reinforces my guess that their services are designed with low bandwidth usage among their top priorities.
A lot also has to do with their respective cultures - as a JavaScript dev, you learn to do more with less because doing more with more is so exquisitely painful. That's why Flash UIs are often visually more attractive - it's easier for them to be visually attractive.
And JavaScript compresses really well - it's not unusual for GZipped + minified JavaScript to be less than 20% the size of the uncompressed source code.