Dropbox engineers explain why they gave up sharing code and used native languages

Dropbox engineers explain why they gave up sharing code and used native languages

Dropbox engineers explained in an official blog post why the company abandoned the strategy of sharing code on iOS and Android and switched to using the native languages ​​of each platform . Dropbox initially chose C++ when developing iOS and Android mobile apps. The idea behind it was to write the code once in C++ instead of writing it twice in Java and Objective C respectively.

But now Dropbox has abandoned this strategy and switched to using Swift and Kotlin, the languages ​​of their respective platforms. The reason for this decision is that the hidden overhead of sharing code is actually very high, which is ultimately more expensive than writing the code twice.

Dropbox said that to share code you need to maintain your own frameworks, libraries and development environment, solve the differences between different platforms, and it is becoming increasingly difficult to recruit and retain experienced C++ developers. These expenses ultimately make sharing code not as simple and cheaper as developing with the IDE of each platform.

<<:  Can India become an exciting battlefield for Apple's "PUBG"?

>>:  Ten tips to speed up Android app building

Recommend

Fan Deng Reading User Growth System!

Fan Deng’s annual revenue from reading books has ...

Why are wetlands called the “Kidneys of the Earth”?

Did you know that wetlands only cover 6% of the E...

Will eating crabs cause children to suffer from precocious puberty?

Do you like eating crabs? It is the season of cra...

Are Chinese rockets really starting to burn "coal"? | Expo Daily

Your best "insider" in the scientific c...

The technical secrets behind Alipay's Double 11 sales over the years

Since the launch of the e-commerce festival Doubl...

Providing offline support for mobile apps

Offline support for mobile applications can be un...

23 thoughts on marketing, operations, advertising, and new media!

For some questions, I always like to go back and ...