The article also seems to indicate that their repository strategy is not properly set up for something like this. Most people, I think, would initially set up

The article also seems to indicate that their repository strategy is not properly set up for something like this. Most people, I think, would initially set up a separate repository for iOS and for Android, given that they are different codebases, and you wouldn't want commit history pollution. But if you're planning on reusing a lot, like in this project, it might make sense to have them both in one repo. Or have a third for shared code, and include that in each individual one?