> Has anyone found a point of contact at Google regarding the Maps API and > Flash?
I don't want to be a debbie downer, but Google is historically horrible when it comes to things like this, and there has been a huge volume of annoyed messages posted to their google groups board about the flash API deprecation over the last few years, none of which made any difference. I wouldn't spend any energy trying to get Google to do anything regarding their Flash API. They're not going to open source it, they're not going to support it, there are existing obvious bugs that they aren't going to fix [1]. And note that the way their Flash API works is that the swc they give you is just a shell that loads a SWF at runtime from their server, which has all the real code. Which means that when they decide to turn that off, your existing apps built on the Flash API will stop working. Their end of life date doesn't just mean you won't be able to use that flash API in new apps, it means old stuff will likely stop working. I'll also point out, Google really doesn't want you using their API in anything but a free publicly accessible HTML app that uses their JS library. If you're doing anything else (commercial use, behind a paid login, loading their tiles in another map component, etc) you are almost certainly breaking their terms of use. Google's business is selling ads (sometimes on maps). And yes, it's a massive shame because Google has the best basemaps, best geocoding, streetview imagery, and best routing. But they are about as unfriendly as you can get when it comes to making it easy for commercial developers to work with them. [1] https://code.google.com/p/gmaps-api-issues/issues/detail?id=1241&q=apitype%3DFlash&colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Stars%20ApiType%20Internal
