A big part of that case has been Apple's promise that the walled garden of a reviewed app store is to keep the store a safe place. However, I don't believe anyone in app review even opened these apps because literally the only thing the app does is open a web browser to an online casino...

I'm interested by these cropping up for two reasons. First because the "report a problem" link has been removed from app store pages, so now the only way to report an app like this is to install it on your device. Secondly because the Epic v Apple case was in the news as recently as today.

One for a fish-themed slot machine has an app store page listing itself as "Gill Guru" an ai-powered "fishing mentor." Another for an Egyptian-themed slot has an app page that pretends to be a historical reference app. And I'm sure this is an iceberg tip and there are plenty more.

I'm just lucky I was born into it natively

(Silver lining, to all of this is, of course, that it means lots of "___ for React Native" small indie hacking business opportunities.)

The clearest example of this I saw was Storybook. At least they support RN at all, but you notice they have pages of first-party docs about how to integrate with NextJS while their RN docs are just a link to a Github repo. The instructions on how to show their UI is two links to dev.to blogposts.

Indeed, even outside styling, the lack of support you get compared to web dev tooling is the most notable thing. You can tell you're moving from extremely polished CLI tools and docs to ones that were done quicker and with less of an eye to QA and polish that supports folks learning the platform.

Good: Build and styling tools have come a long way in 5 years. Not perfect, but so very much easier to set up a new project now. Bad: the various component/theming packages are still lacking and either have a steep learning curve (Tamagui) or lack the polish & qa that the web tooling spoils me with.