Tactile Reward Popup: Animation, Confetti, and Points Counter

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
Tactile Reward Popup: Animation, Confetti, and Points Counter
Simple
~1 day
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
    745
  • image_mobile-applications_rhl_428_0.webp
    Development of a mobile application for RHL
    1161
  • 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
    563

Tactile Reward Popup: Animation, Confetti, and Points Counter

A user completes a quest, receives 500 coins—and the app shows a boring AlertDialog with "Congratulations, +500". The moment is lost. The reward should feel physical: confetti particles, an accelerating counter, haptic feedback at the peak. Without this, gamification becomes a formality.

We design reward popups that turn a technical event into an emotion. Our team has delivered over 50 gamification projects, from startups to enterprise (5+ years in gamification). Our certified engineers use native animations (SwiftUI/UIKit, Jetpack Compose), Core Haptics, and CAEmitterLayer. The popup completes in 1.2–2 seconds—any longer, and users start tapping "close". In one fintech project, replacing a standard Alert with a reward popup featuring an animated counter and haptic feedback increased repeat action conversion by 27% in a week. Our basic package starts at $500, and the advanced package with full analytics is $1,200.

Why Standard AlertDialog Falls Short

An Alert is an information window. A reward popup is a micro-script with a climax, release, and feedback. Alert doesn't support staggered animation, particles, or haptics. It lacks a counter that builds a sense of accumulation. Yet these details boost repeat action conversion by 20–30% (A/B test data from our projects). An animated counter is 3x more effective at conveying reward magnitude than static text.

Reward Popup Anatomy

Typical layer structure:

  • Backdrop: dimmed background with blur (UIBlurEffect / RenderEffect.createBlurEffect)
  • Card: appears from below or scales up with spring animation (we use UISpringTimingParameters with damping ratio 0.6)
  • Reward icon: scale + rotation with bounce
  • Particle burst: confetti, stars, coins—CAEmitterLayer or Lottie
  • Text reveal: animated points counter from previous value to new one
  • CTA button: appears with delay after main animation

Key elements: Backdrop with blur, Particle burst with confetti, and the animated counter. Entire pipeline takes 1.2–2 seconds. Longer—user taps "close".

Implementing an Animated Counter on iOS

The most detailed element is the animated counter. +500 coins should be counted, not just appear.

class CountingLabel: UILabel {
    func countFrom(_ start: Int, to end: Int, duration: TimeInterval) {
        let displayLink = CADisplayLink(target: self, selector: #selector(update))
        self.start = start; self.end = end
        self.startTime = CACurrentMediaTime()
        self.duration = duration
        displayLink.add(to: .main, forMode: .common)
    }

    @objc func update(link: CADisplayLink) {
        let elapsed = CACurrentMediaTime() - startTime
        let progress = min(elapsed / duration, 1.0)
        let eased = 1 - pow(1 - progress, 3)  // ease-out cubic
        currentValue = Int(Double(start) + Double(end - start) * eased)
        text = "+\(currentValue)"
        if progress >= 1 { link.invalidate() }
    }
}

In Flutter, use TweenAnimationBuilder<int> with curve: Curves.easeOut and Text('${value}') inside.

Particle Burst: CAEmitterLayer vs Lottie

CAEmitterLayer is 2–3x more performant than Lottie for particle rendering but requires more code. Comparison:

Parameter CAEmitterLayer Lottie
Performance High (native) Medium (JSON render)
Size ~50 KB 200+ KB
Flexibility Full particle control Limited by animation
Cross-platform iOS only iOS, Android, Web

For a single burst of confetti on popup appearance, use CAEmitterLayer with birthRate = 300 for the first 0.1 seconds, then birthRate = 0. This gives an "explosion" effect without endless stream.

emitterLayer.birthRate = 1  // enabled
DispatchQueue.main.asyncAfter(deadline: .now() + 0.15) {
    emitterLayer.birthRate = 0  // disabled—particles fly until lifetime ends
}

Lottie confetti is simpler: a ready .json file plays once over the popup. See CAEmitterLayer documentation for more details. For tactile effects, Core Haptics documentation provides guidance.

Staggered Animation: Why It Matters

Everything should not appear simultaneously—stagger creates a sense of "unfolding" the reward. Each element has its timing:

Time Event
0ms Backdrop appears, blur intensifies
150ms Card flies in from bottom (spring)
300ms Particle burst
350ms Icon scale up with bounce
500ms Haptic feedback (success)
600ms Text reward fades in
800ms Counter starts animating
1200ms CTA button appears

On iOS, use DispatchQueue.main.asyncAfter for each step or UIViewPropertyAnimator with addAnimations(afterDelay:). In Flutter, use AnimationController with interval curves for each element.

Step-by-Step Confetti with CAEmitterLayer

  1. Create a CAEmitterLayer and set its frame equal to the popup's bounds.
  2. Configure emitterCells: set content (e.g., a colored rectangle), birthRate, lifetime, velocity, scale, spin.
  3. Set birthRate = 1 for 0.15 seconds, then zero (as in code above).
  4. Add the layer as a sublayer to the popup's view.
  5. Verify that particles render before dismiss (lifetime ~0.8 s).

Contact us for a free assessment of your project—we'll analyze your reward scenario. Order a turnkey reward popup development (starting at $500) and get a gamification consultation.

What's Included in Our Work

  • Analysis of user scenario and popup design
  • Implementation in Swift (iOS) or Kotlin (Android) using native animations
  • Haptic feedback integration (Core Haptics / Vibrator)
  • Analytics integration (Firebase / AppsFlyer)
  • Documentation and source code delivery
  • 30-day post-delivery support

We guarantee correct operation on all devices—tested on 20+ models. Timeline: from 1 day for a standard reward popup with animations and haptics on one platform.

Impressive stats: 5+ years in gamification, 50+ projects delivered, certified engineers. Save up to $2,000 compared to rebuilding in-house.

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.