SoloSnap’s AppCore engine was built around a simple idea: make screen recording with application audio feel clean, predictable, and Mac-friendly.

Until now, AppCore has focused on full system audio capture. That means SoloSnap records the screen while capturing the audio your Mac is playing through the selected audio route. It is simple, direct, and easy to understand. For many users, that is exactly what they need.

Later this week, AppCore is planned to grow with a new advanced option: per-app audio.

This does not replace full system audio. It expands AppCore by giving users another way to record audio when they need more control.

New Audio Choice: Full System Audio or Per-App Audio

AppCore now has two clear audio paths.

Full system audio is the straightforward option. It is designed for users who want to record what they hear from their Mac without building a custom routing setup. If you are recording a walkthrough, a presentation, a browser session, a video, or general Mac activity, full system audio keeps the experience simple.

Per-app audio is the advanced option planned for later this week. It is designed for users who want more control over which application audio is captured. Instead of treating all Mac audio as one shared source, per-app audio allows users to build a more intentional recording flow around specific apps.

The goal is not to make AppCore complicated. The goal is to let users choose the level of control that matches what they are trying to record.

New Advanced Workflow: Per-App Audio Capture

Per-app audio is for creators, developers, gamers, educators, support teams, and power users who need cleaner audio separation.

A common example is recording one app while keeping other apps out of the recording. Maybe you want to capture a game, a browser, a video app, a meeting app, or a specific creative tool. With per-app audio, the recording setup can be built around that intentional source instead of everything happening on the Mac.

This is especially useful when users want to avoid unwanted notification sounds, background audio, or unrelated apps being captured in the final recording.

Per-app audio gives AppCore a more professional workflow without forcing every user into that workflow.

New Simplicity Rule: Full System Audio Stays Easy

Full system audio still matters.

Not every user wants to configure routing. Not every recording needs advanced isolation. Sometimes the best experience is just selecting AppCore, choosing the screen capture setup, enabling application audio, and recording.

That is why full system audio remains the familiar path.

It is the everyday mode. It is approachable. It is fast. It works for normal screen recordings where capturing the Mac’s audio output as a whole is perfectly fine.

AppCore’s new direction is not about making the simple path less simple. It is about adding a second path for users who need more.

New Power User Option: More Control Without a Mixer UI

Per-app audio is powerful, but SoloSnap does not need to become a dense audio mixer.

That distinction matters.

SoloSnap is still a screen recording app, not a full digital audio workstation. AppCore’s job is to make audio capture understandable inside a recording workflow. The interface should help users choose the right audio path, confirm their setup, and start recording without feeling buried under professional audio controls.

The advanced behavior belongs in the workflow. The interface should stay calm.

That means per-app audio should be presented as an optional advanced capability, not as the default experience every user must understand before they can record.

New Routing Flexibility: Built for Real Recording Setups

Per-app audio works best when users understand that audio routing is part of the setup.

Some users may use virtual audio devices. Some users may use tools like BlackHole, Soundflower, Loopback-style routing, or other audio routing setups. These tools can help isolate audio from specific applications and send that audio into SoloSnap’s AppCore recording path.

SoloSnap’s role is to make that capture path useful and understandable.

For advanced users, this means AppCore can become part of a much cleaner recording chain. For everyday users, full system audio remains available without requiring them to learn routing first.

That balance is the point.

New Creator Use Case: Cleaner Game and App Recordings

Per-app audio is especially useful for creators who want cleaner recordings.

A user might want to record a game while keeping music, messages, browser audio, or other apps out of the capture. Another user might want to record a tutorial in one app while avoiding random system sounds. Someone making support videos may want the final recording to contain only the relevant application audio.

This is where per-app audio makes AppCore feel more precise.

It gives creators more control over the final output without forcing them to fix unwanted sounds after the recording is already done.

New Microphone Awareness: Headphones Still Matter

Per-app audio can help isolate application audio, but microphone behavior is still real-world behavior.

If a user records their microphone while playing audio through speakers, the microphone may still pick up that sound from the room. That is not an AppCore failure. That is simply how microphones work.

For the cleanest results, users who record both microphone and app audio should usually wear headphones. That keeps app audio from bleeding back into the microphone track.

This is an important part of helping users understand professional capture habits without making the feature feel scary.

The message is simple: per-app audio gives you control over the app audio path, and headphones help keep your microphone clean.

New AppCore Identity: Simple When You Need It, Advanced When You Want It

This update gives AppCore a clearer identity.

AppCore is no longer just the engine for recording screen plus application audio. It becomes the engine that can support both quick everyday captures and more intentional audio workflows.

Full system audio is for speed.

Per-app audio is for precision.

Both belong in AppCore because both serve the same purpose: helping users record their Mac with the audio they actually want.

The difference is how much control the user needs.

New Fairness for Advanced Users

Per-app audio deserves to be explained fairly.

It should not be presented as something only experts can touch. It is advanced, but it is not off-limits. Anyone can use it if they are willing to set up the right audio path and understand what they are capturing.

That is the friendly way to frame it.

Per-app audio is for users who want more control. It may require a little more setup than full system audio, but the reward is a cleaner, more focused recording.

That makes it a feature with real value, not just a technical checkbox.

AppCore Is Growing Up

SoloSnap is adding more control to Mac screen recording without losing the simplicity that made AppCore useful in the first place.

Full system audio remains the easy option for everyday recording.

Per-app audio is planned for later this week, giving AppCore a more advanced path for users who want cleaner, more focused audio capture from specific apps.

Together, these two audio paths make AppCore more flexible, more creator-friendly, and more capable.

SoloSnap is still designed to feel native, focused, and practical. This update simply gives users more choice over one of the most important parts of any screen recording: the sound.