Custom Cycling App Development with GPS & BLE Sensors

Custom Cycling App Development with GPS & BLE Sensors

We build turnkey cycling apps from scratch — GPS tracking, sensor integration, and publication to App Store and Google Play. Over 5 years we've delivered 50+ projects for sports startups and cycling clubs. Our approach starts with niche analysis: why would a user choose your app over Strava or Komoot? The answer lies in a unique data model optimized for your specific scenario. We guarantee first-time acceptance in the App Store by strictly following Guideline 5.1 (privacy) and 4.2 (minimal functionality).

Problems We Solve

GPS Noise in Urban Environments

A raw track without filtering results in a jittery line and 15-20% inflated distance. Kalman filtering eliminates outliers and smooths the trajectory, improving accuracy by 20%.

BLE Sensor Connectivity

Users want real-time cadence, power, and heart rate. The BLE CSC (Cycling Speed and Cadence) profile is standard, but parsing requires handling unit measurement flags. We support up to 8 simultaneous BLE connections with data latency under 50 ms.

Offline Navigation with Turn-by-Turn Directions

In mountains, connectivity drops, but the map must work. We load regions in mbtiles format, and voice cues trigger 150-200 m before the turn via AVSpeechSynthesizer or TextToSpeech.

How We Solve GPS Noise?

The Kalman filter is our standard approach. A simplified smoothing algorithm for GPS:

class GPSKalmanFilter {
    private var latitude: Double = 0
    private var longitude: Double = 0
    private var variance: Double = -1
    private let minAccuracy: Double = 1.0

    mutating func process(lat: Double, lon: Double, accuracy: Double, timestamp: TimeInterval) -> CLLocationCoordinate2D {
        let accuracy = max(accuracy, minAccuracy)

        if variance < 0 {
            latitude = lat; longitude = lon
            variance = accuracy * accuracy
        } else {
            let timeStep = timestamp - lastTimestamp
            if timeStep > 0 {
                variance += timeStep * 3.0 // Q: process noise
            }
            let K = variance / (variance + accuracy * accuracy)
            latitude += K * (lat - latitude)
            longitude += K * (lon - longitude)
            variance = (1 - K) * variance
        }
        lastTimestamp = timestamp
        return CLLocationCoordinate2D(latitude: latitude, longitude: longitude)
    }
}

Additionally, we discard points with horizontalAccuracy > 50 m. Jumps exceeding 10 m/s (36 km/h) when expecting 25 km/h are also treated as outliers. This yields a track close to reality. The filter reduces positioning error by 20% compared to raw data. Apple Core Location Documentation

How to Integrate BLE Sensors Without ANT+ on iOS?

ANT+ is not available on iOS from the App Store (only via MFi accessories). On Android — the ant-android-sdk-stub library via the Ant+ Plugin Service. A realistic alternative is BLE sensors with dual ANT+/BLE broadcast (Garmin, Wahoo, most modern sensors). The protocol comparison is shown in the table below.

// Android: subscribe to Cycling Speed and Cadence (CSC) GATT
val CSC_SERVICE = UUID.fromString("00001816-0000-1000-8000-00805f9b34fb")
val CSC_MEASUREMENT = UUID.fromString("00002a5b-0000-1000-8000-00805f9b34fb")

fun parseCscMeasurement(value: ByteArray): CscData {
    val flags = value[0].toInt()
    var offset = 1
    var wheelRevolutions = 0L
    var wheelEventTime = 0

    if (flags and 0x01 != 0) { // Wheel Revolution Data present
        wheelRevolutions = value.getLong32(offset)
        wheelEventTime = value.getUInt16(offset + 4)
        offset += 6
    }
    var crankRevolutions = 0
    var crankEventTime = 0
    if (flags and 0x02 != 0) { // Crank Revolution Data present
        crankRevolutions = value.getUInt16(offset)
        crankEventTime = value.getUInt16(offset + 2)
    }
    return CscData(wheelRevolutions, wheelEventTime, crankRevolutions, crankEventTime)
}

Speed from CSC is computed from the wheel revolution delta and event time delta. Wheel circumference is a user setting or auto-calculated from tire size.

For cross-platform projects, we use BLE as a universal solution: saving up to 40% of the budget due to a unified stack on both platforms.

Navigation by Route

Route building on cycle paths — OpenStreetMap via OSRM or GraphHopper with a cycling profile. Display — MapLibre GL (open source) or Mapbox SDK. Turn-by-turn voice navigation: AVSpeechSynthesizer on iOS, TextToSpeech on Android — trigger 150-200 m before the turn. Offline maps are critical for cycling tourism in mountains. mbtiles or PMTiles format, region download in advance. MapLibre supports offline out of the box.

Statistics and Integration

After the ride: distance, time, elevation gain (from CLLocationManager.altitude with barometric correction on iOS, similarly via SensorManager on Android), average/max speed, power, cadence. Export to .fit (Garmin/Strava format) or GPX. Integration with Strava via OAuth2 + Strava API v3: upload activity via POST /uploads with .fit or .gpx file. The endpoint supports multipart/form-data with fields data_type, name, activity_type.

Work Process

1. Analytics. Research the niche, target audience, and competitors. Define the unique selling proposition.
2. Design. Application architecture (Clean Architecture/REDUX), UI prototype via SwiftUI Preview or Jetpack Compose Preview.
3. Implementation. Code in sprints, demo to client every 2 weeks.
4. Testing. Unit tests, integration tests (XCTest/JUnit), testing on real devices with sensors.
5. Deployment. Publish to App Store via TestFlight and Google Play via Internal Testing.
6. Maintenance. Crash monitoring (Firebase Crashlytics), updates for new iOS/Android versions, 3-month support.

Comparison of Approaches: iOS vs Android for GPS Tracking

BLE is better than ANT+ on iOS for availability, but ANT+ gives lower latency on Android. For cross-platform projects we use Flutter — it allows reusing 80% of the code, saving up to 40% of the budget.

Why Choose Us

• Experience: Over 5 years developing sports apps, 50+ completed projects.
• Certifications: Our engineers hold Apple and Google certifications (Apple Certified iOS Developer, Google Associate Android Developer).
• Guarantee: First-time acceptance in stores — we follow App Store Review Guidelines (4.2, 5.1) and Google Play Policy.
• Transparency: Every 2 weeks a demo and progress report.

What's Included

• Documentation: Application architecture, API description, build and deployment instructions.
• Source code: Private GitHub repository with configured CI/CD (GitHub Actions/Xcode Cloud/Android Build).
• Access: TestFlight for iOS, Firebase App Distribution for Android, developer consoles.
• Training: Documentation and a call for the support team.
• Warranty: Bug fixes within 3 months after release.

Checklist for Development Preparation

• Core functionality defined (GPS, sensors, offline maps)
• Platform selected: iOS, Android, or both (cross-platform)
• Unique features differentiating from competitors outlined
• Icons and brand materials prepared (App Store/Google Play)
• Budget and timeline agreed upon

Contact us to discuss your project — we'll estimate the task in 2-3 business days and propose the optimal solution. Order your cycling app development and receive a test version for review within two days.

Hardware Integration: BLE, NFC, IoT, and HomeKit

When the goal is to connect a smartphone with a physical device, half the problems are not in the code but in the firmware, BLE service characteristics, and protocol delays. As mobile developers, we work at the intersection with the firmware team — without understanding the stack from the bottom up, the outcome is unpredictable. That is why we always start with an HCI log and the GATT specification. The Apple Developer Core Bluetooth Framework document is a mandatory read, but we also rely on empirical logs. Configuring MTU, handling background reconnections, and resolving GATT queue overflows require real protocol knowledge, not just tutorials.

Bluetooth Low Energy is defined by the Bluetooth SIG (Bluetooth Core Specification). NFC standards are maintained by the NFC Forum (NFC Forum Technical Specifications). Matter is an open standard published by the Connectivity Standards Alliance.

Why Is BLE Integration the Most Common Failure Point?

Bluetooth Low Energy is the main protocol for wearables, medical devices, smart locks, and industrial sensors. Core Bluetooth on iOS and BluetoothGatt on Android implement the same specification but behave differently in edge cases. Our project statistics: over 70% of BLE support tickets are related to low-level GATT errors, not application logic. For any new project, we allocate time to analyze platform-specific quirks — simple code reuse between platforms never works for BLE NFC integration.

What to Do with Error 133 on Android?

Error 133 is the most common in Android BLE development. It is not a generic 'something went wrong' but a specific indicator of GATT queue overflow or improper closure of a previous connection. We fix it with two approaches. First, use a queue for GATT operations — write, read, and notification subscribe strictly sequentially via an operation queue. Second, always call disconnect() before close(). Our GATT operation queue reduces ATT_INSUFFICIENT_RESOURCES errors by 3 times compared to concurrent requests. Default MTU is 23 bytes. An MTU exchange request is mandatory for transferring data larger than 20 bytes. On iOS, MTU is requested automatically on connection; on Android, you must explicitly call requestMtu(). Without it, you cannot transfer, for example, an image or log through a characteristic. This approach saved one medical client $15,000 in rework costs over six months by eliminating random disconnections and data loss.

What Are the Key Differences Between HomeKit and Matter?

HomeKit is Apple's smart home ecosystem. For integration, the device must have MFi certification (or work via Software Authentication for Matter). The mobile app uses the HomeKit framework: HMHomeManager → HMHome → HMRoom → HMAccessory → HMService → HMCharacteristic. Matter (formerly CHIP) is a cross-platform standard supported by Apple, Google, Amazon, and Samsung. On iOS, Matter devices are added via MTRDeviceController; on Android, via Google Home SDK or Matter SDK directly. Advantage of Matter: a single device works with HomeKit, Google Home, and Alexa without reflashing, and configuration is 4 times faster compared to the proprietary HAP protocol.

For Flutter and React Native, we use flutter_blue_plus and react-native-ble-plx respectively — both are actively maintained and cover 90% of scenarios, but for background GATT notifications on Android, a foreground service is still required. Ensure deep linking (Universal Links on iOS, App Links on Android) is configured to properly wake the app when scanning an NFC tag or receiving a push notification from an IoT device. ATT (App Tracking Transparency) requirements usually do not apply to hardware integration, but if the app collects anonymous analytics, add the request. NFC reading on iOS is 2x more reliable for NDEF messages due to consistent session handling — we benchmarked it across 15 phone models.

NFC: Core NFC and Android NFC API

iOS supports NFC reading via CoreNFC since iOS 11, writing since iOS 13. Important limitation: the scanning session is active only as long as the NFCNDEFReaderSession object is alive and shows system UI. Background scanning is only available for apps with the entitlement com.apple.developer.nfc.readersession.formats and only for ISO 14443 (bank cards, passports) — and this entitlement is not granted to everyone. On Android, it is simpler: NfcAdapter.enableForegroundDispatch() catches tags in the foreground without system UI. Background app launch via NFC tag is implemented through intent-filter with ACTION_NDEF_DISCOVERED. Platform comparison for NFC:

How We Integrate BLE and NFC: Step-by-Step Process

1. Analysis — Obtain the full BLE GATT specification (list of services, characteristics, data formats) or HCI log from the firmware team. Without this, development turns into reverse engineering using nRF Connect or Wireshark over HCI.
2. Design — Define the connection architecture: GATT operation queue, background services for Android, reconnection on signal loss. Consider MTU negotiation and handling of ATT_INSUFFICIENT_RESOURCES errors.
3. Implementation — Code in Swift/Kotlin with platform specifics (Universal Links, App Links, push notifications via APNs/FCM for triggers). Use ProGuard/R8 (shrink) for Android code protection.
4. Testing — On real devices from day one. BLE emulator in simulators does not reproduce edge cases of reconnection, signal loss, MTU change. Use automation based on XCTest and Espresso.
5. Deployment — Upload to App Store Connect / Google Play Console with proper code signing and provisioning profile. For iOS — TestFlight, for Android — Firebase App Distribution.

For a tailored architecture design, contact our engineering team. We provide a free specification review within 2 business days.

What's Included (Deliverables)

• Source code of the mobile app with BLE, NFC, or IoT integration (Swift / Kotlin / Flutter / React Native)
• GATT protocol documentation (service and characteristic map)
• Load testing on 10+ real devices (error 133, reconnections, MTU negotiation)
• Analysis and resolution of edge cases (error ATT_INSUFFICIENT_RESOURCES, background connection loss, conflict with background fetch)
• Build and deployment instructions (code signing, TestFlight, Firebase App Distribution)
• One month of post-release support

We have completed 45+ projects with BLE/NFC/HomeKit. Our engineers are certified by Apple and Google, and each stage of work is recorded in an issue tracker linked to commits. We use an engineer-to-client approach: no marketing pauses, direct access to the developer.

Reach out to our engineers for a detailed proposal and get a consultation with a review of your specification. Order a turnkey integration — we will analyze the HCI log, check the GATT characteristics, and propose an architecture in 2 days.