What DoomOff's built-in browser can actually see
DoomOff's built-in browser runs against the web pages it loads, the same standard web versions of YouTube, Instagram, TikTok, and the rest that you'd reach from any browser. It can read the page, hide elements on it, rewrite what loads, all before you see it rendered. That's the mechanism behind every toggle in this library: hide the Shorts shelf, remove the Explore grid, default a feed to Following.
What it cannot do is reach into a separate native app. Instagram's native app and DoomOff's browser are different processes, sandboxed from each other by design on both iOS and Android, and nothing, from DoomOff or anyone else, gets to cross that boundary.[1] A tool that claimed to modify the native Instagram app directly would be describing something neither platform permits.
Why that isn't a limitation of DoomOff specifically
This is true of every app on iOS and Android, not a gap in DoomOff's engineering. Apple's own documentation on Safari's content-blocking model, which DoomOff's optional Safari extension on iPhone relies on for the same reason, describes it as a deliberately narrow, declarative system: an extension hands Safari a set of rules, and Safari applies them to web content, with no equivalent path into a native app's rendering.[2] The narrowness is the design, on both the extension model and the app-sandboxing model behind it. It's also what keeps the fix from needing broad, invasive permissions to do its job.
Why the fix works anyway
YouTube, Instagram, TikTok, Facebook, Reddit, X, and LinkedIn all ship a full web version, not a stripped-down mobile placeholder. Feed, search, comments, messages, all of it works. That web version is a normal web page, which means it's exactly the kind of thing DoomOff's built-in browser can act on directly, no extension required.
So the fix isn't "get inside the native app." It's "make the web version, which DoomOff can already reach, the one you actually land on." That's the second half of the mechanism: on Android, an Accessibility permission that notices when a native app opens and reroutes it into the built-in browser; on iPhone, a guided Shortcut that does the same, or, if you'd rather, an optional Safari extension that applies the identical fix inside Safari instead.
What this means in practice
Nothing about your account changes, nothing gets installed inside Instagram or TikTok, and there's no server involved reading what you do. The entire fix lives in two places you already control: what DoomOff's browser shows you, and where the app icon actually sends you. That's a narrower claim than "blocks the app," and it's also the honest one.