April 2026: Pulling Collaboration Forward
June shifted AE CoCast from transport-layer stabilization into client-side refinement, application-sharing behavior, and broader real-world testing. In parallel, Apex Engine platform work continued across account management, authentication, launcher tooling, and shared infrastructure, while planning work around Apex HEL and the HeroEngine environment moved forward.
Several CoCast capabilities being developed during this period originated from collaboration functionality already planned for Apex Engine. Pulling that work forward into a focused standalone application allowed us to test and refine those systems independently while continuing development of the larger platform.
This log covers development activity through June 30, 2026.
AE CoCast Alpha
With the transport-layer stability milestone reached in May, June development moved toward the client experience and the practical behavior of simultaneous application and desktop sharing.
The goal remained simple: multiple participants should be able to share at the same time without presenter handoffs, while each broadcast remains independently available to other participants.
Application and Desktop Sharing
- Continued development of simultaneous multi-presenter sharing
- Expanded support for multiple active broadcasts within the same session
- Refined application-level capture behavior alongside full desktop sharing
- Continued work on maintaining independent broadcast panels so one participant starting or stopping a share does not interrupt another participant
- Added safeguards around application selection, including preventing minimized applications from being selected for sharing
- Continued testing of active application closure behavior and automatic cleanup of associated share panels
Client Interface Refinements
June also brought continued work on how active broadcasts are presented and managed within the client.
- Refined multi-panel layout behavior for concurrent broadcasts
- Continued work on focus and enlarged viewing modes for individual shares
- Improved visual separation between a participant's own broadcast controls and broadcasts being viewed from other participants
- Continued UI cleanup around session entry, active sharing, and session exit behavior
- Expanded testing of how panels respond when applications are closed, minimized, restored, or replaced during an active session
Real-World Testing
Testing continued across different hardware, network conditions, and user configurations rather than relying exclusively on development systems.
This included continued residential network testing and broader compatibility checks designed to identify problems that may not appear on newer development hardware.
The objective remains to keep CoCast lightweight enough to work across a broad range of systems while still supporting multiple simultaneous broadcasts.
From the Apex Engine Roadmap to CoCast
Several of the collaboration concepts being implemented in CoCast were originally planned as part of Apex Engine's broader real-time collaborative environment.
Apex Engine is designed around multiple developers working within the same environment, with collaboration, shared tools, versioning, server infrastructure, and communication integrated into the platform.
Rather than wait for the complete Apex Engine platform before testing selected collaboration capabilities, we pulled several of those concepts forward into CoCast.
That decision allows us to:
- Test collaboration behavior with real users much earlier
- Validate network and session architecture independently
- Refine multi-user interaction patterns outside the larger development environment
- Build reusable experience and infrastructure that can inform future Apex Engine collaboration tools
CoCast is therefore developing as its own product while remaining closely connected to the technical problems Apex Engine was already designed to solve.
Apex Engine Platform
Apex Engine development continued alongside CoCast throughout June.
AMS and User Account Core
- Continued development of the Account Management System backend
- Expanded account, user, and team data structures
- Continued work on the UAC foundation and associated authentication flows
- Began additional preparation for MFA integration
- Continued separation of shared account services from individual product-specific functions
The objective remains to provide a common account and access foundation that can support Apex Engine, Apex HEL, CoCast, and future services without requiring each product to recreate the same systems independently.
Launcher and Tooling
- Continued pre-alpha launcher development
- Expanded launcher-side account and product integration work
- Continued preparation for installation, update, and product-access workflows
- Refined communication between launcher services and the broader account infrastructure
Rendering and Development Tools
Parallel work also continued across several Apex Engine development systems.
- Continued shader and rendering development
- Additional Animation Editor testing
- Continued integration planning across development tools and shared platform services
- Continued server and backend preparation for future collaborative development environments
Apex HEL and HeroEngine
June also included continued planning around Apex HEL and the HeroEngine technology foundation.
Apex HEL is intended to provide a practical bridge between the existing HeroEngine technology and the broader Apex Engine ecosystem. That work includes more than the engine client itself. It also requires the surrounding systems needed to support accounts, subscriptions, deployment, hosted services, and future pilot access.
Work during this period included continued planning around:
- HeroEngine account and access integration
- Subscription and entitlement structure
- Hosted deployment and supporting services
- Alignment with the shared Apex Engine account infrastructure
- Preparation for future pilot availability
The goal is not simply to restore access to HeroEngine, but to place it within a modernized service and account environment that can continue evolving alongside Apex Engine.
Shared Infrastructure
June continued to reinforce the value of building common systems rather than isolated product stacks.
CoCast, Apex Engine, and Apex HEL increasingly share architectural requirements around:
- Authentication
- Account and team management
- Session services
- Cloud infrastructure
- Deployment
- Monitoring
- User access and entitlement
Building these systems as common infrastructure allows each product to move independently while still contributing to the same broader technical foundation.
Looking Ahead Into July
July will continue AE CoCast's transition from internal development toward broader practical testing and demonstration, with additional attention to application-sharing behavior, session usability, and multi-presenter workflows.
Apex Engine development will continue across its established platform roadmap, while Apex HEL work progresses around account, subscription, and service preparation.
As development continues, CoCast is also giving us an opportunity to validate collaboration concepts much earlier than originally planned.
What began as selected functionality pulled forward from the Apex Engine roadmap is becoming useful both as a standalone product and as a practical proving ground for the larger collaborative systems still ahead.
This is much closer to the May log structurally: intro, technical sections, bullets, platform update, shared infrastructure, looking ahead.
I would expect you to correct a fair bit of the June-specific chronology, especially which CoCast UI/application-sharing features were actually completed in June versus July. That is the part I would not want to invent from the later state of the product.