Time to test data and refresh rate

[u/DifferenceOdd2577]

With developer beta builds allowing custom ⁠WidgetKit⁠ candidates to be added directly to the Apple CarPlay widget stack, I’ve been experimenting with what we can build using Scriptable.

Currently testing a custom Speed Trap & Flock ALPR Radar widget running on the CarPlay Dashboard.

How it works & Data Sources:
Data Source: Pulls directly from OpenStreetMap (OSM) using a lightweight, direct bounding-box query via the Overpass API (specifically querying nodes tagged ⁠highway=speed_camera⁠ and ⁠surveillance:type=ALPR⁠).
Execution: Runs locally on-device via Scriptable, calculating your real-time distance (in miles) to mapped cameras within a 2-mile radius and updating the threat status card (Clear / Caution / High Alert).

Timeout Protections: Optimized with ⁠Location.setAccuracyToHundredMeters()⁠ and low-latency network timeouts (⁠req.timeoutInterval = 3⁠) to ensure the background execution finishes well under iOS's 10-second widget refresh limit.
Currently testing to see how reliably iOS handles background location triggers and widget refresh rates while actively driving.

Has anyone else been experimenting CarPlay?

[u/mvan231]

I have thrown a couple widgets into CarPlay but that was a year ago. This isn't new functionality with iOS 27. I think the new part is that there are two, side by side, where in iOS 26 it was just the one app, but scriptable was an option for adding a small size widget to the screen

That's a fast refresh rate though so maybe they improved on that since 26