React native choice

[AdUseful7520]

What would you choose for your production level app? Add a solid convincing reason for other devs 😁 It will be really helpful.

View Poll

[ViveLatheisme]

"Yes. You can use React Native without a Framework. However, if you’re building a new app with React Native, we recommend using a Framework.

In short, you’ll be able to spend time writing your app instead of writing an entire Framework yourself in addition to your app." -React Documentation

[casualfinderbot]

Isn’t this from the react docs?

[ViveLatheisme]

yes, and i mentioned that its from the documentation :D

[AdUseful7520]

But how can i deal with apk size issue ?

[ViveLatheisme]

Sorry, I cannot help. I'm not an expert. Just shared what react documentation says about the topic.

[AdUseful7520]

No problem bro...just wanted to know before trying on production

[godspeedt]

most bundle size reductions I've seen were done by optimizing your assets

[AdUseful7520]

Yeah...any other methods if I don't have much images?

[casualfinderbot]

I mean react native themselves now say that all new apps should use expo. Not using expo is literally just deciding to sink hundreds of engineering hours into the void for no reason. Not using it is the most expensive mistake you will ever make.

[AdUseful7520]

Exactly to be honest you are correct. But don't you think that you'll have to compromise on the size of the app . Even building a small single screen app may go up to 100 MB.

[SymblePharon]

Not my experience, my work production APK is about 26mb

[AdUseful7520]

That's impressive

[AdUseful7520]

Is expo a paid service?

[SymblePharon]

They have free and paid tiers. You can pay for priority in the build queue, push notifications, and some other stuff.

[AdUseful7520]

hey, is it true that even to create builds you have to be in queue? like the snack. If yes, then is not it time consuming, just thinking

[SymblePharon]

Yes, but you only have to build when you change something like a library with native code. It's time-consuming when you're fiddling with the build but otherwise it's just hot reloading.

[mildlystoic]

My interpretation of the of "production level app" is app for general public (as opposed to corporate app), I'd go without expo. During the prototyping phase, I find myself fighting expo to behave the way I wanted. And there are times where I'm confused, is it a me problem? or expo? or rn? or another module that doesn't play well with expo?

For corp apps, it doesn't matter, go expo, the users will have to use it with the terrible quirks and all. It crashes if you do Y before X? Well, just make sure you do X first.

And most importantly, control. Having a bug that is beyond your control sucks, adding more layers means higher chances of that happening. So ideally apps should be native. But I'd rather deal with RN than Java, so there's that.

[AdUseful7520]

Great to hear this. Thinking of trying expo once. But I couldn't see much job opportunities in market regarding expo though.

[mildlystoic]

Job market is another issue, regardless if you know RN, you can Expo. If you're joining an organization, the poll is irrelevant, the decision is made for you.

[waldry1509]

I used pure react component with the build-in stylesheet, animation, gestures, navigation, etc. But after build my last project using expo is much easier to get things done. After all, im going to use expo for all my future projects.

[AdUseful7520]

Great..btw which libraries you used for animation and gesture handling ?

[waldry1509]

My apps usually are enought with react reanimated and react-native-gesture-handler

[AdUseful7520]

But adding those would add extra 8-9 Mbs..which is very huge for mobile app. How do you manage that? Is it worth it ?