- Porting from iOS will take more work, but the API support is much better. It gives you a universal app solution you can develop on to make use of native Windows 10 features and APIs, but with Android you may remain limited to what’s available in the translation layer.
– Your ported iOS codebase can be used to target other devices, while so far as we know the Android translation layer will only be supported on Windows Mobile for now.
– A ported iOS app also gets compiled native, while an Android app uses a translation layer. On high end devices, for many apps the experience might feel equivalent, but on lower end devices it may suffer. We haven’t yet seen what performance is really like in a final release, so it’s not known how much the performance will differ.
– Maintenance is easier with Android, since you can just make your changes and then Windows Phone gets them for free. With iOS, you’d need to either re-port the updated version of your app or apply those changes directly in your existing ported code. Depending on complexity, it may be a problem for you to have to maintain 2 codebases. However, if you want your Android app to feel like it belongs on Windows Phone, you’d probably end up having 2 versions of your Android codebase to maintain anyway.