React Native短列表用ScrollView是否合理？FlatList与ScrollView选型咨询

Great question—this is a super common confusion for React Native developers, especially when you start learning about FlatList's performance benefits for long lists. Let's break this down step by step.

Is ScrollView Useless Now? #

Absolutely not. ScrollView still has plenty of valid use cases where it's the better (or only) choice:

• When you need all child components mounted at once: Think about a form with multiple input fields, a static card layout with unique content per card, or any scenario where you need instant access to every element without worrying about them being unmounted as you scroll. ScrollView keeps everything in the view tree, which is perfect for interactive elements that need to stay alive.
• Simple scroll containers: If you just need to wrap a few components that don't follow a repeating pattern, ScrollView's API is way simpler. No need to mess with data or renderItem props—just drop your components inside and go.
• Nested scrolling scenarios: Sometimes you need a scrollable container inside another one (like a horizontal scroll of cards within a vertical page). ScrollView handles these cases more intuitively when you don't need item reuse, avoiding the extra complexity of FlatList's virtualization logic.

Why Hasn't ScrollView Been Deprecated? #

There are three big reasons it's still around:

• It's the foundation for other list components: FlatList and SectionList are actually built on top of ScrollView! They add virtualization and item reuse logic, but the core scrolling functionality comes from ScrollView. Deprecating it would break all these higher-level components.
• It's lighter for non-virtualized use cases: For scenarios where you don't need virtualization, using FlatList adds unnecessary overhead. ScrollView is leaner and avoids the extra code needed to manage item mounting/unmounting.
• Backward compatibility: React Native has a huge ecosystem of existing apps that rely heavily on ScrollView. Deprecating it would force massive refactors for countless developers, which goes against the team's focus on maintaining backward compatibility.

Short Lists (≤25 Items): Which Should You Choose? #

It depends on your specific needs:

Go with ScrollView if: #

• Your list items are static or unique (no repeating data pattern—each item is a custom component with its own logic).
• You need all items to stay mounted (e.g., items have real-time inputs, timers, or state that can't be lost when scrolling).
• You want minimal boilerplate: Skip the data/renderItem setup and just drop your components directly into the scroll container.

Go with FlatList if: #

• Your list items are generated from a uniform dataset (same structure, different data—like a list of user profiles). Using data + renderItem keeps your code cleaner and more maintainable.
• You might scale the list later: Even if you only have 25 items now, if there's a chance the list could grow to 100+ in the future, using FlatList now saves you from refactoring later.
• You need built-in features: FlatList comes with out-of-the-box support for pull-to-refresh (refreshControl), load-more-on-scroll (onEndReached), and item separators (ItemSeparatorComponent). Implementing these with ScrollView would require writing custom code.

内容的提问来源于stack exchange，提问作者Amir Meyari