Gabrielle Earnshaw
1 min readMar 10, 2019

--

Hi Saar, great article. I did the same ‘experiment’ as you three or four years ago, except for professional services rather than a start up, and I came to very similar conclusions as you did. The main reasons for me ultimately moving my team to native development were as follows. 1) Mobile technologies move fast, and it can be difficult to keep up with dependencies at the best of times. With cross platform you introduce a whole new layer of dependencies, and managing them is at best painful, at worst impossible. 2) Even with cross platform, you still need native expertise. You need people who understand how things should work on Android and how they should work on iOS, and you need to be able to drop down into native code to write custom libraries. However when your team is focused on cross platform, it’s not easy to acquire that expertise. 3) Cross platform technologies come and go. There’s a strong chance that if an app has longevity, you will end up having to port the code to a different platform at some point.

--

--

Gabrielle Earnshaw
Gabrielle Earnshaw

Written by Gabrielle Earnshaw

Making Mobile Simple. Mobile App Strategy, Leadership and Engineering Expert. makingmobilesimple.com

No responses yet