4 ms·

Especially those who have positive experience, could you share your experience with 3rd party libraries particularly in these particular areas: * Layout

Especially those who have positive experience, could you share your experience with 3rd party libraries particularly in these particular areas: * Layout * Infinite scrolling * REST client * Image handling (loading, displaying, caching) for popular formats * Push notification (Apple's and Google's) * Built-in (not server-side) SQL for storage * Animation (like transitions, fading) * [Added] In-app purchases The reason I ask is, from my experience with non-native platforms, they look appealing and "production ready" ("Look how quick and concise you can make default UI using our platform!"), but once you go beyond default UI, things get ugly. These days, those things I listed are arguably pretty standard for modern apps.

frostik 9y ago
Layout: It's the main reason to go all in with RN. You're much faster building these with RN then using native stuff. Infinite Scrolling: ListViews and RN are a thing. There's a new List Type since a few Versions - if you're following the book regarding DataStrucure everything should work. REST Client: RN provides basic API so nearly everything which works in Browser works in RN too. I use Redux Sagas and fetch. Working great so far. Image Handling: It's built on top of fresco and works great so far. Push: Can't say mush about it, because i don't use it but should work ok. In-App: There's a great Plugin. Animation: Native Animations are around for some time. Should work ok, but depends what you're planning to do. Basically it's extremely easy to go native if necessary. But at that point you need to implement it on every platform. Even though for usual use cases it shouldn't be necessary. You just need to keep Track of your renderings and make sure you use PureComponents at the right point, so there are no unnecessary rerenders congesting the bridge and slowing everything down. But if you do it right you will achieve performance and an feature level that is on par with every native development in less time. And with 95% Code Share.
- antoniuschan99 9y ago
  Push works great!
dean177 9y ago
From your list I have had no experience with in app purchases or client side sql. I had a fair amount of trouble with push notifications on android (callbacks not being called etc), but those issues were eventually resolved (and had no issues with iOS). Everything else on your list I found much simpler &a quicker than working with the native platforms

frostik 9y ago

Layout: It's the main reason to go all in with RN. You're much faster building these with RN then using native stuff. Infinite Scrolling: ListViews and RN are a thing. There's a new List Type since a few Versions - if you're following the book regarding DataStrucure everything should work. REST Client: RN provides basic API so nearly everything which works in Browser works in RN too. I use Redux Sagas and fetch. Working great so far. Image Handling: It's built on top of fresco and works great so far. Push: Can't say mush about it, because i don't use it but should work ok. In-App: There's a great Plugin. Animation: Native Animations are around for some time. Should work ok, but depends what you're planning to do. Basically it's extremely easy to go native if necessary. But at that point you need to implement it on every platform. Even though for usual use cases it shouldn't be necessary. You just need to keep Track of your renderings and make sure you use PureComponents at the right point, so there are no unnecessary rerenders congesting the bridge and slowing everything down. But if you do it right you will achieve performance and an feature level that is on par with every native development in less time. And with 95% Code Share.

antoniuschan99 9y ago
Push works great!

dean177 9y ago

From your list I have had no experience with in app purchases or client side sql. I had a fair amount of trouble with push notifications on android (callbacks not being called etc), but those issues were eventually resolved (and had no issues with iOS). Everything else on your list I found much simpler &a quicker than working with the native platforms