Influxx and Ocsidian are both staying Apple exclusive going forward — but the reasons for saying so out loud are different for each. Influxx has been macOS- and iOS-native since its last release, so confirming where it's headed is mostly a formality. Ocsidian is the real news here: the agentic game creation platform has shipped on both macOS and Windows since it launched, and starting with this announcement, ETAPX is narrowing Ocsidian's development to Apple platforms only. Windows installs of Ocsidian Os will keep running, but they will not receive new releases going forward. That's a real change to a real product, and we're not going to announce it quietly.
Influxx and Ocsidian Are Staying Apple Exclusive
Let's start with the plain statement, because everything else in this piece is just explaining it. Influxx, ETAPX's agentic environment, and Ocsidian, ETAPX's agentic game creation platform, are both committing to the Apple ecosystem exclusively — macOS and iOS for Influxx, macOS for Ocsidian Os. Neither product is being built out for Windows or Android going forward. For Influxx, that's a confirmation of a direction it was already on. For Ocsidian, it's a new decision, and most of this article is about being straight with you on that distinction rather than blurring the two together.
Influxx's move to native macOS and iOS apps made the browser an option rather than the only option, and that release never touched Windows or Android — Influxx has been an Apple-platform product in practice since then, full stop. What's new is Ocsidian committing to the same lane. Ocsidian Os, the desktop editor built on the BlackFrost Engine, has been available on macOS and Windows since the platform launched. Starting now, ETAPX is narrowing where Ocsidian Os goes next: new features, engine updates, and new releases will target macOS only.
The rest of this piece walks through that decision properly rather than leaving it as a headline. We'll cover exactly what's changing for Ocsidian and why the Windows version isn't simply being frozen quietly in place, the reasoning ETAPX's engineering leadership is standing behind in public, what it actually means if you're a creator with projects open right now, and why this is a statement about two specific products rather than a new company-wide stance on Apple. We'd rather over-explain a hard decision than let people fill in the gaps themselves.
The Real News: Ocsidian's Windows Chapter Is Closing
We want to be exact about what's changing, because vague language is how companies quietly walk back commitments without ever admitting they made one. When ETAPX introduced Ocsidian, we described Ocsidian Os as "a native, Electron-based desktop editor that ships as a standalone application for both macOS and Windows." That sentence was true then, and it's still technically true today — the Windows build exists, it works, and nothing about it breaks the moment this article publishes. What changes is what happens next. ETAPX is not going to keep building two versions of Ocsidian Os in parallel. From here forward, development narrows to macOS.
What We Said At Launch, and What's True Now
Ocsidian launched on the strength of being available wherever creators already were, and Windows was a real part of that pitch, not an afterthought bolted on for coverage. Solo creators and small studios running Windows machines picked up Ocsidian Os expecting it to keep pace with macOS, because that's what ETAPX told them it would do. Nothing about that history is being rewritten here. Ocsidian has run on Windows since it launched, and it ran there because ETAPX built and maintained a genuine Windows version, not a token one kept alive for a bullet point.
What's different now is the decision about where to point future engineering effort. That's a forward-looking call, not a retroactive one, and John Ridge, ETAPX's CTO — who built Podz, the workspace layer inside Influxx, before stepping into the CTO role — is the person who pushed hardest for it internally.
"I don't want anyone reading this to think Windows was always the plan B, because it wasn't. We built a real Windows editor, and people built real games on it. This isn't us pretending that didn't happen. It's us deciding that going forward, we'd rather build one exceptional version of Ocsidian Os than two versions that are each a little worse than they could be. That's a genuine change in direction, and I'd rather say that plainly than dress it up as something that was true all along."
— John Ridge, CTO, ETAPX
Why Now — The Reasoning Behind Going All-In on Apple
None of this is happening because Windows failed Ocsidian, or because of some abstract brand alignment exercise. The reasoning is specific to what Influxx and Ocsidian actually are — resource-heavy, real-time, agentic tools — and to what ETAPX has learned building both of them at once. There are three separate arguments underneath the decision, and they reinforce each other rather than standing alone: integration depth, hardware fit, and engineering focus. Taken individually, any one of them might be an argument for doing better on two platforms instead of committing to one. Taken together, ETAPX's engineering leadership decided they added up to a clear answer.
One Ecosystem, Deeper Integration
Influxx's native macOS and iOS apps only became possible once ETAPX stopped treating "the app" as something that also had to work identically inside a browser tab on whatever operating system a visitor happened to have. Committing to one ecosystem let the team build background task execution, real system notifications, and a desktop bridge that behaves like part of the operating system instead of a guest inside it. Ridge argues Ocsidian is in the same position, and has been for longer than most people realize.
"Every deep integration we've shipped for Influxx — background execution that survives closing the app, notifications that come from the system instead of a page, a desktop bridge that hands a session between web and native without you noticing — came from narrowing our target instead of widening it. Ocsidian's editor is talking to a real-time engine, live physics, and a full rendering pipeline in the same window you're editing in. Splitting that attention across two operating systems means neither one gets the depth of integration it deserves. One ecosystem means we can go deeper instead of staying even."
— John Ridge, CTO, ETAPX
Apple Silicon and the Kind of Work Both Tools Do
Influxx and Ocsidian both spend most of their time doing things that are unusually demanding on consumer hardware — Influxx running agentic tasks that lean on sustained background compute, Ocsidian driving a real-time 3D engine with live physics and a full rendering pipeline in the same window you're composing a scene in. Both benefit from hardware with a consistent, well-understood performance profile instead of a wide spread of configurations to account for. Apple Silicon's performance characteristics are already the foundation under Influxx for macOS, and that's the same reasoning ETAPX is now applying to Ocsidian Os going forward. Building against one hardware generation's known behavior, rather than an open-ended and constantly shifting range of Windows configurations, is a meaningful part of what let Ocsidian's live preview stay tight during editing in the first place. Committing fully to that hardware line is a continuation of a bet ETAPX already made, not a new one.
A Smaller Surface, A Faster Pace
The least glamorous reason is also the most honest one: engineering time is finite, and every hour spent keeping a second platform at parity is an hour not spent making the primary one better. Ridge is direct about this trade-off internally. Supporting Windows and macOS at genuine parity meant every new feature, every engine improvement, and every editor refinement had to be built, tested, and shipped twice — or shipped once and quietly left to drift on whichever platform got less attention that month. Narrowing to a single platform doesn't reduce the amount of work ETAPX is willing to do. It reduces the number of places that work has to be duplicated, which shows up less as a single dramatic change and more as a release cadence that simply gets faster, and a lot fewer platform-specific bugs, over the months that follow. It's a slow, compounding kind of benefit rather than a single obvious one, which is exactly why it's easy to underrate next to something more visible like a new feature — but it's the difference between an editor team that ships confidently every few weeks and one that's perpetually catching up on two fronts at once.
What This Means If You're Building on Ocsidian Today
Strategy is easy to state and hard to feel the effects of unless someone spells out what actually changes for the person sitting in the editor right now. Here's the direct version:
- Existing Windows installs: keep working. Nothing is being remotely disabled, and nothing about your current setup breaks the day this article goes live.
- New releases: ship for macOS only from here forward. New features, engine updates, and fixes land there first, and only there.
- Your projects: unaffected as projects. Your TypeScript scripts, materials, physics setups, and templates are the same files either way — they simply no longer have an actively maintained home on Windows.
- What you build and export: this is a decision about the platform the editor runs on, not a new restriction on where the games you make are allowed to reach players.
- If Windows is your only machine: the honest answer is that staying current with Ocsidian going forward means having access to a Mac. We'd rather tell you that directly now than let you find out three releases from now that you've quietly fallen behind.
That last point is the one ETAPX expects to hear about the most, and it should be. Telling working creators that the platform they built on is no longer where the product is headed isn't a footnote. For anyone running Windows today, it's the headline of this announcement, and treating it as a minor detail would be its own kind of dishonesty.
This Is a Decision About Tools, Not a Company-Wide Apple Bet
It would be easy to read this announcement and assume ETAPX has decided to become an Apple-only company across the board. That's not what's happening, and it's worth being explicit about the difference so nobody spends the next month worrying about a product this doesn't touch.
Whistlr, ETAPX's social platform, is built on the opposite philosophy on purpose. Whistlr's whole strategy is maximum reach — it runs on a Windows desktop app, and Whistlr Go exists specifically to keep the platform usable on lower-end Android devices, not just flagship hardware. None of that changes here. Whistlr isn't mentioned anywhere in the reasoning behind today's announcement because Whistlr isn't affected by it in any way. It's a different product, built for a different audience, aimed at a different goal.
AJ, ETAPX's founder and CEO, draws the line between the two parts of the company plainly.
"We have two different jobs happening under one roof, and they call for opposite instincts. Whistlr's job is reach — it needs to run well on whatever device someone actually has, including the lower-end Android phones a huge number of people are using, because showing up there is the whole point of that product. Influxx and Ocsidian have a different job. They're focused tools for people doing demanding, real-time, resource-heavy work, and for that job, depth of integration matters more than breadth of devices. Going all-in on Apple for those two products isn't ETAPX picking a side company-wide. It's us being honest that a reach product and a focused creative tool shouldn't be built by the same playbook."
— AJ, Founder & CEO, ETAPX
Put simply: if you use Whistlr, nothing here touches you, on any device, today or after this announcement. This is specifically about Influxx and Ocsidian, ETAPX's creative and agentic tools — not a statement about the company as a whole.
The Trade-off We're Not Going to Spin
It would be simple to end this piece on the upside — deeper integration, a hardware line built for the work, a faster release pace — and let that stand as the whole story. That would also be a little dishonest. Narrowing Ocsidian to Apple platforms is going to disappoint people who chose Ocsidian specifically because it ran on the machine they already owned. Some of those people don't have a Mac, aren't in a position to get one soon, and are going to feel this decision as a door closing rather than a strategy sharpening.
Ridge doesn't pretend that cost isn't real.
"I've spent enough time around Ocsidian's community to know exactly who this lands hardest on — creators who picked Windows because it's what they had, not because it was a lesser choice. I'm not going to sit here and tell them this is secretly good news for them, because for a Windows-only creator, it isn't. What I can tell them is that we're not doing this to chase a trend or cut corners. We're doing it because we believe a smaller, more focused Ocsidian ends up being a better Ocsidian, and we'd rather build that thing well than keep building a wider thing that's stretched thin across two platforms. That's a real trade-off. We're making it with our eyes open, not pretending it doesn't cost anyone anything."
— John Ridge, CTO, ETAPX
That's the whole trade-off, stated once and not softened: a smaller platform footprint in exchange for a more focused, more deeply integrated product. Some current users benefit from this immediately. Some current users lose something they were actively relying on. ETAPX is betting that the first group is where Ocsidian's future is best built, without pretending the second group doesn't exist or doesn't matter.
Frequently Asked Questions
Does this mean Ocsidian is dropping Windows support?
Yes, going forward. Existing Windows installs of Ocsidian Os will keep running, and this announcement doesn't disable anything you already have installed or lock you out of projects you've already built. But new releases, features, and fixes will target macOS only from this point on — Ocsidian isn't getting new Windows builds after today, and there's no future date at which that changes. We'd rather say that directly, once, than leave it ambiguous and make people ask the same question every few months.
Is Influxx also Apple exclusive?
Yes, and this isn't new — Influxx has been macOS- and iOS-native since its last release, with no Windows or Android version ever shipped or announced for it. This piece confirms Influxx's path forward stays on Apple platforms; the new decision here is specifically about Ocsidian joining it, not about Influxx changing course.
Will my existing Ocsidian projects and files still open on Windows?
Your existing Windows installation will continue to open your existing projects — scripts, materials, physics setups, templates, and everything else you've already built. What you won't get on Windows going forward is new engine updates, new editor features, or fixes for anything that comes up after this announcement. If you want to stay on the version currently maintained, that means working from macOS.
Does this affect Whistlr or any other ETAPX product?
No. This announcement is specific to Influxx and Ocsidian, ETAPX's creative and agentic tools. Whistlr's strategy is the opposite by design — maximum reach, including a Windows desktop app and Whistlr Go for lower-end Android devices — and none of that changes because of this decision. There is no company-wide Apple mandate hiding behind this announcement.
Why is ETAPX narrowing Ocsidian to Apple instead of keeping both platforms?
Three reasons, in ETAPX's own words: going all-in on one ecosystem allows for deeper integration than splitting attention across two ever could; Apple Silicon's consistent performance profile suits the real-time, resource-heavy work both Influxx and Ocsidian do; and a smaller engineering surface means faster, more polished releases instead of two platforms each getting a diluted share of attention. It's a deliberate bet on depth over breadth, made with a clear-eyed view of who it disappoints — and it's why both products are staying Apple exclusive going forward.
Influxx was always going to end up as an Apple-platform product; Ocsidian choosing to become one is the actual news in this announcement, and ETAPX would rather you hear the reasoning and the cost of that choice in plain language than piece it together from a changelog. The bet is that a narrower, more integrated Ocsidian is a better Ocsidian. The cost is that some creators who built on Windows are going to need a Mac to keep building with it going forward. Both of those things are true at once, and this is ETAPX saying so directly.
