meliorence/react-native-snap-carousel

Snapping between items is very jerky

Open

#189 opened on Oct 18, 2017

View on GitHub
 (30 comments) (19 reactions) (0 assignees)JavaScript (10,045 stars) (2,223 forks)batch import
*enhancementhelp wantedreact-native bug

Description

Hi guys,

I've searched around a lot and haven't found any information about this, but even the simplest of tests with the carousel I find are very jerky.

When swiping between items in the carousel, I notice that as soon as I release my finger, the speed of the snap changes. This means when I quickly flick to the next item, it instantly slows the snap speed so it looks like the swipe "hit a wall."

I'm tested this using Expo on an iPhone 7.

I've compared this to the native ScrollView with pagingEnabled or even snapToInterval and that has a much smoother effect.

Is this purely because the "snapping" action can't work out how much force a user swiped with? Or am I completely missing something?

I can probably put together an Expo snack to demonstrate the issue if need be.

Contributor guide

Tech stack
javascriptreactandroidios
Domain
mobilefrontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
React Native basicsUnderstanding of gesture handlersAnimation in React Native
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the carousel's snapping animation logic in the source code (e.g., Carousel.js). Compare the behavior with native ScrollView's pagingEnabled. Review the 30 comments for any proposed fixes or insights. Consider creating an Expo snack to reproduce the issue for precise debugging.