DogSC records the screen on macOS and edits it without leaving the app

Recording covers the sources you actually have

The feature table is organised as six pairs, and the recording column is the first one. You can record a display, a window, a region, or an iPhone or iPad connected by a data cable, and you can record the camera, the microphone and system sound at the same time. That last point is what makes it usable for tutorials rather than only for screen demonstrations, because the narration and the application audio arrive in the same take and therefore the same timeline. Capturing a tethered iPhone is an unusual and useful choice, since a phone screen is a common subject and the alternative is a second camera pointed at a second device. The app is a native macOS build rather than a browser page, which matters for two reasons, since a browser tab cannot capture other windows and cannot easily capture system audio without a virtual device. The project is written in Swift with a Package.swift and a Package.resolved, and the repository carries Sources/ for the code, Resources/ for the assets and a build-app.sh script.

Editing that stays lightweight

The editing column lists the operations: split, trim, reorder, speed change and restore of an edit, with thumbnails and waveforms switchable at any time and edges that snap automatically. The scope is worth reading carefully. There is no timeline with arbitrary keyframes, no compositing of separate clips and no colour correction beyond what the picture column describes. What it offers is the set of operations that a screen recording actually needs, where the recording is long and mostly static and the problem is removing the wait, the mistake and the part where you opened the wrong window. The automatic edge snapping matters more than it sounds, because trimming a clip without snapping leaves a one frame gap and you end up re-cutting the same edit. The restore of an edit, listed as one of the operations alongside the others, means a destructive change can be undone, which is the difference between an editor you experiment in and one you are careful in.

Camera moves and framing are the differentiators

The third column is where this app differs from a plain recorder. There is automatic following of the cursor and manual zoom, the tilt, perspective and focus blur of a 3D screen effect, and an opening animation. The fourth column covers the picture side: aspect ratio, cropping, padding, rounded corners, shadow, background and device mockup frames, plus overlay, softening and highlighting, with scene presets. Together these are the features that turn a screen recording into something you would publish, and they are all in the app rather than in a post-production tool. The mouse and camera column adds cursor styling, click feedback, hiding the cursor when idle, and time calibration, plus camera layout and entrance animation, which are the details that separate a tutorial recording from a demo recording. The editor screenshot in the README shows a preview pane, background settings and a multi-track timeline, and the motion screenshot shows zoom focus, curves and timeline segments, so the camera move is a timeline object rather than a single effect applied at export.

Export options, and the project stays editable

The export column specifies the formats, MP4 or M4A, the resolutions, the source resolution, 1080p, 1440p or 4K, and the frame rates, 30 or 60 fps. The last detail in that list is the one that sets the app apart from a recorder that renders on stop. The project can continue to be edited at any time, which means the recording is a project rather than a finished file, and the export is a render of that project. That is why the editor carries a multi-track timeline with a preview, background settings and effect segments, and why copying an effect segment on the timeline with the standard copy and paste commands works while a separate paste operation applies only its properties. The tips section adds a few practical notes, among them that pressing a modifier combination during recording leaves an edit marker you can find later on the timeline, and that a floating notes window can serve as a teleprompter because it is not recorded into the frame.

Building from source, and the signing situation

The source build needs an Apple Silicon Mac, Xcode 26 or newer and your own Apple Development certificate, and the sequence is short:

git clone https://github.com/laogou717/dogsc.git
cd dogsc

You then find the 40 character SHA-1 fingerprint of your own identity with the security find-identity command, pass it to the build script through the DOGSC_SIGNING_IDENTITY environment variable, and open the resulting app from the .build/local directory. The script does the Release compilation, assembles the icons, fonts, localisation and Sparkle, and signs the whole app, and a plain swift build will not produce an .app bundle. There is also a development build, DogSC Dev with the identifier cn.laogou.dogsc.dev, whose preferences and system permissions are independent of the release build and which does not receive release updates. If Xcode is not in Applications you point at it with DEVELOPER_DIR, and the first build needs network access to download Sparkle.

Permissions, notarisation and where the licence stops

Three practical points sit in the getting started and licence sections. The permissions are granted through a guided setup, with screen recording and accessibility requested and the microphone and camera authorised as needed, and the interface language switches in the settings and takes effect immediately. The current test build is signed with an Apple Development certificate and has not been through Apple notarisation, so if macOS blocks it on first launch you have to go to System Settings, Privacy and Security and choose to open it anyway, and the README asks that you download only from the repository releases. The licence is MIT for the source, and the bundled fonts follow their own terms with a separate note in the resources. The releases are frequent, with v0.1.8 on 2026-10-18, v0.1.7 on 2026-10-14 and v0.1.6 on 2026-10-13, and the app itself is described as a native macOS recorder and lightweight editor with a Simplified Chinese and English interface, requiring macOS 14 or later on Apple Silicon.

Editorial conclusion

Adopt DogSC if you record macOS screens for tutorials or demos and want the trim, camera move and export steps in one application rather than a separate editor. Do not adopt it for distribution to other users from the test builds, because the current builds use Apple Development signing and are not notarised, so they are blocked on first launch. Verify first that you are on macOS 14 or later with Apple Silicon, that you grant screen recording and accessibility permissions during setup, and that your own signing identity is available if you want to build from source, which also needs Xcode 26 or newer.

Frequently asked questions

Official sources

1. Issues
2. laogou717/dogsc on GitHub
3. License: MIT
4. README
5. Releases