react-native-keyboard-aware-scroll-view VS react-virtualized

Hey man… I am interested in integrating your component into my app. I’m currently using the flat list from https://github.com/APSL/react-native-keyboard-aware-scroll-view to scroll to specific components based on focused text inputs. How could I combine your component with that and get both functionalities together? Thanks!

Also, it will bug out any time you're using react navigation. (Yes this bug still exists, no you cannot avoid it in all situations).

Hi, I already created an issue on github But it's urgent. Do you guys know how to avoid overlap header & status bar? I tried to change android:windowSoftInputMode but it didn't work

There are packages like react-native-keyboard-aware-scrollview (just in case you are not "aware") that automatically scrolls to the focused TextInput component. But, in your use case, that is not enough. You probably want to push an element on top of the soft-keyboard or change style when it is visible or hidden.

Try this https://github.com/APSL/react-native-keyboard-aware-scroll-view

You may increase the rendering efficiency of tabular and huge list data by using the React Virtualized module. React apps perform better overall when the quantity of requests and DOM elements is limited. React Virtualized is comparable to many other tools; however, what sets it apart from the competition is the sheer volume of features and excellent upkeep.

17.react-virtualized

If you have been using React for awhile, you may have heard of the infamous virtualisation library react-window or it's predecessor react-virtualized

React Virtualized is a React library that helps you work with large lists and tabular data efficiently in React. It has more than 25K stars on GitHub and more than 2.5 million weekly downloads on NPM as of August 2023.

Use virtualization (e.g. react-virtualized) to prevent off-screen components from actually rendering.

Virtualization can be achieved using third-party libraries like react-window or react-virtualized. These libraries provide a way to render only the visible data and load more data as needed, resulting in faster application performance.

You can implement the same pattern on the web when dealing with large amount of data. There are some libraries for React that trivialize this, like https://github.com/bvaughn/react-virtualized

Oh, right. I totally forgot to mention that– but the idea of "less rendering" in this case seems less like a Suspense concern and more like a windowing concern. I've written a few libraries for that stuff (react-window and react-virtualized) although there are others that may fit your needs better. Their main focus is limiting what you're rendering to more or less only what's on the screen at any given point. Combine that with memoized filtering and I would imagine you're set.

I've used the InfiniteLoader from react-virtualized in combination with useInfiniteQuery from @tanstack/react-query and it was relatively painless.

Here’s a react library https://github.com/bvaughn/react-virtualized