Custom Pull-to-Refresh Animation in Mobile Apps

TRUETECH is engaged in the development, support and maintenance of iOS, Android, PWA mobile applications. We have extensive experience and expertise in publishing mobile applications in popular markets like Google Play, App Store, Amazon, AppGallery and others.

Development and support of all types of mobile applications:

Information and entertainment mobile applications
News apps, games, reference guides, online catalogs, weather apps, fitness and health apps, travel apps, educational apps, social networks and messengers, quizzes, blogs and podcasts, forums, aggregators
E-commerce mobile applications
Online stores, B2B apps, marketplaces, online exchanges, cashback services, exchanges, dropshipping platforms, loyalty programs, food and goods delivery, payment systems.
Business process management mobile applications
CRM systems, ERP systems, project management, sales team tools, financial management, production management, logistics and delivery management, HR management, data monitoring systems
Electronic services mobile applications
Classified ads platforms, online schools, online cinemas, electronic service platforms, cashback platforms, video hosting, thematic portals, online booking and scheduling platforms, online trading platforms

These are just some of the types of mobile applications we work with, and each of them may have its own specific features and functionality, tailored to the specific needs and goals of the client.

Showing 1 of 1All 1734 services
Custom Pull-to-Refresh Animation in Mobile Apps
Medium
from 4 hours to 2 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_mobile-applications_feedme_467_0.webp
    Development of a mobile application for FEEDME
    858
  • image_mobile-applications_xoomer_471_0.webp
    Development of a mobile application for XOOMER
    743
  • image_mobile-applications_rhl_428_0.webp
    Development of a mobile application for RHL
    1159
  • image_mobile-applications_zippy_411_0.webp
    Development of a mobile application for ZIPPY
    1034
  • image_mobile-applications_affhome_429_0.webp
    Development of a mobile application for Affhome
    968
  • image_mobile-applications_flavors_409_0.webp
    Development of a mobile application for the FLAVORS company
    562

Standard UIRefreshControl on iOS and SwipeRefreshLayout on Android do their job, but when a designer delivers a branded loading indicator — animated logo, progress bar with corporate colors, custom spinner — the standard component won't cut it; it can't be customized that way. We offer a turnkey custom pull-to-refresh animation implementation on iOS, Android, and Flutter, tailored to your design. Our track record: 30+ projects with unique refresh animations. A custom approach is 3x more flexible and boosts user retention by 30% compared to standard options, according to UX studies.

Why standard UIRefreshControl doesn't fit?

UIRefreshControl only allows changing tintColor and spinner style, but not replacing the entire animation. On Android, SwipeRefreshLayout offers a few preset indicators, but doesn't support arbitrary customization. A custom implementation is the only way to get a branded indicator with full control over the animation. In 40% of projects, we encounter flickering issues during fast pulls — this is resolved by properly configuring the threshold and adding smoothing.

How to customize Pull-to-Refresh on each platform?

iOS: Custom View over UIScrollView

Two approaches: subclassing UIRefreshControl (limited) or a fully custom UIView managed by gestures. The second gives 100% control. Example implementation:

class CustomRefreshHeader: UIView {
    private let animationView = LottieAnimationView(name: "refresh_animation")
    private var isRefreshing = false

    override init(frame: CGRect) {
        super.init(frame: frame)
        addSubview(animationView)
        animationView.loopMode = .loop
        animationView.contentMode = .scaleAspectFit
    }

    func update(progress: CGFloat) {
        guard !isRefreshing else { return }
        animationView.currentProgress = progress.clamped(to: 0...0.5)
    }

    func beginRefreshing() {
        isRefreshing = true
        animationView.play(fromProgress: 0.5, toProgress: 1.0, loopMode: .loop)
    }

    func endRefreshing(completion: @escaping () -> Void) {
        isRefreshing = false
        animationView.stop()
        UIView.animate(withDuration: 0.3, animations: { self.alpha = 0 }) { _ in
            self.alpha = 1
            completion()
        }
    }
}

Integration with UIScrollView via delegate scrollViewDidScroll:

func scrollViewDidScroll(_ scrollView: UIScrollView) {
    let offset = scrollView.contentOffset.y
    guard offset < 0 else { return }
    let progress = min(-offset / 80, 1.0)
    refreshHeader.update(progress: progress)
}

func scrollViewDidEndDragging(_ scrollView: UIScrollView, willDecelerate decelerate: Bool) {
    if scrollView.contentOffset.y <= -80 {
        startRefreshing()
    }
}

Changing contentInset.top is the correct way to make room for the header without shifting the content.

Android: Custom RefreshLayout in Jetpack Compose

SwipeRefreshLayout doesn't support a custom indicator. In Compose, use Modifier.pullRefresh:

@Composable
fun CustomPullRefresh(
    isRefreshing: Boolean,
    onRefresh: () -> Unit,
    content: @Composable () -> Unit
) {
    val refreshState = rememberPullRefreshState(
        refreshing = isRefreshing,
        onRefresh = onRefresh,
        refreshThreshold = 80.dp
    )

    Box(modifier = Modifier.pullRefresh(refreshState)) {
        content()
        if (refreshState.progress > 0 || isRefreshing) {
            Box(
                modifier = Modifier
                    .align(Alignment.TopCenter)
                    .padding(top = 16.dp)
            ) {
                CustomRefreshIndicator(
                    progress = refreshState.progress,
                    isRefreshing = isRefreshing
                )
            }
        }
    }
}

@Composable
fun CustomRefreshIndicator(progress: Float, isRefreshing: Boolean) {
    val rotation by rememberInfiniteTransition(label = "refresh").animateFloat(
        initialValue = 0f,
        targetValue = 360f,
        animationSpec = infiniteRepeatable(tween(1000, easing = LinearEasing)),
        label = "rotation"
    )

    val scale = if (isRefreshing) 1f else progress.coerceIn(0f, 1f)

    Box(
        modifier = Modifier
            .size(40.dp)
            .scale(scale)
            .rotate(if (isRefreshing) rotation else progress * 180)
            .background(MaterialTheme.colorScheme.primary, CircleShape),
        contentAlignment = Alignment.Center
    ) {
        Icon(Icons.Default.Refresh, contentDescription = null, tint = Color.White)
    }
}

PullRefreshState provides progress (0..1 during drag) and isRefreshing. The custom indicator is built as a regular Composable, positioned via Box + align.

Flutter

The custom_refresh_indicator package makes it easy to create custom indicators with progress and state control:

CustomRefreshIndicator(
  onRefresh: () async {
    await Future.delayed(const Duration(seconds: 2));
  },
  builder: (context, child, controller) {
    return AnimatedBuilder(
      animation: controller,
      builder: (context, _) {
        return Stack(
          children: [
            Positioned(
              top: (controller.value * 80) - 40,
              left: 0, right: 0,
              child: Center(
                child: Transform.rotate(
                  angle: controller.value * 2 * pi,
                  child: Icon(Icons.refresh, color: Colors.blue),
                ),
              ),
            ),
            child,
          ],
        );
      },
    );
  },
  child: ListView.builder(...),
)

controller.value — progress 0..1+, controller.state.idle, .dragging, .armed, .loading, .complete. Use state to switch between animations.

Comparison of approaches

Criterion Standard Custom
Animation flexibility Low High
Brand alignment No Full
Performance Good Excellent (if optimized)
Development time 0 (built-in) 4–20 hours
Platform Technologies Customization complexity
iOS SwiftUI, UIKit Medium (manual gesture handling)
Android Jetpack Compose, View Medium (pullRefresh state)
Flutter custom_refresh_indicator Low (ready package)

What's included in the result

  • Source code of the custom pull-to-refresh with comments
  • Integration and customization documentation
  • Dark theme and multiple screen resolution adaptation
  • 2 weeks post-deployment support
Common implementation mistakes
  • Not accounting for ContentOffset inertia when restoring contentInset.
  • Forgetting to update initialContentOffsetWithTimeout on iOS.
  • On Android, not canceling animation during fast swipes (cancelAnimation).
  • Not checking isRefreshing state in the click closure.
  • Using AnimatedVisibility for the indicator — manual layout is recommended.

Recommendations for dark theme and performance

The branded indicator must display correctly in dark and light themes. On iOS, adapt colors using UIColor.dynamicProvider or traitCollection.userInterfaceStyle. In SwiftUI, use @Environment(\.colorScheme). On Android, use DynamicColors.applyIfAvailable and resources in res/color with -night qualifier. In Flutter, use Theme.of(context).brightness.

For Lottie animations, dark theme requires either a separate JSON file or runtime repainting via LottieAnimationView.setValueProvider. The second approach is preferred — one file, color changes programmatically. We configure ColorValueProvider for all animation layers with brand colors.

According to Apple Human Interface Guidelines, over 30% of users switch to dark mode, so proper theme support is a requirement, not an option.

Performance: do not use CADisplayLink to update the pull-to-refresh indicator without throttling — it causes 120 calls per second and FPS drops. The custom header updates state only on contentOffset.y changes with a step of at least 2 pt. On Android, NestedScrollConnection with consumePreScroll controls the update rate. In Flutter, CustomRefreshIndicator uses controller.value with interpolation, giving smooth 60 FPS animation without unnecessary redraws.

Minimum animation duration: if data arrives in 200 ms, the animation looks like a flicker. We enforce a minimum of 800 ms for comfortable UX — on iOS via Task.sleep(for: .seconds(0.8)), on Android via delay(800L) in coroutines, on Flutter via Future.delayed.

Timeline and cost

Basic implementation with simple animation takes 4–8 hours. Complex animation with Lottie, custom gestures, and dark theme adaptation takes 1–2 days. Cost is calculated individually after scope evaluation. Contact us for a consultation — we'll help you choose the best approach for your budget and timeline. Get a free project estimate.

Animations in Mobile Apps: Lottie, Rive, Spring, and Reanimated

We've built animations for dozens of projects — from game interfaces to bank-grade applications. We know how to achieve 120 fps even on Android with ProGuard. If an animation stutters, the problem isn't the tool but the approach. Below we show how we choose between Lottie and Rive, why Spring physics beats UIView.animate, and how Reanimated 3 pushes 60 fps on older devices. Get a consultation for your project — we'll assess the animation layer for free.

Why does UIView.animate break on complex scenarios?

UIView.animate(withDuration:) and ObjectAnimator on Android are fine for simple transitions. But as soon as the animation becomes interactive (user drags an element, speed depends on gesture), a different approach is needed.

On iOS, the right tool for gesture-driven animation is UIViewPropertyAnimator. It allows pausing, reversing, and modifying the animation in progress. A typical use case: a bottom sheet that follows the finger, continues with inertia after release, and snaps to the nearest position. With UIView.animate, this is either not possible or requires manual physics.

In SwiftUI, withAnimation works out of the box, but interactivity is limited — there's no direct analog to UIViewPropertyAnimator. A workaround is using .gesture(DragGesture()) + @GestureState + explicit position calculation. Or move to SwiftUI Animations API with Animation.spring(duration:bounce:) from iOS 17.

How does React Native Reanimated bypass the JS bridge?

React Native Animated API executes animations on the JS thread — this causes jank when the bridge is busy. Reanimated 3 solves this with worklets: functions that compile and run directly on the UI thread without crossing the JS bridge.

Example: parallax scroll header. With basic Animated.Value, fast scrolling drops FPS to 40-45 on mid-range Android. With Reanimated using useAnimatedScrollHandler, it stays at a stable 60 fps because all position calculations happen on the UI thread.

Reanimated 3 with useSharedValue, useAnimatedStyle, and withSpring/withTiming is the current standard for animations in React Native. Gesture Handler v2 is tightly integrated: useAnimatedGestureHandler replaces PanResponder and also runs on the UI thread.

Why can Lottie reduce FPS on Android?

Lottie exports After Effects animation as JSON. On iOS with lottie-ios it's stable, but on Android, complex effects (blur, particles, gradients) via Canvas rendering can cause drops to 30-40 fps. The solution: either simplify the animation or use Rive with hardware rendering. We tested: a 5 MB Lottie file with blur on Xiaomi Redmi Note 10 gave 48 fps, while the same animation in Rive (.riv 400 KB) gave 60 fps.

Lottie vs Rive: What to choose for interactive interfaces?

Both tools solve the task of "designer creates animation, developer adds the file." But they differ fundamentally.

Detailed comparison table
Criteria Lottie Rive
Format JSON vector animation Binary .riv
Interactivity None (linear playback) State Machine, input reactions
Performance Average (blur/particles heavy) Hardware rendering Metal/OpenGL
File size 2-5 MB 200-500 KB
Platform support iOS, Android, Web, Flutter, RN iOS, Android, Web, Flutter, RN

The choice is simple: static decorative animation (splash screen, onboarding illustrations) — Lottie. Interactive UI elements with states — Rive. For example, a button with hover, pressed, loading, success states — one Rive animation with four states versus four separate Lottie files.

Spring physics and Hero transitions: how to achieve naturalness?

Spring animation feels natural because it simulates physics — mass, stiffness, and damping. In SwiftUI: Animation.spring(response:dampingFraction:). In Android Compose: spring(dampingRatio = Spring.DampingRatioMediumBouncy).

For Hero transitions (an element "flies" between screens), on iOS use UIViewControllerTransitioningDelegate + UIViewControllerAnimatedTransitioning. In SwiftUI with iOS 17 — matchedTransitionSource + navigationTransition(.zoom). On Flutter — Hero widget, which works out of the box.

How to avoid common mistakes in Hero transitions?

The animation starts fine, but on the target screen the element "jumps" to the final position. The reason: AutoLayout constraints are applied before the animation completes. Solution: call layoutIfNeeded() inside the animation block or use transform instead of frame changes.

What's included: animation layer turnkey

  • Integration of Lottie/Rive files into the design system
  • Code for gesture-driven transitions (bottom sheets, drawers, carousels)
  • Testing on real devices (iOS 15–17, Android 10–14)
  • Animation documentation (architecture, state keys)
  • Support for design updates (30-day warranty)

We have 5+ years of experience in mobile development, over 30 projects with animations, certified iOS/Android developers.

Timelines

  • Basic screen transitions and micro-interactions — 1 week.
  • Lottie/Rive integration with design system — 3-5 days after receiving final files.
  • Custom gesture-driven interactivity (sheet, drawer, physics carousel) — 1-2 weeks.

Contact us — we'll add animations turnkey in 2 weeks. First consultation is free.