It’s not quite WKWebView, but I think it’s a relatively decent approximation. Unfortunately, I’m in a place where I can test your argument, so the best evidence I can give you is the personal anecdote that I run Slack in Safari rather than using the Electron app for performance reasons. I’m making a shot in the dark here, but I’d think that given access to their iOS project I could whip up something passable within a couple of months, if not less. Ok, sure, but most of this work has already been done for their iOS app. #SLACK FOR MAC APP DOWLOAD CODE#> Regardless, there’s still a complexity cost - unique native platform UI code is still unique native code, plus all the localisation, QA testing, etc, etc fun that will entail for an app the size of Slack. The benefit of using C++ is that you can call it easily from most languages. Generally, all the cross-platform, UI independent bits go into the framework, and then you write a thin UI layer on top of it using your platform’s native UI APIs. > I can see why it might potentially be attractive in purely architectural terms, but I wonder if the “savings” meaningfully materialise in practice when so little pure native development occurs in C++ on iOS and Android. Last I heard, Dropbox has moved towards using Python for everything, which gives them kinda horrible performance IMO. > I recall reading years ago Dropbox trying this One of the projects that I am tangentially involved in is doing this, but swapping out C++ with Rust. In my opinion, this is probably the best way to actually do decent cross-platform development. I think Microsoft Office does this too, and I’m pretty pleased with the results, performance and UI wise. Do people still regularly try to ship common platform code as a shared C++ library to minimise unique code bases for their mobile apps?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |