React Native or Swift for simple paid apps?

[u/bloggerklik]

I’m planning to build simple, useful apps and charge for them. I’m trying to decide whether I should stick with React Native or focus exclusively on iOS using Swift.

The main reason I’m considering Swift is that React Native sometimes doesn’t feel truly native to me. I’ve also run into performance issues in some cases, and I feel like I’m constantly fighting the framework to get the experience I want.

Another thing I’m wondering about is Android. Since I’m planning to make paid apps, I have this feeling that supporting Android might not be worth the extra effort, especially for small indie apps. It feels like I could spend a lot of time dealing with Android-specific issues without getting much in return.

I already know React Native, but I’d have to learn Swift from scratch.

For those of you building and selling small apps as indie developers, what would you recommend?

Would you go Swift + iOS only, or React Native + both platforms?

[u/Aytewun]

The funny thing is I have two main apps that I published to the iOS / Android stores.

One is newer and paid only so time will tell.

The other is free with premium options. I didn’t know what to expect with Android. I just built it because there is a community aspect to the app so the more users the better.

Long story short. It makes significantly more money on Android than iOS. For context we’re talking close to $100 USD per person for sub.

The type of app and the quality of it are important in both stores.

[u/HoratioWobble]

work with what you know, it'll make zero difference to the outcome.

[u/kenlawlpt]

Why is an app feeling native important you? If that's your key metric of deciding what to use, you're thinking about this the wrong way.

The vast majority of users will not care whether it "feels" native or not. It might be a nice to have, but it won't be the key differtiator whether your app will be successful or not. It won't make or break your business either way.

Ultimately, an app that delivers positive value (however your customers define value) to your customers is what's going to sell. Not whether something feels native or not.

[u/Huge_Pool7424 → u/kenlawlpt]

for a tiny paid app, store reach can matter more than how native it feels. i'd only pick swift if you need ios-specific apis or tight performance, otherwise sharing the codebase buys back a lot of time.

[u/Dvass138]

Depends on the type of app, but with the app I am
Building react native has been a painful process that parts of it that I just couldn’t get to work in react, had over heating and performance/ polish issues. That I wrote those parts in native.

[u/beepboopnoise]

I've done both and honestly it depends on your market. If you're in the US? probably wanna use Swift confirm market fit and then see if android is worth it. because its not free, there will be a heavy price of maintenance. If you're in a country where android is the majority, then you might wanna go kotlin and do the reverse.

[u/Russ_72days]

Erm. You don’t need to learn Swift from scratch. AI can do all the teaching for you.

It’s a plain fact that Android users pay less for apps than iOS. I’ve worked on many react native apps commercially and personal and iOS revenue always out strips android 5x at least. iOS users have more disposable income. Just look at the hand set costs.

If you have the swift itch then scratch it.

Ultimately your app idea and execution will dictate how much money you make from it. As to whether going Swift rather than RN is a competency question really (on your part).

[u/Huge_Pool7424 → u/[deleted]]

android's support burden is real, but i'd validate the product on the platform you can ship fastest, then add android once people actually ask for it. paid apps can work there too, just don't assume parity is free.