Skip to content
WLOCAuthorized iOS location testing

Use cases

Route, geofence, and movement-state QA without a live drive

Route and geofence bugs show up as “arrived but cannot drop off,” “coupon fired in the parking garage,” or “the warehouse dock never armed.” This hub is for movement-state QA on apps you maintain, without sending a courier across town for every edge.

Movement states you can name

Movement states you can name

Pickup, en-route, at-door, inside fence, neighboring unit, and outside threshold are different product states. If your team only ever tests the store-center pin, the expensive mistakes stay hidden until a live order or a campaign weekend.

Use cases

Route, geofence, and movement-state QA without a live drive

Directory rehearsals: courier pickup and drop-off, path preview, retail fence, home-arrival automation, and warehouse dock arming. A venue-staging card also cross-links when the same fence logic is shared.

Walk the polyline on a desk

Walk the polyline on a desk

  1. Save the real path as named points, including the unit next door and the garage.

  2. Replay pickup → travel → fence enter → fence leave with a test order or test offer.

  3. Hand the mismatches to configuration, then Restore so the next rehearsal is clean.

Your logistics, not a live delivery

Your logistics, not a live delivery

These pages validate states in apps you own. They do not complete a real delivery, fire a customer coupon in production, or claim every map SDK will animate the same way. Watch the preview on the phone, then Restore after the polyline packet is filed.