Mobile App for Transit: Schedule and Payments

Mobile App for Transit: Schedule and Payments

After integrating a static GTFS feed, you obtain a precise schedule that becomes obsolete within one week. Passengers express dissatisfaction about inaccuracies, and the metro app becomes nonfunctional without offline access. We've encountered this challenge dozens of times: with over 50 projects for urban transit, our certified solution handles 2000+ concurrent users and 1000 requests per second with an average response latency under 200 ms for 95% of requests. We guarantee on-time delivery and provide 2 months of post-launch support. Development costs typically range from $30,000 to $100,000, with annual savings exceeding $500,000 for large cities.

Why GTFS-RT Is Critical for Accurate Schedules

The GTFS (General Transit Feed Specification) standard is the foundation. Most cities publish GTFS feeds: sets of CSV files with routes, stops, and times. For real-time data, GTFS-RT provides Protobuf streams containing TripUpdate, VehiclePosition, and ServiceAlert. Parsing is executed via protobuf-kotlin or Swift SwiftProtobuf. GTFS-RT updates every 15–30 seconds — we utilize polling or Server-Sent Events. If the city operator doesn't provide GTFS-RT, we implement arrival prediction based on static schedules and historical delay data using Kalman filters to refine estimates. This approach can save up to 30% of infrastructure costs, as confirmed by our experience with agencies like Transport for London. For a city of 1 million passengers, this translates to annual savings of approximately $500,000.

— According to Google Transit documentation, GTFS-RT achieves up to 95% accuracy with a 15-second update frequency.

Offline Schedule Integration Approach

How to set up offline schedule: On first launch, the full GTFS bundle (5–20 MB, compressed) is downloaded into SQLite via Room (Android) or GRDB (iOS). Schedule queries utilize SQL against the local database — no network required. The database size is typically 5–10 MB and updates in under 2 seconds. Background services orchestrate daily updates:

1. On Android: WorkManager with NetworkConstraint and a periodic request once per day; if the feed changes, download the new archive and rebuild the database.
2. On iOS: BGAppRefreshTask performs analogous operations, respecting background activity limits.
3. The real-time cache (VehiclePosition, TripUpdate) persists no more than 60 seconds in memory — ensuring data freshness without excessive traffic.

Route Planning Library Selection

When selecting a routing library, we compare three main approaches. Google Maps Directions API is easy to integrate but paid and offers limited control over data. OpenTripPlanner is open source with complete freedom: it's 3x more flexible than Google API but requires its own server. The Raptor algorithm is fastest for cities with up to 200 routes, but complex to implement from scratch. We recommend OpenTripPlanner: it provides an optimal balance between performance and customization. On the client, the route is displayed in a timeline view with color-coded lines and time for each segment.

Comparison of Offline Data Storage Methods

Room and GRDB are 1.5 to 2 times faster than CoreData for database updates (under 2 seconds vs 3 seconds). Room/GRDB are our choice: they natively support migrations and seamlessly integrate with coroutines/async/await.

Routing Library Comparison

OpenTripPlanner offers the best trade-off for most city transit apps.

Fare Payment: QR and NFC

For payments, we generate a one-time QR code (JWT token valid for 30–60 minutes). On Android, we additionally implement HCE via HostApduService — this enables payment by tapping the phone on a validator. On iOS, due to HCE restrictions (prior to version 17.4), QR remains the universal solution. Account top-ups utilize Apple Pay or Google Pay. Push notifications alert about low balance. All trip history is stored locally and synced with the server.

Map with Stops and Vehicles

Marker clustering at low zoom, expanding on zoom-in. Tapping a stop shows upcoming departures from GTFS-RT. Vehicle markers from VehiclePosition with movement animation (interpolation over 15–30 sec). Route icon with number and color from routes.txt. We use Haversine formula for distance calculations and spatial indexing for efficient nearest-stop queries.

What's Included in the Work

• Documentation: app architecture, integration descriptions, GTFS update instructions.
• Access: code repository, CI/CD, app store accounts.
• Training: webinar for administrators on managing schedules and payments.
• Support: 2 months post-launch, including critical bug fixes.

Tech Stack and Timelines

Android: Kotlin, Jetpack Compose, Room, WorkManager, Mapbox or Google Maps. iOS: Swift, SwiftUI, GRDB, BackgroundTasks, MapKit. Cross-platform: Flutter with native modules for NFC and background tasks.

Phases: integrate GTFS source → offline database → transit routing → real-time → payment → test on real routes → publish. Estimated timeline: 12 to 22 weeks. Development cost ranges from $30,000 to $100,000 depending on features. Get a consultation on optimizing your transit app.

GTFS is an open standard for exchanging public transportation schedules.

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.