Well, we've all agreed they need to communicate more.
It seems pretty straightforward to me. The only way I can see that it originally meant Android would be done before general shipping would be if their comments about taking 2 weeks for treg (IF no problems were found), but even once it was approved to ship, it would take another couple of months before it began.
But, as it happens, I've done a little further checking:
From June 2015
TextBlade's companion app (which allows MultiMap users to create custom maps) is available for iOS at first ship. Mac uses the same code base and will come soon after.
Android is a more significant port (since we have a large iOS / Mac code base), and will take a couple months. We'll kick this off once the iOS version is complete. Android also runs on a wide variety of hardware, making the process of vetting software more involved.
So, AT FIRST SHIP it would be just iOS. Android taking another couple months which would therefore put it after shipping.
From February 2016
TREG tests will be complete when users give us the thumbs up. Based on what we find together, that may take as little as a week, or up to several weeks. As soon as the TREG folks are happy, we'll start general release.
Of course, "as soon as" doesn't necessarily mean the same moment, but certainly would not be a very long time once approval was given.
From April 2016
As has been previously confirmed frequently, android revision will start after first (iOS version) is completed.
Should be up on Google about two months after general release begins.
So, I think, at least at the times these things were said, that it was intended for Android to come after general shipping began and iOS version was done. We do not know when it the iOS version will be "done". I certainly expect further updates after shipping anyway. I can say that some things in the iOS app are not functional yet though most are . They may not even have all those things active before shipping as some aren't that critical. We just don't know at this time.
But then, those statements go back quite a ways. So it wouldn't surprise me if whoever works on the apps were already working on the Android version. It's like when people complained about something being added to the app that wasn't announced originally - claiming that these new things slowed progress down. But not if it is different people. No reason for the app people to do nothing while unexpected issues are dealt with with other workers.
Same for the Android app. If the hard work on the iOS version is solid enough that they don't have to worry about big changes, I wouldn't object to them starting work on Android before shipping starts - and maybe that would mean it is ready before shipping as a result. But nothing has been said that makes it a gating issue.