Despite how bad I really hated the few times I had to work in Android because of its 'way more beta than even Siri' feeling, this is an intern who probably has little clue about what the upper boys are thinking in terms of priority. Any perception that they don't care is really just his personal view.
And I wouldn't really trust him to know what's up in iOS given a lack of any qualifying data like say just the fact that he's written an app for the device.
He makes some general statements about Google's priorities, but it's on a general level - design and development principles, something every developer working there would know. I don't see where he claims to know "what the upper boys are thinking". He just says "this thing is important, it hasn't been done yet, I think it should have high priority". The comment from the engineer sheds light on the technical obstacles and makes it obvious why it hasn't been done yet.
If Google considers the issue to be worth the effort at this time, they are probably waiting for the next major OS version or some other time. It would make sense that they collect issues whose fixes require breaking application compatibility, and then fix all of those in one go to minimize trouble for the devs.