Pull-to-Refresh Implementation Without Spinner Freeze

User pulls down, spinner spins forever. The cause — onRefresh doesn't handle errors. In 90% of cases setRefreshing(false) is called only in then(), not in finally(). After a failed request, the spinner freezes indefinitely. This spinner freeze is a common issue in mobile apps regardless of platform. Our team has implemented Pull-to-Refresh in 50+ projects on iOS, Android, Flutter, and React Native — not a single frozen indicator. A standard implementation on one platform takes 4–8 hours. Let's break down how to avoid this and other problems: double refresh, gesture conflict, and custom animation needs.

Root Cause: Why the Spinner Freezes?

When a request fails, the exception is caught in catch, but setRefreshing(false) is never called. The spinner stays active. The only reliable way is to place the call in finally:

const onRefresh = useCallback(async () => {
  setRefreshing(true);
  try {
    await fetchData();
  } catch (e) {
    showError(e.message);
  } finally {
    setRefreshing(false);
  }
}, []);

This guarantees the indicator hides regardless of the outcome. According to Apple Human Interface Guidelines, Pull-to-Refresh should update content instantly — our approach fully aligns with this recommendation.

How to Avoid Double Refresh?

If the user pulls twice before the first request completes — two parallel requests fire. Solution: an isRefreshing flag. Set true at the start of onRefresh and reset in finally. Check this flag before calling the fetch. Proper state management of isRefreshing prevents double refresh.

Pull-to-Refresh Gesture Conflict with BottomSheet

If Pull-to-Refresh is inside a BottomSheet — the gesture may be intercepted by the parent. On iOS verify that UIRefreshControl is attached to the inner UIScrollView. On Android Compose use nestedScroll connection. In React Native with @gorhom/bottom-sheet enable enableOverDrag={false}. Gesture conflict resolution takes 1–2 hours.

Platform Comparison

SwiftUI .refreshable reduces code by 50% compared to UIKit. On Compose PullToRefreshBox (Material 3) is replacing the deprecated SwipeRefresh from Accompanist. Basic integration of UIRefreshControl or SwipeRefreshLayout takes 4–8 hours.

Custom Pull-to-Refresh Animation

If the brand requires a unique indicator — e.g., a rotating logo. Flutter's RefreshIndicator supports indicatorBuilder. iOS allows replacing the standard UIRefreshControl with a custom UIView using Core Animation. But note: custom animation increases development time to up to 2 days and introduces higher risk of bugs.

How to Implement Pull-to-Refresh in 5 Steps

1. Choose the platform component (table above).
2. Add isRefreshing state in ViewModel or hook.
3. In onRefresh, call async data loading.
4. Handle errors and always hide the indicator in finally.
5. Test on a real device with poor network.

Additionally: prevent double refresh with a flag, resolve gesture conflicts via canChildScrollUp() or enableOverDrag={false}.

Performance Comparison: Standard vs Custom Implementation

What's Included in the Work

• Audit of current Pull-to-Refresh implementation.
• Development or refinement of component for iOS, Android, Flutter, or React Native.
• Integration with existing API and error handling.
• Testing on real devices under various network conditions.
• Documentation and team training.
• 30-day post-launch support.

Order a turnkey Pull-to-Refresh implementation — get a consultation from an engineer with 50+ projects experience. We'll evaluate your project in 1 day. Contact us to start.

Testing and Acceptance Criteria

A correct Pull-to-Refresh implementation is verified with three scenarios: successful refresh, network error, and simultaneous requests from fast swipes. For iOS we automate tests via XCUITest — simulate a swipe down and verify UIRefreshControl disappears within 0.5 seconds after server response. On Android Compose we use ComposeTestRule.performTouchInput { swipeDown() }. Writing test coverage for Pull-to-Refresh takes additional time depending on platform and logic complexity.

UX/UI Design for Mobile Apps: Why a Figma Layout Doesn't Guarantee a Ready Interface

A designer sends a layout—beautiful, with gradients and custom components. The developer opens it and realizes: the button is 36pt, the tap target is 20pt. On an iPhone SE, it's physically impossible to press with a thumb. The bottom sheet covers content when the keyboard appears. Navigation is built against the native iOS model. Apple will reject the app, or users will leave within a week—depending on how lucky you get with the review.

We have been designing mobile UX/UI for over 5 years and have seen hundreds of such situations. During this time, we have designed and helped launch 30+ mobile apps—from fintech products to social networks. You don't need to guess whether the design will pass App Review or Google Play—we embed platform requirements from the first screen. We'll assess your project in one day, contact us.

Mobile UX/UI is not an adaptation of web design. It is a separate discipline with specific platform constraints: safe area, touch gestures, UIViewController lifecycle, Activity state management.

Why Can't You Ignore Human Interface Guidelines and Material Design 3?

Apple HIG and Google Material Design 3 are not aesthetic recommendations. They are documented user expectations formed by years of using system applications. Expectations confirmed by user experience research on mobile platforms (User experience design).

HIG defines: minimum tap target 44×44 pt, safe area insets for notch and Dynamic Island, standard gestures (swipe back on iOS, back gesture on Android 10+). Ignoring safe area is a common mistake. safeAreaLayoutGuide in UIKit and safeAreaPadding in SwiftUI exist precisely for this. A designer who doesn't set safe area margins in Figma guarantees a bug during development.

Material Design 3 introduced Dynamic Color—the color scheme is generated from the user's wallpaper via MaterialTheme.colorScheme in Jetpack Compose. An app that ignores dynamic colors on Android 12+ looks out of place. This is not critical for niche products but is noticeable in mass-market apps.

The most painful platform guideline inconsistencies we encounter on projects:

• Custom navigation on top of system navigation. iOS users expect swipe back from any point on the left edge of the screen. A custom NavigationController without interactive gesture breaks this. Android users expect the system back button—a custom back button in the left corner does not fully replace it.
• Modal windows instead of navigation push. Bottom sheets are appropriate for actions, not for navigating content.
• Missing haptic feedback. UIImpactFeedbackGenerator on iOS is not decoration but part of the interface response. Buttons, swipes, and confirmation actions without tactile feedback feel broken.

Table: Comparison of iOS and Android UX/UI Requirements

How to Get the Most Out of Figma?

The Figma Variables API has changed the workflow. Design tokens—colors, typography, radii, spacing—are stored as variables and exported directly to code via figma-tokens or style-dictionary. This eliminates manual value transfer and desynchronization between design and implementation. Practice shows: Figma Variables speeds up asset handoff to development by 2–3 times compared to static frames, and using design tokens reduces code transfer errors by 60%.

Auto Layout with wrap and spacing between elements allows building components that behave like flex containers. A developer opens a component and sees not a static artifact but a description of behavior at different content sizes.

Component Properties—variants, boolean toggles, instance swaps—enable building a full design system right in Figma. A button with 4 states (default, hover, pressed, disabled), 3 sizes, and 2 icon variants is one component, not 24 frames.

Figma Prototype with Variables allows creating an interactive prototype with real state: showing how the screen changes with different variable values. This is no longer just a "clickable layout" but a full UX testing tool.

How to Benefit from Prototyping and UX Testing Before Development?

The most expensive mistake in a mobile product is to develop a feature, release it, and discover that users don't understand how it works. A Figma prototype at the testing stage costs zero development hours. Redoing a finished screen costs days. Testing a prototype before development begins reduces the number of fixes by 80%.

For usability testing, we use Maze (task testing on a prototype—the user goes through a scenario, we get heatmaps and mis-click rates) or direct sessions via UserTesting. Key metrics are task completion rate and time on task, not "like/dislike."

A/B testing on mobile is harder than on web: the App Store doesn't allow UI changes without an app update. Therefore, it's important to test hypotheses on a prototype before release, not through production experiments. According to research, fixing a bug found on a prototype costs 10 times less than after production release. And average task completion time increases by 40% after proper UX optimization during prototyping.

Why Are Animations Critical for Interface Perception?

Animations in mobile apps are feedback. An element doesn't appear instantly—it transitions to the desired state over 200–350 ms. This gives the brain context to understand what happened.

• iOS: withAnimation in SwiftUI, UIViewPropertyAnimator in UIKit for interactive animations with interruption capabilities. Spring animations with dampingRatio are the basis of most Apple system transitions.
• Android: AnimatedVisibility, animateContentSize, Crossfade in Compose. MotionLayout for complex scenes with multiple transformations.
• Flutter: AnimationController + Tween, Hero animations between screens, Lottie for After Effects exports. Lottie is especially effective for onboarding illustrations and empty states.

The key constraint is 16 ms per frame (60 fps) or 8 ms (120 fps on ProMotion devices). Animations must run on the GPU via CALayer/RenderThread, not on the CPU via layoutSubviews. Profiling via Core Animation instrument in Xcode is a mandatory step before releasing animated screens.

Why Is Accessibility Not an Optional Feature?

VoiceOver on iOS and TalkBack on Android are used by up to 15% of users—this statistic is confirmed by accessibility research described in Accessibility (Wikipedia). In absolute numbers for a large app, this is thousands of people. Additionally, App Store rejections due to accessibility occur, though rarely.

Minimum checklist:

• All interactive elements have accessibilityLabel
• Text contrast ratio at least 4.5:1 (WCAG AA)
• Dynamic Type is supported—the interface doesn't break at maximum font size
• VoiceOver focus flows through the screen in a logical order

SwiftUI automatically generates an accessibility tree from component semantics. UIKit requires manual setup of accessibilityTraits, accessibilityHint, and grouping via shouldGroupAccessibilityChildren.

What Does the Work Include?

The UX/UI design deliverables include:

What Is the Process and Timeline?

Design goes through stages: research and competitive analysis → user flows and wireframes → design system → UI layouts → prototype → testing → handoff to development.

Timeline estimates:

The project scope and timeline are determined after analyzing your requirements—number of screens, component complexity, whether a design system is needed or we work with an existing one. Get a consultation for your project—contact us for a preliminary assessment. Order a complete mobile app design—we'll assess your project in one day and propose the optimal work scope.