callstack / callstack/react-native-paper
Add support for skeleton loaders
- Dominant language
- TypeScript
- Stars
- 14.5k
- Forks
- 2.2k
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 12
Description
**Is your feature request related to a problem? Please describe.**
This is not related to a problem, just a desirable feature.
**Describe the solution you'd like**
It would be amazing if we could have an opinionated implementation of skeleton loaders [as defined in MD3](https://m3.material.io/styles/motion/transitions/transition-patterns#f7ff608a-087d-4a4e-9e83-f1af69184487).
**Describe alternatives you've considered**
There is a plethora of open source libraries providing this feature, although with debatable APIs and performance.
**Additional context**
As of today, the bar for truly great UX is really high and skeleton loaders are one of the building blocks that contribute to achieve that. Other component libraries provide those out of the box (e.g. [NativeBase](https://docs.nativebase.io/skeleton), [React Native Elements](https://reactnativeelements.com/docs/next/components/skeleton)), IMHO it wouldn't be unreasonable to think that `react-native-paper` users should be able to find those in the component section.
https://github.com/callstack/react-native-paper/assets/8156463/bc415ede-7ee5-4efb-9c4f-746d5013df50
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reviewing the repository's existing component patterns and the linked Material Design 3 skeleton-loader guidance, then compare the referenced NativeBase and React Native Elements implementations. The issue does not define acceptance criteria or what tests should cover.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- frontend, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100