4 ms·
SwiftUI is better than React and CSS... on iPhone. It’s not going to help you at all on Android. So at a bare minimum you’re replacing React and CSS with two to
by untog 6y ago
SwiftUI is better than React and CSS... on iPhone. It’s not going to help you at all on Android. So at a bare minimum you’re replacing React and CSS with two totally different UI implementations. Maintaining two separate code bases (and hiring engineers to do so) is not simpler than React and CSS. And we haven’t even started talking about desktop.
And I’m not convinced about the “hacked” argument. How can anyone be hacked via any web browser on an iPhone? At least on Android they could download an APK without knowing what they’re doing but default security will stop them installing it. Meanwhile we’ve recently discovered that a ton of native apps constantly read the user’s clipboard, something web sites aren’t able to do. So it’s nuanced at best.
But IMO the biggest argument for the web is simply that you don’t have to install it. If I’m shopping I want to browse through a few different sites, I’m not going to download and install an app just to look at one product listing.
- postfacto 6y agoI’ve found the two codebases approach, one for iOS and one for Android, is simpler and cheaper because native development tools are just so better.
- untog 6y agoThen you’re doing web development wrong, frankly.
- wdb 6y agoYou will always keep separate code base for Android and iOS due to difference in the interaction paradigms between the platforms. Doesn't matter if the code is in Javascript/CSS or shared via Swift between Android and iOS. For native apps. For web it's different but you see more and more webapps following the Android's Material Design which for me feels awkward on Windows or macOS.