I think there are sort of two main types of Android users:
1) Regular, non-techy people who would either buy an iPhone if they could afford one, or just don't care about mobile platforms at all so long as they have a camera and Facebook and can check their email.
2) And neophile, beta-tester-types, who like to tinker, and who actively do not want an iOS device for various technical or philosophical reasons.
I would not be surprised if the latter were (at least at one point, if maybe less so now) disproportionately represented among your users, because of their inclination to put up with less than fully-mature experiences, for the sake of checking out something new with interesting potential.
iOS people keen to check out something like cake.co are, I would guess, disproportionately Silicon Valley-types either involved in start-ups, or who actively follow that scene -- (non-neckbeard) tech hipster Apple enthusiasts who regularly retweet the sage sayings of SV-VC gurus. :-)
No doubt the iOS app kept some of those iOS people around, but it really seems to me that you're going to want the type-2 Android users (among whom I count myself) to stick around and contribute also, so as to get some critical mass of content here to make the structure and features of this place make more sense. And an Android app would probably help to some significant degree.
This was a serious pain to type because of the scrolling/typing issue with cake.co in Chrome Android -- I don't doubt that that's a Chrome bug, but I definitely do not encounter it on all web apps. Also, it has been easy for me to forget about cake with the lack of notifications.
Would an experimental Flutter or React Native, cross-platform project be feasible with your existing web and iOS developers, if a full-blown, full-native Android team isn't a near-future option?