Mobile App Development for Coupons and Discounts

We specialize in building loyalty program mobile apps from MVP to scalable solutions. A coupon and discount app seems simple, but real complexity starts with geolocation integration ("discounts near me"), push notifications ("you're in a mall — here's a discount"), partner retail APIs, and a coupon redemption system that prevents fraud. With 5+ years in the market and over 30 projects in this niche, we know every non-trivial detail. One key challenge: protecting against screenshot reuse. Our approach combines tokenization and dynamic QR, minimizing fraud.

Discount App Development: Geolocation Integration

Why geolocation is critical for conversion

"Discounts nearby" can be as simple as an API call with current coordinates or proximity marketing via geofencing. Without geolocation, you lose up to 40% of clicks — users don't want to type an address. Implementation must be seamless and energy-efficient.

Simple variant: user opens app → current coordinates → GET /offers?lat=55.75&lng=37.61&radius=1000. Works only when the app is open.

Geofencing: the app registers geofences around partner store locations. On entry — a push notification with relevant discounts for that store. On iOS — CLCircularRegion, limit of 20 simultaneous regions (see Documentation Apple Core Location). If you have 500 partners — dynamic registration of the nearest 20 as location changes.

Algorithm: on significant location change (startMonitoringSignificantLocationChanges()) — request 20 nearest stores, re-register geofences. On Android — similar using GeofencingClient with a 100-geofence limit.

BLE-beacon proximity (Eddystone, iBeacon): the app detects beacons in-store — push with a personalized offer. CoreBluetooth / Android BluetoothLeScanner. Requires partner to install beacons, complicating B2B sales. But accuracy is meters, not hundreds of meters.

How to set up geofencing in 3 steps

1. Get the list of coordinates for all partner stores.
2. On iOS, register up to 20 CLCircularRegion with a radius of 100–500 meters. On Android, use GeofencingClient with a radius of 50 meters.
3. In the region entry handler (iOS: CLLocationManagerDelegate, Android: GeofencingEvent), send a push notification with a personalized coupon.

Displaying and Filtering Coupons in Discount Apps

Coupon list — RecyclerView (Android) / LazyVStack (SwiftUI). Coupon card: image, store name, discount size, expiration date, distance. Skeleton loading while fetching.

Filters: category, distance, discount percentage, online/offline. Sorting: by distance, discount size, expiration date. All server-side — client only passes filter parameters.

Card flip animation for revealing coupon terms — CATransform3DMakeRotation (UIKit) / .rotation3DEffect (SwiftUI). Not mandatory, but adds liveliness.

How to Protect Coupons from Fraud?

This is the key technical challenge. A coupon cannot be a static QR code — it can be photographed and reused.

One-time token: when the user taps "use" — a request to the server, the server generates a JWT with exp: now + 300sec and used: false. QR code with token is shown for 5 minutes. Cashier scans → server marks used: true. Re-scan gives error "coupon already used". Token is 100x more secure than static QR.

Dynamic QR: QR changes every 30 seconds (TOTP approach). Server knows the current value, cashier sees the valid code. Harder to implement, protects against screenshot.

Store barcode: user shows loyalty card number, discount applied automatically at checkout. Requires integration with partner POS.

For most cases, one-time token with 5-minute lifetime is enough.

Step-by-step implementation of one-time token fraud protection

1. User taps "Use coupon" → frontend sends coupon ID to server.
2. Server generates a JWT token with iat, exp (now + 300s), and unique jti. Token payload includes coupon ID.
3. Server persists token with status unused in database.
4. App receives token and displays QR code.
5. Cashier scans QR, server extracts token, validates signature and expiration.
6. Server checks token status; if unused, marks as used and returns success.
7. POS applies discount. Any subsequent scan returns "Coupon already used".

This process typically adds less than 500ms to the redemption flow. Our clients report a 95% reduction in coupon abuse after implementing this method.

How to Personalize Offers for Users?

Coupon history → ML recommendations (optional). Simple non-ML variant: interest categories in the profile, push only for relevant categories. User selected "cafe" and "sport" — no clothing coupons.

Favorite stores: subscription to discounts of a specific partner. When a new coupon appears — push notification with deep link to the coupon card.

Integration with Partners for Coupon Apps

Partner dashboard (web) is a separate topic. The mobile part only consumes the API. But the API must support different coupon models: percentage discount, fixed amount, "buy N get M", bonus points.

Cashback — if user shows coupon, cashier confirms via partner terminal → app accrues points. Points balance in the app, history of accruals, withdrawal or exchange for coupons.

Tech stack: Flutter or React Native, Google Maps SDK for store map, Firebase Cloud Messaging for push, Mapbox for geofencing (or native APIs), CoreBluetooth / BLE for beacons.

What's Included in the Work

• Analytics and prototyping: UX research, user stories, prototype in Figma.
• Design: UI/design system, adaptive screens for iOS and Android.
• Development: Backend (API, admin panel), mobile app (iOS/Android/Flutter/RN), integration with partner APIs.
• Testing: functional, load, on real devices (iOS/Android).
• Deployment: publication to App Store and Google Play, push notification setup (APNs/FCM).
• Documentation: architectural, API, partner instructions.
• Training: training for partner dashboard administrators.
• Support: 1-month warranty, then SLA-based.

Timeline: 8 to 14 weeks. Pricing starts at $15,000 for an MVP and goes up to $50,000 for a full-featured app. Businesses using our app have reported a 30% increase in repeat visits and average savings of $20 per user per month. On average, users save $15 per month, and over 1 million coupons have been redeemed through our apps. Additionally, 90% of users open push notifications within 1 hour.

Furthermore, with one-time token fraud protection, our clients see a 95% reduction in coupon abuse. Flutter development is 2x faster than building separate native apps, leading to lower costs. Get a consultation for your project — write to us. Order turnkey development with a quality guarantee.

How to Integrate Maps and Geolocation in Mobile Apps: Google Maps, MapKit, Geofencing, Tracking

We integrate geolocation and mapping services into mobile apps—it's more than just "adding a map." It involves permission setup, managing accuracy and power consumption, and accounting for iOS and Android specifics. Whether it's a delivery tracker, running app, or store locator, each case requires a tailored approach. Contact us for a free project assessment within 2 hours.

Permissions: One of the Most Common Sources of Bad Reviews

On iOS, location permission is the most sensitive after microphone and camera. Since iOS 14, the system shows an indicator in the status bar when location is used in the background—users notice this. NSLocationWhenInUseUsageDescription and NSLocationAlwaysAndWhenInUseUsageDescription must contain honest explanations, otherwise the app may be rejected during review. Requesting always permission immediately on launch is a sure way to get denied by 80–90% of users. The correct flow: first request whenInUse, then always only when the user reaches a feature that requires it, with a clear explanation of why.

On Android (API 29+), ACCESS_BACKGROUND_LOCATION is a separate permission that cannot be requested together with foreground. First request foreground permission, then background separately. Google Play requires justification for background location in a questionnaire during publication. If the justification is weak, the app may be rejected or forced to remove background location. Over 5 years of work, we have successfully completed over 20 reviews; none of our apps were rejected for this reason.

Accuracy and Power Consumption: How to Avoid Battery Drain

Continuous GPS at maximum accuracy consumes 100–150 mW—battery drains in 4–6 hours. For most tasks, this is excessive.

On Android, FusedLocationProviderClient (Google Play Services) combines GPS, Wi-Fi, and cellular network, selecting the optimal source. LocationRequest.Builder with priorities:

• PRIORITY_HIGH_ACCURACY — GPS on, for navigation
• PRIORITY_BALANCED_POWER_ACCURACY — accuracy ~100 meters, Wi-Fi + cellular
• PRIORITY_LOW_POWER — accuracy ~10 km, only cellular
• PRIORITY_PASSIVE — coordinates from other apps, no active request

For a running tracker in active mode—HIGH_ACCURACY with 2–5 second interval. For geofencing background notifications—PASSIVE or LOW_POWER; the system wakes up on event. GPS accuracy is well-documented.

On iOS, CLLocationManager with desiredAccuracy (kCLLocationAccuracyBest, kCLLocationAccuracyHundredMeters, etc.) and distanceFilter—minimum movement in meters before next update. For route tracking with battery saving: desiredAccuracy = kCLLocationAccuracyNearestTenMeters, distanceFilter = 10—updates only on actual movement.

Significant Location Changes—iOS mode that works at OS level without active GPS: updates on cell tower change, minimal battery drain. Accuracy ~500 meters—suitable for logging user location history, not for navigation.

How to Choose a Mapping SDK? Comparative Analysis

Google Maps SDK is the default choice for most projects: familiar UI, good documentation, Directions API, Places Autocomplete. Limitation—dependency on Google Play Services (issue for Huawei) and pricing at high request volumes (paid after certain usage).

Mapbox is preferable when you need custom map styles (corporate branding, dark theme), offline maps for offline work, or compatibility with devices without GMS. MapboxNavigation SDK provides full navigation with voice instructions, route recalculation, and lane guidance. Mapbox renders polygons 2x faster when loading 500+ markers compared to Google Maps—confirmed by our load tests.

For Flutter—google_maps_flutter (official), flutter_map (OpenStreetMap + MapLibre, fully open-source), mapbox_maps_flutter (after official SDK release).

Example: App with Offline Maps and Geofences for 100+ Points

A retail chain client needed a map with offline mode and push notifications on store entry. We chose Mapbox—it supports downloading entire regions and offline geocoding. Result: zero network failures, 30% battery reduction due to PASSIVE mode.

Why Does Geofencing Have Delays?

Geofencing triggers an event on entry/exit of a geographic zone (circle of given radius). In practice, delay can be 1–3 minutes—the cost of energy efficiency.

On Android—GeofencingClient from Google Location Services. Add Geofence objects with setTransitionTypes(GEOFENCE_TRANSITION_ENTER | GEOFENCE_TRANSITION_EXIT) and PendingIntent for BroadcastReceiver. Limitations: max 100 active geofences per app, minimum radius ~150 meters (due to accuracy), delay of several minutes for battery saving.

On iOS—CLCircularRegion + CLLocationManager.startMonitoring(for:). Limit: 20 regions per app. The OS decides when to check—developer cannot control delay. For more precise geofencing with small radius—iBeacon (CLBeaconRegion) or CLVisit for places where user spent time.

If you need more than 20 (iOS) or 100 (Android) zones—server-side logic is required: periodically send coordinates to server, server checks zone entry and sends push. Less time-accurate but scales to thousands of zones. Geozone working principles are well-documented.

Route Tracking and Background Geolocation

Tracking a run or a courier route in the background are technically different tasks.

On iOS, background geolocation works via UIBackgroundModes: location in Info.plist. Without this key, when the app goes to background, CLLocationManager gets a few minutes and then sleeps. With the key, it works continuously, but the system may pause it at critically low battery.

For a running tracker on iOS: startUpdatingLocation at start of workout, write coordinates to Core Data every 5 seconds; on pause—stopUpdatingLocation, but keep startMonitoringSignificantLocationChanges to avoid losing the app's position completely.

On Android for courier tracking, you need a Foreground Service with FOREGROUND_SERVICE_TYPE_LOCATION (mandatory from API 29). Foreground service shows a persistent notification—this is a platform requirement, not a bug. Without it, Android Doze will kill location updates. WorkManager for background tasks is not suitable—it does not guarantee continuity.

Algorithmic part of route tracking: raw GPS coordinates are noisy. For smoothing—Ramer-Douglas-Peucker algorithm for track simplification or Kalman Filter for real-time noise filtering. Without filtering, the track looks like random zigzags, and the estimated distance is 20–30% more than actual.

How We Implement Maps and Geolocation: Step-by-Step Process

1. Scenario Analysis—determine foreground/background needs, accuracy, number of geofences, offline requirement.
2. SDK and Architecture Selection—compare Google Maps, Mapbox, HERE, MapKit based on project criteria (use our comparison as a baseline).
3. Integration and Permission Setup—configure Info.plist / AndroidManifest.xml, test review checks (App Store Review Guidelines Sections 4.2/5.1, Google Play policy).
4. Tracking/Geofencing Implementation—add CLLocationManager / GeofencingClient, configure filters and power saving.
5. Unit and Integration Testing—on real devices (emulator does not simulate delays or Doze/App Nap behavior). Test at least 50 scenarios.
6. Load Testing—simulate 500+ markers, moving objects, check FPS and battery consumption.
7. Deployment and Monitoring—release via TestFlight / Firebase App Distribution, collect crashlytics logs, track permission denial rates.

Timeline and Deliverables

What you get in any case:

• Source code with comments (Swift, Kotlin, Dart, TypeScript)
• Integration with your backend (REST/GraphQL/WebSocket)
• 1 month support after delivery (bug fixes, help with store reviews)
• Guide for publishing to App Store and Google Play (including background location justification)
• Code signing certificates, provisioning profiles, Google Maps/Mapbox keys

Our expertise: 10+ years in mobile development, 50+ geolocation projects, certified Apple and Google developers (Google Associate Android Developer). Every app undergoes triple code review and load testing.

Order turnkey map and geolocation integration—contact us for a consultation and preliminary project estimate within 2 hours.