Despite everything you saw on Twitter about this article during the week, this isn't about switching from a cross-platform codebase to a native one. It's the story of an app rewrite from native to native. It goes against conventional wisdom to do this, but it sounds like this one has been a success.
The most interesting part of the article for me was the section titled "Use the OS":
While UI frameworks can be powerful and increase developer productivity, they require constant upkeep and maintenance to keep up with the ever-changing mobile OS landscape. Rather than reinventing the wheel, we used the UI framework available on the device’s native OS to support a wider variety of application feature needs.
I regularly hear stories from developers at large companies where they’ve made their own abstractions on top of the UI frameworks. It's so tempting, especially if Xcode can't handle your scale, so why not? Unfortunately, those stories are rarely happy ones. 🚑
Or... maybe this is the right take on it? 🍻
- Old situation: There's a rule saying push notifications should not be used for advertising, promotions, or direct marketing purposes. Everyone ignored the rule, including Apple.
- New Situation: There's a new rule saying that advertising by push is OK as long as people can opt-out of that advertising.
The biggest issue by far is the wording:
unless customers have explicitly opted in to receive them via consent language displayed in your app’s UI, and you provide a method in your app for a user to opt out from receiving such messages.
That's so ambiguous it's almost painful to read. Do apps need to separate marketing pushes from other pushes? Will they police the inclusion of a marketing opt-out any more effectively than they did with the original rule? The proof in this pudding will start to be revealed by how Apple implement it for their own apps like Apple Music, News+, TV+, etc...