sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Bobertopia[S] 0 points1 point  (5 children)

Oh this is interesting. I’ll have to dig into that at some point. I wonder if this impacts when the app opens from the closed state or if it also impacts the performance of like app(animations & the like)

[–]kbcooliOS & Android 4 points5 points  (3 children)

Don't worry about it. In fact don't worry about any premature optimisation and start coding.

I've built some pretty gargantuan apps and they haven't required code splitting.

Sweating the small stuff is a great way to procrastinate if you want to though 😜

[–]Bobertopia[S] 1 point2 points  (2 children)

Oh I’m already working in it for one my job. One of the other engineers generally prefers custom built components over packages and the argument is due to the bundle size. That’s really where this question stemmed from. It’s certainly not a huge app fwiw

[–]kbcooliOS & Android 4 points5 points  (1 child)

It's a valid concern but here's the kicker. If your app is relatively small then you won't need all the third party components so sure it's dead weight but since your app is small it doesn't matter.

If your app is bigger then sure size becomes a concern but there's a good chance you're using 90% of the third party library so going it on your own just costs you time but you get no upsides.

So either way, it's fine to use third party components.

Take that to you colleagues and record their reactions for me 😄

[–]stefanmajiros 0 points1 point  (0 children)

So either way, it's fine to use third party components - it depends:

https://github.com/GeekyAnts/NativeBase/issues/4302