DEV Community: Martin Grüner

Keeping 3D device-frame perspective editable through native export

Martin Grüner — Wed, 19 Aug 2026 16:43:21 +0000

A device frame can explain what kind of app is being shown, but a flat mockup often sits on top of the composition instead of belonging to it. In Screen Studio Kit 1.2, I added controlled depth without flattening the frame into a finished bitmap.

Device-frame layers now store independent Turn and Tilt angles. The hardware body, screen content, finish, shadows, and perspective remain connected to the same editable layer. Both angles are constrained from -60° to 60°, and the canvas updates immediately while the frame is edited.

The detail that mattered most was export parity. The interactive canvas is not the final renderer, so the native export engine consumes the same stored angles. Existing projects migrate with zero-degree values, preserving their previous appearance until a frame is deliberately changed. Perspective is scene data, not a preview-only effect.

This also needs restraint. Screen Studio Kit warns when a rotated custom iPhone frame is used for an App Store output so the artwork can be checked against Apple’s current requirements. The same reusable project can keep a 3D treatment for another store or campaign and reset the App Store version.

The complete editor, local projects, asset management, preview, validation, device-frame editing, one size and one language per export, and up to 10 full-resolution exports per local day are in the Free tier.

The release notes show the real editor and exported artwork: https://martingruner.com/blog/screen-studio-kit-1-2

A diff tool should fail honestly when the input gets difficult

Martin Grüner — Wed, 19 Aug 2026 16:24:29 +0000

Diff Anything 1.2 is a quality release in the literal sense: the same files produce more faithful results, difficult inputs fail more honestly, and every route into a comparison follows the same rules.

The visible change is a broader Free tier. The desktop app can now preview YAML, XML, CSV, environment files, HTTP responses, API schemas, folders, archives, PDF and Office documents, images, and binary files. Free previews are explicitly bounded: files up to 5 MiB per side, 10 new sessions per local day, the first 100 collection items, and the first 3 PDF page previews. The Free CLI remains focused on text and JSON.

The less visible work is in awkward inputs. Structured comparison now handles cases such as duplicate keys, repeated CSV keys, repeated HTTP headers, YAML multi-documents, XML namespace meaning, and masked environment values with explicit warnings when a result cannot be represented without ambiguity. Image comparison handles transparency and decoded-size budgets more carefully. PDF and Office handling keeps extracted text and rendered evidence distinct.

Everything stays local: there is no account, cloud comparison service, analytics, or telemetry. The point is not to claim that one engine can perfectly understand every format. It is to select a bounded specialist engine, show its limits, and keep desktop, CLI, Git, and CI behavior aligned.

The full release notes include the exact boundaries and screenshots: https://martingruner.com/blog/diff-anything-1-2

What a Windows developer workspace should remember between context switches

Martin Grüner — Wed, 19 Aug 2026 16:23:48 +0000

I built DevDock because reopening a codebase is not the same as recovering the context needed to work on it. A product may span several folders, and the useful state is scattered across commands, Docker, Git, databases, project health, and the checks I want to run before release.

DevDock is my attempt to keep that context in one local Windows workspace. Each registered project gets an overview, saved commands, run history, Docker and Git state, database operations, local security findings, settings, and tools. A Today view keeps recent projects and saved daily workflows close when I switch between products.

The important boundary is that it is a local tool. It does not upload source code. The security audit checks registered folders for exposed secrets, private keys, tracked credential files, unsafe permissions, escaping symlinks, and missing lockfiles, while withholding matched secret values. Database tools are deliberately bounded around schema inspection, constrained record lookups, migration review, diagnostics, and confirmed backup operations.

The Free tier supports up to three local projects with core commands, Git, Docker, Project Doctor, and security audits. Pro is a one-time purchase for unlimited and multi-folder projects, custom workflows, complete history and insights, database tools, SSH transfers, and configuration backup and restore.

I would especially value feedback from developers who work across several local repositories: which piece of context costs you the most time when you return to a project?

https://martingruner.com/projects/devdock