DevHub: A macOS Offline Toolbox for Developers Who Keep Opening Browser Tabs

The Problem DevHub Targets: Tool Sprawl on macOS

The README frames the goal plainly: DevHub is meant to replace "a scattered set of web tools, shell snippets, and temporary utility sites." That is a real pattern. A developer decoding a JWT pastes it into a website and hopes the site does not log it. A developer converting an image to Base64 opens a browser, uploads the file, and downloads a text blob. Each step is small; the aggregate is a dozen browser tabs and a low-grade privacy question every time.

DevHub answers that with one macOS application that runs the work locally. The README describes it as "offline first" and "built primarily for local use, which is useful when privacy and stability matter." The intended audience is broad: frontend engineers working with JSON, URL, Base64, HTML, CSS, QR codes, colors and image assets; backend engineers working with JWT, hashes, Basic Auth, RSA keys, timestamps, API requests and data conversion; QA and DevOps engineers working with regex, crontab, ports, permissions, time and device information; and indie developers who want a fast, low-friction utility collection. The common thread is that none of these tasks need a network round trip, and all of them benefit from being one keystroke away instead of one search away.

How DevHub Is Built: SwiftUI, Local Execution, URL Scheme

The repository's primary language is Swift, and the topics list includes swiftui, swiftui-app and macos-app, so the UI layer is SwiftUI on top of macOS. The README does not describe an internal module layout, a plugin API, or a scripting surface beyond one integration point: URL Scheme support. The README states that this "integrates with Raycast, browsers, terminal commands, and automation workflows," and that you can "trigger specific tools through URL Scheme from Raycast or personal automation workflows."

That is the whole extensibility story visible in the repository. There is no documented plugin system, no command-line binary, and no server component. The data flow is the simplest possible one: you open a tool window, paste or drop input, and the result is computed on the machine. Nothing in the README describes telemetry, sync, accounts or cloud storage, which is consistent with the offline-first claim. The trade-off is that DevHub cannot be scripted beyond the URL Scheme, so it will not slot into a CI pipeline or a build script the way a CLI tool would.

The tool coverage is the substance of the app. The README groups it into text and encoding (Base64, Unicode, ASCII, HTML encode/decode, text case conversion, word count, Morse code), code and data (JSON formatting, HTML to Markdown, Prettier, regex testing, URL parsing, JWT parsing), images and media (OCR, image watermarking, ICO conversion, image to Base64, color extraction, EXIF viewing), productivity and system (world time, date conversion, chronometer, random port generation, device info, file info, chmod calculator), and security and network (API requests, SSL management, hash generation, Basic Auth generation, RSA key generation). The README also carries a long checklist of completed tools, from a timestamp converter and an HTML to Markdown tool through to a WiFi QR code generator, a random port generator and a chmod calculator.

Installing DevHub and Running a First Task

The README does not document a Homebrew cask, a source build, or a downloadable disk image hosted in the repository. What it does provide is an App Store link, rendered as a badge pointing at an Apple ID (6476452351), and a macOS 14+ requirement badge. So the documented install path is the App Store, not a package manager. The repository is source-available in the sense that the Swift project lives on GitHub, but the README gives no build instructions, so treat the App Store as the supported route.

Once installed, the first useful task is the one most developers repeat: formatting a JSON payload. The README lists JSON formatting under code and data tools. Open DevHub, pick the JSON formatter, and paste a minified object. The README does not show the exact output pane, so expect a formatted view rather than a guaranteed diff or schema validation.

The second task worth trying is the JWT parser, because it demonstrates the privacy argument. Copy a token and paste it into the JWT parser tool. The README lists JWT parsing under code and data and JWT under backend use cases. If the app behaves as described, the token is decoded locally and never leaves the machine, which is the concrete difference from the average JWT decoding website.

The third is the URL Scheme entry point, which is how DevHub is meant to be reached without clicking through the UI. The README does not publish the scheme string, so the honest next step is to check the app's own documentation or the release notes for the exact URL format before wiring it into Raycast. The README states the capability exists but does not spell out the identifier, and guessing it would be guesswork.

Where DevHub Falls Short

The most obvious limitation is the platform. DevHub is a macOS app requiring macOS 14 or newer, per the repository badge. Windows and Linux developers are out entirely, and so are Macs that cannot run macOS 14. That is a hard boundary, not a soft one, and it rules out a large share of the audience for a general-purpose developer toolbox.

The second limitation is the absence of a documented CLI or plugin API. The README's only automation surface is the URL Scheme, and the README does not publish the scheme format. If your workflow depends on piping data through a shell command or embedding a formatter in a build step, DevHub is the wrong tool. A small command-line utility such as jq for JSON or openssl for hashing will serve that case better and is scriptable by design.

The third is the breadth-versus-depth trade-off. The README describes a goal of curating "over 100 utilities," and the completed-tools checklist is long. A toolbox with that many small tools will inevitably have some entries that are shallower than a dedicated app. The README does not publish per-tool limitations, so the only way to judge a specific tool is to open it and compare against whatever you use today. If you need a serious regex debugger with step-through execution, or a full image editor, DevHub is a convenience layer rather than a replacement.

Finally, the README does not state the licence, and the repository's top-level entries include privacy-policy.md and terms-of-service.md but no LICENSE file. That is a real gap for anyone evaluating the source, and it is worth checking before you assume any particular reuse rights.

DevHub Versus a CLI Toolchain or a Browser Bookmark Folder

The realistic alternative is not another GUI toolbox; it is the combination most developers already have: browser bookmarks to converter sites, plus a handful of CLI tools. The difference in approach is architectural. A CLI tool reads from stdin and writes to stdout, so it composes: you can chain a JSON formatter into a diff, or hash a file inside a shell loop. DevHub is a windowed application with a URL Scheme and no documented pipe interface, so composition stops at the clipboard.

The other alternative is editor extensions. If your editor already formats JSON, decodes Base64 and previews JWT claims, adding a separate application duplicates that surface. The counter-argument is the one the README makes: the utilities that do not belong in an editor, such as QR code generation, EXIF viewing, image watermarking, chmod calculation and device information, are exactly the ones that push you to a browser today. DevHub's case is strongest for that second category and weakest for anything an editor already handles well.

For the privacy-sensitive subset, the comparison is starker. Pasting a production JWT or an RSA private key into a website is a genuine risk. A local app removes that risk without asking you to trust a server. The README's offline-first framing is the whole argument, and it is a good one for that specific class of task.

Maintenance Cadence, Licence and Upgrade Cost

The repository is not archived, and the last push was on 2026-04-21. That is recent enough to suggest the project is still being worked on, but the README's stated ambition of weekly releases is a goal, not a guarantee, and the release history shows a slower rhythm: v2.1.0 on 2025-11-04, v2.1.1 on 2025-11-11, and v2.2.0 on 2026-01-06. Between the January release and the April push there is no release tag in the repository, so anyone depending on a steady cadence should watch the releases page rather than the README's aspiration.

Upgrade cost is low by design. The app is distributed through the App Store, so updates arrive through the standard macOS mechanism, and there is no self-hosted server, database or config file to migrate. The risk of an upgrade breaking a workflow is limited to UI changes and any behaviour change in the URL Scheme, which is the one integration point that could affect automation.

The licence is the unresolved item. The repository has no LICENSE file among its top-level entries, and the README does not name a licence. The presence of privacy-policy.md and terms-of-service.md suggests the distribution terms live with the App Store listing rather than in the repository. If you intend to read, fork or redistribute the Swift source, confirm the terms first; nothing in the repository grants those rights, and this is not a question to settle by assumption.

Editorial conclusion

Adopt DevHub if you work on macOS 14 or newer and lose time to browser-based converters, or if you want a local JWT, hash and QR code tool that does not send your data to a third-party site. Skip it if you are on Windows or Linux, or if your workflow already lives inside a single editor with equivalent extensions. Before relying on it, check the App Store listing for the current price, since the README does not state whether the app is free, and confirm the URL Scheme format from the app itself before wiring it into Raycast.

Frequently asked questions

Official sources

1. Issues
2. jaywcjlove/DevHub on GitHub
3. Project website
4. README
5. Releases