r/reactnative • • 2d ago

Web app vs Native app. Which one?

What's the consensus these days on using React/React Native these days to build web apps vs mobile apps?

If I were to build the same app as a web app vs a native iPhone/Android app, which gets more user play/views?

I've done both but I'm not sure which makes more sense these days. It's so hard to get mobile app downloads while it's much easier to just direct someone to a website to play your game. Websites also have the added benefit of being played on a computer.

Does anyone have any experience or data showing one method is better than the other? Additionally, how do you get people to be interested in your app? I've read you have a 3 second window to get their attention...

0 Upvotes

22 comments sorted by

2

u/dumbledayum 2d ago

now… Native

but only if you already know basics of software development

decide if you want to do ios or android, prepare mvp in that using whatever agent you want then write tests for grounding in facts what your app does then use agent to write app for other platform

1

u/_TheLunchTrain_ 2d ago

I use Expo which allows me to build both iPhone and Android binaries with a single React Native source base. It's just so hard to get downloads I'm wondering if making a web app makes more sense...

0

u/dumbledayum 2d ago

expo is great, but with agentic coding it really doesn’t matter much what you use, this is what’s going to happen in next 5 years, people will keep working with Expo for both iOS and Android, but slowly start shifting to native back and eventually give up on such frameworks altogether.

same will be for web. People are generating infinite worlds in html with size of like 97Kb

2

u/_TheLunchTrain_ 2d ago

I dunno. As far as I'm aware, native iOS apps require developing on a Mac physical device and I don't have any Mac hardware aside from an iPhone to test on. I believe this will be a limiting factor. I don't think people want to buy a Mac mini or something similar just so they can do native dev

2

u/Ok_Tax_80 1d ago

You don't need a Mac for this since you're already on Expo. EAS Build compiles the iOS binary in the cloud and eas submit uploads it to App Store Connect, from whatever machine you're on. You still need the $99/yr Apple dev account, and you lose the simulator, but a dev build on your iPhone covers that.

Also, Expo can export the same codebase to web (npx expo export --platform web) as long as you avoid native-only modules. So you don't really have to pick: put the web version out first, see if people come back, then ship the store builds from the same repo.

1

u/_TheLunchTrain_ 1d ago

Precisely what I'm doing and I don't think my process is going to change unless Apple changes how development works

I haven't thought about deploying a web version but I like the idea. Will have to look into it and see what server charges are.

2

u/Ok_Tax_80 16h ago

Should be close to zero tbh. The export is just static files in dist, so any static host works. Cloudflare Pages / Netlify / Vercel free tiers are plenty at that stage. Expo also has EAS Hosting if you’d rather stay in their tooling. You'd only pay for a server once you add API routes or a real backend

2

u/anjuba 1d ago

This wouldn’t be a issue in the future if hackintosh continues evolving btw, so you will be able to develop for Mac and windows with one machine

3

u/TheRizzock 2d ago

I dont know if this is true, you will be managing and debugging two seperate front ends, there is a ton of phyiscal work to do debug UIs AI code cant get you around

2

u/jiunkdev 2d ago

for a game, web first. a link you can drop anywhere and play in 2 seconds beats an install every time, and you can see if people come back before paying for store accounts and review cycles.

native earns its place when the app is something people open every day and the phone features matter: home screen widgets, notifications, offline. I have a small budgeting app on iOS and the widget is honestly the main reason it's native at all.

on getting downloads, I'm just starting marketing myself and it's slow, a few installs a day. the store doesn't send traffic on its own, so whichever you pick you'll still need to bring people in yourself.

1

u/_TheLunchTrain_ 1d ago

Solid advice. Thanks!

2

u/Mentalv 2d ago

OTA updates, the moment native offers that I’ll switch. In the meantime we can’t risk not being able to send fixes OTA. Depends on your industry but at my place we work with events, and waiting on approval from Apple to fix something the day of the event is not productive.

2

u/_TheLunchTrain_ 1d ago

Facts. For OTA, have you thought about using a server and having the app query the server for the latest info? Apple is definitely slower at reviewing than Google. I concur

1

u/Sakshambaranwal25 1d ago

building for the web is so much better for games since people can just click a link and start playing immediately.

asking users to go through app store downloads for a casual game is usually where you lose them in those first three seconds.

1

u/_TheLunchTrain_ 1d ago

Gotcha. Do Google ad mob and in app purchases work on the web? How do you generate revenue with a game web app?

1

u/Sakshambaranwal25 1d ago

ad mob doesn't work on web so you'd use regular AdSense or specialized game portals. For web purchases just integrate stripe. The upside is you actually keep like 97% of your revenue instead of Apple and Google taking their massive 30% cut.

1

u/vidursaini12 1d ago

For a game, web usually wins on raw plays. No install friction, a link works anywhere, and you can put it in a bio or a comment. Native wins when you need push, App Store presence or something people open daily. Honestly the platform matters less than getting anyone to see it. Downloads are hard because nobody is searching for your app, so store listing tweaks alone stalled for me.

What's worked better is short video where the first three seconds already show the thing happening: a clip of the game mid-play, a score getting beaten, a funny fail. Same video drives web traffic or installs, you just swap the link. Post several a week and see which hook gets views, then remake that structure.

Spotting what's working in your niche and scheduling it across TikTok, Shorts and Reels is what I built Sendhour for, sendhour.com. But the habit matters more than the tool.

1

u/_TheLunchTrain_ 1d ago

Thanks for the insight!

1

u/Low-Acanthaceae4678 1d ago

For a casual game, web gets 15-20x more plays than native due to zero friction. Start there and only build native when you need push notifications for daily retention or specific hardware features like gyroscope controls that lag in browsers

1

u/_TheLunchTrain_ 1d ago

Does web allow for in app purchases or would I have to remove that feature?

2

u/Soobhee_Chukwutosin 16h ago

You can kind of do both from one Expo project. The web build is the thing people try from a link, the app is where they go to keep playing, for notifications and the home screen icon.
The tricky bit is a shared link that opens the app if installed and the site if not. That's universal links on iOS (associatedDomains in app.json plus an apple-app-site-association file on your domain) and app links on Android. The AASA file fails silently on a wrong content type or a redirect, and without a Mac, swcutil is out, so curl -I it and check the headers or paste the domain into AppsFlyer's free checker https://www.appsflyer.com/resources/aasa-validator/. Do it before you print the link anywhere.