Apple today took a shot at React Native and other cross-platform frameworks.
I have thoughts.
First, the quote in question, from their keynote (around the 40 minute mark):
"Some other frameworks promise the ability to write code once for Android and iOS.
And that may sound good, but by the time you've written custom code to adapt each platform's conventions, connected to hardware with platform-specific APIs, implemented accessibility, and then filled in functionality gaps by adding additional logic and relying on a host of plugins, you've likely written a lot more code than you'd planned on.
And you are still left with an app that could be slower, look out of place, and can't directly take advantage of features like Live Activities and widgets.
Apple's native frameworks are uncompromisingly focused on helping you build the best apps."
I have thoughts.
First, the quote in question, from their keynote (around the 40 minute mark):
"Some other frameworks promise the ability to write code once for Android and iOS.
And that may sound good, but by the time you've written custom code to adapt each platform's conventions, connected to hardware with platform-specific APIs, implemented accessibility, and then filled in functionality gaps by adding additional logic and relying on a host of plugins, you've likely written a lot more code than you'd planned on.
And you are still left with an app that could be slower, look out of place, and can't directly take advantage of features like Live Activities and widgets.
Apple's native frameworks are uncompromisingly focused on helping you build the best apps."
First, their direct claims:
That you will write more code than you'd planned on.
First off -- this is cleverly worded. Notice they don't say "...you will write more code than you would have written for two separate apps."
This statement, honestly, could apply to any software project. I've never encountered a coding project where the end result was "wow, we wrote way less code than we thought we would" ... this is an evergreen claim.
That you will write more code than you'd planned on.
First off -- this is cleverly worded. Notice they don't say "...you will write more code than you would have written for two separate apps."
This statement, honestly, could apply to any software project. I've never encountered a coding project where the end result was "wow, we wrote way less code than we thought we would" ... this is an evergreen claim.
Secondly, the specifics:
- custom code to adapt each platform's conventions
This is honestly pretty rare. Mostly, it just works, because React Native uses the platform's primitives. Less than 1% of the code in any of the many React Native / Expo project we've worked on is dedicated to platform-specific UI changes. It just isn't an issue in practice.
- custom code to adapt each platform's conventions
This is honestly pretty rare. Mostly, it just works, because React Native uses the platform's primitives. Less than 1% of the code in any of the many React Native / Expo project we've worked on is dedicated to platform-specific UI changes. It just isn't an issue in practice.
- connected to hardware for platform-specific APIs
This is also rare, for most apps. And when this is necessary, you just ... drop into native code and write it how you would if it were a native app, and add a little bit of boilerplate to hook it up so React Native can orchestrate it.
This is a React Native strength, not a weakness.
This is also rare, for most apps. And when this is necessary, you just ... drop into native code and write it how you would if it were a native app, and add a little bit of boilerplate to hook it up so React Native can orchestrate it.
This is a React Native strength, not a weakness.
- accessibility
Probably the most valid complaint, but it can be done in React Native and done well.
Also: some of the worst accessibility experiences I've had were on native apps in the iOS app store.
What matters is a developer actually caring about accessibility.
Probably the most valid complaint, but it can be done in React Native and done well.
Also: some of the worst accessibility experiences I've had were on native apps in the iOS app store.
What matters is a developer actually caring about accessibility.
- relying on a host of plugins
Valid observation, but these are overwhelmingly open source.
What do you do when an Apple API has a bug? Report and wait. You have no ability to fix it yourself.
Valid observation, but these are overwhelmingly open source.
What do you do when an Apple API has a bug? Report and wait. You have no ability to fix it yourself.
Second direct claim:
That your app could be slower
@jmeistrich went and put time into his Legend List and made it incredibly fast, using just JavaScript. The speed limit isn't React Native.
Just like accessibility, it just takes a developer who cares about performance.
That your app could be slower
@jmeistrich went and put time into his Legend List and made it incredibly fast, using just JavaScript. The speed limit isn't React Native.
Just like accessibility, it just takes a developer who cares about performance.
The new architecture in particular opens up so many more options for performance, as well.
Sure, your app could be slower. It could also be faster, faster to market, take less time, smaller team, cost less, and allow you to build a business around it.
Sure, your app could be slower. It could also be faster, faster to market, take less time, smaller team, cost less, and allow you to build a business around it.
Third direct claim:
That your app might look out of place
Google doesn't think so. They named an Expo / React Native app the best app of 2024.
That your app might look out of place
Google doesn't think so. They named an Expo / React Native app the best app of 2024.
https://x.com/ccheever/status/1858697505707618706
Not to mention the many times Expo / RN apps have topped the App Store for many categories.
https://x.com/ccheever/status/1859668127136743877
Actual users like (well-built) React Native apps. And maybe we should listen to...actual users.
https://x.com/ccheever/status/1887035897121792061
Fourth direct claim:
That your app can't directly take advantage of features like Live Activities and widgets
"Directly" is doing the heavy lifting here. But, as @tarikpnrc has shown more than once, it is not difficult.
That your app can't directly take advantage of features like Live Activities and widgets
"Directly" is doing the heavy lifting here. But, as @tarikpnrc has shown more than once, it is not difficult.
https://x.com/tarikpnrc/status/1918328242194243691
@tarikpnrc Tarik even just dropped a PencilKit Expo Module:
https://x.com/tarikpnrc/status/1931636827057684609
I get that Apple doesn't want it to be easier for app developers to develop for both iOS and Android.
But it's getting old.
Apple has made a ton of money off of React Native apps and it's enabled countless businesses. It's time that they give it the respect it deserves.
But it's getting old.
Apple has made a ton of money off of React Native apps and it's enabled countless businesses. It's time that they give it the respect it deserves.
Apologies, it's the Platforms State of the Union, not the WWDC keynote. Link here:
• • •
Missing some Tweet in this thread? You can try to
force a refresh
