Well I have been developing native apps for both for over a decade, and I don't think either is particularly more difficult than the other.
What it came down to is that I use an iPhone as my daily driver, and when I pulled my Android test device out of a drawer the battery was twice the size so I immediately brought it to an electronics recycling center.
Which means that in order to complete the Android version, I need to shell out $400 for a new phone I'm only gonna use once for a non-commercial project. So my idea was, let's release iOS first, see if people care, and then I'll spend the remaining time and money to finish up the Android build!
I think if I did try to finish Android at the same time, I would have given up on both and released nothing.
What it came down to is that I use an iPhone as my daily driver, and when I pulled my Android test device out of a drawer the battery was twice the size so I immediately brought it to an electronics recycling center.
Which means that in order to complete the Android version, I need to shell out $400 for a new phone I'm only gonna use once for a non-commercial project. So my idea was, let's release iOS first, see if people care, and then I'll spend the remaining time and money to finish up the Android build!
I think if I did try to finish Android at the same time, I would have given up on both and released nothing.