Build real-time order tracking and delivery driver systems with PubNub
91
65%
Does it follow best practices?
Impact
94%
1.84xAverage score across 15 eval scenarios
Advisory
Suggest reviewing before use
GPS location streaming and battery optimization
Driver location channel naming
0%
100%
userId set on SDK init
100%
100%
Restore and network detection
0%
100%
Heartbeat interval configured
0%
100%
Adaptive publish frequency
100%
100%
Near-destination high frequency
0%
100%
Stationary skip threshold
62%
0%
Max frequency cap
100%
100%
Haversine distance calculation
100%
100%
storeInHistory disabled for GPS
0%
100%
Location message fields
40%
100%
Presence for driver status
0%
0%
Order status pipeline and server-side validation
Order status channel naming
0%
100%
All lifecycle states defined
40%
100%
Correct transition rules
30%
100%
Server-side validation function
100%
100%
Invalid transition blocking
100%
100%
Dual channel publishing
50%
100%
Previous status included
100%
100%
storeInHistory for status
0%
100%
Timestamp in messages
100%
100%
Terminal states handled
100%
100%
Message deduplication consideration
0%
0%
Customer tracking page with privacy controls
Subscribes to both channels
0%
100%
Separate handling for location vs status
100%
100%
Smooth marker animation
100%
100%
30-frame interpolation
100%
100%
Fetches last location on init
50%
100%
Progressive location privacy
100%
100%
Distance thresholds for privacy
37%
100%
ETA debouncing
0%
100%
ETA buffer multiplier
0%
100%
Minimum speed floor for ETA
0%
100%
Customer SDK init with restore
0%
0%
Unsubscribe on stop
100%
100%
Dispatch coordination and failed delivery handling
Nearest driver selection
100%
100%
Haversine for dispatch distance
100%
100%
Presence-based driver tracking
0%
100%
Driver commands channel
0%
100%
Dispatch channel usage
0%
100%
Failed delivery notification
0%
100%
Driver freed on failure
50%
100%
Retry limit of 3
100%
100%
Geofence pickup threshold
0%
100%
Geofence dropoff threshold
0%
100%
Channel groups for fleet
0%
100%
Chat, push notifications, and proof of delivery
Chat channel naming
0%
100%
Chat history loading
100%
100%
Quick reply templates
100%
100%
APNS push payload
100%
100%
GCM/FCM push payload
100%
100%
Photo proof of delivery
100%
100%
PIN or signature proof
100%
100%
Proof stored in history
100%
100%
Access token management
50%
100%
Post-delivery cleanup
100%
100%
Chat storeInHistory enabled
0%
100%