5 ms·

This sounds great in principle and I saw this tried for several years for Dropbox mobile. It was a failed experiment though: > By writing code in a non-standar

This sounds great in principle and I saw this tried for several years for Dropbox mobile. It was a failed experiment though: > By writing code in a non-standard fashion, we took on overhead that we would have not had to worry about had we stayed with the widely used platform defaults. This overhead ended up being more expensive than just writing the code twice. https://dropbox.tech/mobile/the-not-so-hidden-cost-of-sharing-code-between-ios-and-android https://dropbox.tech/mobile/the-not-so-hidden-cost-of-sharin...

sirwhinesalot 4y ago
Isn't the Dropbox desktop app Electron crap these days? It's certainly not the pleasant experience it used to be. Plus what you're talking about there is the opposite of what I'm suggesting, you wrote 2 UIs with a shared C++ logic, I'm suggesting two native platform layers with hosted webviews.
- aejae 4y ago
  > Isn't the Dropbox desktop app Electron crap these days? It's certainly not the pleasant experience it used to be. Sadly I agree. However the blog post I linked describes their mobile strategy. Sorry about the confusion. FWIW The desktop app now uses the strategy you suggest: native with many hosted webviews. > what you're talking about there is the opposite of what I’m talking about Sorry, skim read and missed that! See above comment re Dropbox desktop using your approach though.