Kickstart Overdrive

Use the companion menu bar app to inspect and control Simulator while you build.

Keep Testing Tools Beside Simulator

Kickstart Overdrive is a separate companion app that puts testing and capture tools right beside Simulator. You can change conditions, inspect saved data, compare the interface with a design, and record what happens without endlessly hunting through different utilities.

Overdrive follows the frontmost Simulator window. Bring the device you want to work with to the front, pick the app you're testing, and use the tab that fits the job.

Pick a First Job

You don't need every inspector to get started. Just try one of these workflows:

• Check a layout: Open the app at a particular screen, import its design in Compare, and adjust the overlay to see where the two differ.
• Record a feature: Set a consistent time and battery display in Status, choose a save location in Capture, then record the flow you want to show.
• Test accessibility: Use Overrides to try larger text or a different appearance, then work through the screen as you normally would.
• Investigate saved state: Select the app and open Defaults, Data, or Files to see what changed after an action.

Most everyday Simulator tools don't need any changes to your app. Network and notification inspection use the optional Relay integration in a debug build, as explained below.

Setup

1. Click Launch Now from Kickstart's welcome screen or Build activity.
2. Grant simulator access when Overdrive asks for it. This lets it read installed apps, app containers, app groups, UserDefaults, and simulator metadata.
3. Grant Screen Recording permission. Overdrive uses this to detect the active Simulator window, compare designs, capture video, show touches, and inspect the live simulator screen.
4. Bring an iOS Simulator window to the front. Overdrive shows tools for that simulator and updates when you switch to another one.
5. For Relay-based tools, add the Overdrive Relay support to a debug build of your app and run that app in Simulator. Relay powers network inspection, notification inspection, network throttling, and memory pressure triggers.

Top-Level Tabs

The main panel is organized around seven tabs: System, Compare, Capture, Status, Location, Overrides, and Debug.

System

Use System for app-level simulator work: launching, restarting, quitting, deleting, opening containers, changing permissions, sending triggers, and moving clipboard contents between macOS and Simulator.

• Application: choose an installed user app, then launch, restart, quit, or delete it from the selected simulator.
• App Data: open the app data folder, app group folder, app bundle, UserDefaults inspector, Data Inspector, or clear restoration state.
• Permissions: grant, revoke, or reset simulator privacy permissions for the selected app.
• App Triggers: send saved push notifications or open saved deep links. You can also jump straight to the editors for those saved triggers.
• Clipboard: copy the simulator pasteboard to your Mac, or push your Mac clipboard into Simulator.

Compare

Use Compare when you want to line up a live simulator screen with a design reference, screenshot, or mockup.

• Import comparison images and keep saved references around for later sessions.
• Switch comparison modes between None, Split, and Overlay.
• Adjust reference opacity when an overlay is active.
• Delete old references once a design round is done.
• Sample colors from the screen, keep a reusable color history, copy SwiftUI, UIKit, or AppKit color code, and drag color swatches into an asset catalog.

Capture

Use Capture for clean screenshots and recordings of the current simulator.

• Choose a save location before capturing assets.
• Capture PNG screenshots or MP4 recordings.
• Add device bezels or choose no bezel for square or rounded output.
• Record system audio, microphone audio, or both when permissions allow.
• Show touches in recordings, choose a touch color, and set a background color for rendered output.
• Stop active recordings from the panel and watch export progress while Overdrive finishes the file.

Status

Use Status to force predictable simulator status bar values before testing screens or taking screenshots.

• Set a custom date and time, set the classic 9:41 time, or clear the time override.
• Change carrier text, network type, Wi-Fi mode, Wi-Fi bars, cellular mode, and cellular bars.
• Set battery state and battery level.
• Clear overrides when you want the simulator to go back to its normal values.

Location

Use Location to test maps, geofencing, weather, travel, check-in, and route-based features.

• Search for places, set coordinates from the map, copy the current coordinates, save locations, and clear the active location.
• Turn on jitter to move the simulated location slightly over time, which is handy for testing apps that react to small GPS changes.
• Import GPX routes, choose playback speed, and play, pause, resume, stop, or clear route simulation.
• Use saved locations for repeatable testing across sessions.
• Start and stop built-in simulator location scenarios when Xcode provides them.

Overrides

Use Overrides to test system presentation and accessibility settings without digging through the Simulator app.

• Switch appearance between Light and Dark.
• Set language and locale overrides. These require a simulator reboot to take effect.
• Change Dynamic Type content size.
• Toggle accessibility overrides such as Bold Text, Button Shapes, Differentiate Without Color, Increase Contrast, On/Off Labels, Reduce Motion, Prefer Cross-Fades, Reduce Transparency, Smart Invert, and Tinted Liquid Glass.

Debug

Use Debug for deeper inspection and active testing of a selected simulator app. Pick an app first, then choose one of the Debug inspectors.

• Force iCloud Sync: asks the simulator to sync iCloud data now.
• Reset Keychain: clears simulator keychain state for testing first-run, sign-in, and migration flows.
• Slow Animations: toggles slower simulator animations so you can get a proper look at transitions.
• Trigger Memory Pressure: appears when Relay is connected and sends a simulated memory warning to the selected app.
• Inspector tabs: Network, Notifications, Defaults, Data, Files, and Stress.

Debug Inspectors

Most Debug inspectors have a compact view inside the Overdrive panel and a full details window for longer inspection sessions. Relay-based inspectors need a debug app with Relay connected; file, defaults, and data inspectors work from simulator container access.

Network Inspector

The Network Inspector watches requests made by Relay-connected apps and helps you track down slow, failed, blocked, or unexpected traffic.

• The compact view shows the newest requests for the selected app, including method, status or error, host, and path.
• The full view includes request count, unique hosts, average response time, app scoping, search, method filters, verdict filters, and a clear button.
• Select a request to inspect summary data, request headers, request body, response headers, response body, status, duration, sizes, errors, and source app.
• JSON bodies are formatted when possible, text bodies are readable, and binary bodies are summarized with a hex preview.
• The Throttle control can fail monitored requests, apply presets such as Very Bad Network, Edge, 3G, LTE, and Wi-Fi, or use custom download speed, upload speed, latency, and failure rate values.

Notification Inspector

The Notification Inspector records local and remote notification lifecycle events from a Relay-connected app.

• The compact view shows recent notification events for the selected app, with event type, identifier, title, body, time, and action identifier when available.
• The full view shows a searchable event stream with counts, unique notification identifiers, source app, userInfo key counts, and a clear button.
• Select an event to inspect kind, observed time, origin, app, identifier, title, subtitle, body, trigger kind, trigger details, badge, category, thread, action, userInfo keys, and source bundle ID.
• Event coloring makes queued, delivered, presented, responded, and removed events easier to scan.
• Use it when testing notification scheduling, presentation, categories, actions, deep links, and cleanup behavior.

UserDefaults Inspector

The UserDefaults Inspector lets you read and edit the selected app's defaults without bolting on temporary debug UI.

• The compact view loads the selected app's defaults, monitors for changes, and highlights rows that changed recently.
• The full view lets you choose the app, enter a suite name, reload defaults, search by key or value, and edit values in place.
• Supported editable values include strings, integers, doubles, Booleans, dates, data encoded as Base64, arrays, and dictionaries.
• Import plist files to replace or merge defaults, export the current defaults, delete individual keys, or delete all keys in the current domain.
• Built-in system entries are marked so you can tell app settings apart from simulator or framework defaults.

Data Inspector

The Data Inspector browses SQLite-backed app data, including SwiftData and Core Data stores, directly from the simulator container.

• Overdrive scans app containers and app groups for .store, .sqlite, .sqlite3, and .db files.
• The compact view lets you drill down from stores to tables to rows, with change flashes when store files or tables update.
• The full view has an app and store selector, table list, row browser, search over loaded rows, sortable columns, refresh, and store path help.
• Rows are shown in a table with visible columns only, and editable cells can be changed directly when the inspector can write the value safely.
• Use it for checking saved model state, migrations, cache tables, sync metadata, and whether user actions are actually writing the data you expect.

File System Browser

The File System Browser lets you poke around the selected app's sandbox and open or delete files while the simulator is running.

• The compact view shows the current folder, supports back navigation, opens the current folder in Finder, and flashes items that changed.
• The full view has an app picker, a sidebar tree for the app sandbox, context menu deletion, and a detail pane for selected files.
• File previews show path, size, MIME type when available, readable UTF-8 text, and a binary summary when text preview isn't possible.
• Large files show a preview of the first chunk rather than cramming the whole file into the UI.
• Use it for inspecting documents, caches, logs, media, downloaded files, exported reports, and other sandbox artifacts.

Stress Tester

Stress Tester drives the simulator with random taps, swipes, and long presses so you can flush out crashes, broken navigation states, and fragile interaction flows.

• Stress Tester requires macOS Accessibility permission because it injects mouse input into Simulator.
• Choose a simulator and app, or use the locked app when opened from the Debug panel.
• Set a random seed so a useful run can be repeated later.
• Adjust the event interval and choose which input types are allowed: taps, swipes, and long presses.
• Start a run, then shake the mouse to stop it at any time.
• Review recent events, hot targets, possible crash notes, failure evidence screenshots, and copy a run report after the test finishes.

Menu Bar Tools

Overdrive also has a menu bar presence for quick developer references and maintenance tasks.

• Open Dev Reference for device sizes, SF Symbols, system fonts, Dynamic Type, and other common app-building lookups.
• Click a device resolution in Dev Reference to switch between point and pixel dimensions.
• Use Xcode data cleanup when local build data is bogging down your development loop.
• Turn on Launch Overdrive at Login if you want the companion app ready whenever you sign in.
• Keep Overdrive running while you work so simulator-heavy tools stay close to the active Simulator window.

Practical Tips

For a repeatable investigation, jot down the app build, simulator, and conditions you used. If a problem only happens at one location or with a particular stored value, that context is part of the bug report.

Resetting permissions, deleting an app, clearing defaults, and resetting keychain state change different parts of the environment. Pick the action that matches what you're testing rather than assuming a restart wipes everything. Inspector edits and deletion actions affect the selected simulator app's data, so double-check the selection before using them.

• Use Compare before manually nudging SwiftUI layouts. It's faster to see the mismatch first.
• Use Status and Capture together when making App Store, support, or documentation screenshots.
• Save locations and GPX routes for states you need to reproduce often.
• Use Overrides early when building accessibility-sensitive screens, not just at the end of a release.
• Only include Relay in debug builds. It's meant for local inspection and simulator testing, not production behavior.
• Use Stress Tester with a saved seed when you hit an interesting failure, then copy the report before clearing the run.