zlacker

But can you reuse UX? UX on Android and iOS are completely different, which implies different UI, which in the end of the day implies different codebase. I do believe that it's possible to implement an app indistinguishable from native with any technology given enough time to implement all UX guidelines (voiceover support, animation dynamics like scroll list velocity constants, disability stuff, etc) but than we spend too much effort reinventing Cocoa Touch, so ROI of this endeavor is highly speculative. I hope in the future iOS and Android will be closer UX wise, which should simplify code reuse and make everyone happy.

>>dmytro+(OP)
Well the UI can be changed per platform, and as I said, it's a matter of budget. I implemented a solution like that with xamarin but it's not like web. It's way more complicated and the real problem is many things are not supported and so on... React Native? No desktop support. Qt? Oh no, it doesn't feel native... Give me a break! I'm really sick of everyone being a perfectionist and making no compromises. There are too many users, too many platforms and not many developers (at least, quality ones). Facebook can maintain 100 platforms, that doesn't solve my problem of having something "usable" (not perfect) on X platforms.

- Yeah we don't support offline mode on iOS, sorry.

- How much would it cost to implement that?

- Hmm, a rewrite plus more devices to test and licenses and... hmm. Just 50K for a start.

- What, are you kidding? I just want to enter this order when offline?!

>>dmytro+(OP)
No single top 100 app (except those made by Google or Apple) uses the default system UI components. Google does not follow its own UX guidelines.

Everybody by now knows what a hamburger button, tabs, and toggle switches do.