Your Apple-dev toolkit, one click away

Browse and edit the app's SQLite database

Select an installed app and Devil lists the SQLite databases inside its container, every table in them, and the rows themselves. Switch between the data and the schema, search rows, and correct a value in place instead of rebuilding to reach one field.

Read and edit UserDefaults, down to nested values

Three columns: every defaults file in the container, the keys inside the one you pick, and the value itself. Each key carries its type, so a Bool is distinguishable from the JSON blob next to it at a glance. Nested JSON opens as raw text, formatted output, or a searchable tree, and a buried flag takes a moment to find rather than a debugging session. Supported property-list values are editable in place.

Put the simulator anywhere

Seven preset cities cover the usual cases. For everything else, search for a place or drop a pin straight on the map, then save it under a name you will recognize. The location applies to the active simulator immediately, and saved places are stored globally, so every simulator you boot can reuse them.

Every branch, local and origin, in one table

Each repository gets a Branches page. It fetches and prunes origin first, then puts local and remote branches in one searchable table with their upstream, their ahead and behind counts, and the current and default markers. When the remote is unreachable the last snapshot stays on screen instead of emptying out.

Create and check out

Branch from where you are, or check out a branch that only exists on origin and get a local tracking branch for it. Both want a completely clean tree first.

Publish and rename

Push a branch to origin for the first time and set its upstream, or rename it locally and on the remote together, with explicit recovery actions if a network step is interrupted.

Delete, once merged

Local and origin deletion is offered for merged branches. Discarding unmerged work is not a decision a menu-bar utility should make for you.

Answer a request with your own response

Pick a request that already completed, choose Create Mock, and the matcher arrives filled in from the real call. Keep it exact, or add a condition on a query item, a header, a JSON path or the raw body when only one variant should be caught. Edit the JSON body scalar by scalar instead of retyping the document. Save and enable it, and the next matching request is answered inside the capture framework before a real task is ever created.

Return what you need

Any HTTP status, safe headers, a JSON or UTF-8 text body, and up to sixty seconds of added latency when you want to see the loading state properly.

Or return nothing at all

Simulate offline, a timeout, a lost connection, or a host that cannot be found or reached, so the error path gets exercised without unplugging anything.

Fails open, always

A disabled rule, an unpaired or disconnected app, a rejected snapshot, the global Master Off, or simply no match — every one of them falls through to the real network.