Development Log: September 2026 - The Bug That Wasn’t
September focused on modernizing and cleaning up code across AE CoCast while continuing smaller feature refinements and preparing the application for Beta. Work also began around the next major networking milestone: transitioning from the current peer-to-peer architecture toward an SFU-based model designed to support larger sessions more efficiently.
In parallel, development continued across web infrastructure, server operations, deployment preparation, and the shared systems supporting CoCast, Apex Engine, and Apex HEL.
This log covers development activity through September 30, 2026.
AE CoCast: Preparing for Beta
As CoCast moves closer to Beta, September concentrated heavily on hardening the application rather than introducing large new feature sets.
That work included modernization of older prototype-era code, continued cleanup of client and transport behavior, smaller usability improvements, and preparation for the next stage of networking architecture.
Code Modernization and Cleanup
September included substantial ongoing cleanup across the CoCast codebase. As Alpha testing continued to expose edge cases and older implementation paths, portions of the application were simplified, standardized, and reorganized ahead of Beta.
Work included:
- Refactoring older prototype-era code
- Removing temporary development paths and redundant logic
- Standardizing newer session and sharing behavior
- Cleaning up client state handling
- Continued refinement of asynchronous client and transport behavior
- Preparing interfaces and transport abstractions for the upcoming SFU architecture
- Continued smaller bug fixes and usability refinements throughout the month
- Resolved a newly identified race-condition issue during Beta hardening and server rebuild testing
Much of this work is intentionally less visible than a new feature, but it is essential to reducing technical debt and improving reliability before broader testing begins.
Preparing for SFU
CoCast currently uses a peer-to-peer architecture, where participants connect directly to one another for media transport. This works well for smaller sessions, but the number of direct connections grows quickly as additional participants and broadcasts are added.
An SFU, or Selective Forwarding Unit, changes that model. Instead of every participant sending separate streams directly to every other participant, each stream is sent once to the SFU, which then forwards it to the participants who need it.
For CoCast, the upcoming SFU build provides a more scalable foundation for larger sessions while preserving the ability for multiple users to broadcast simultaneously.
September work included early preparation around the interfaces and transport structures needed to support that transition without disrupting the existing collaboration model.
Client and Session Refinements
Alongside code modernization, smaller client-facing improvements continued throughout the month.
Development and testing included:
- Continued refinement of application and desktop sharing behavior
- Additional cleanup around share-panel lifecycle
- Continued testing of session entry and exit behavior
- Improvements to automatic cleanup when an application share ends
- Continued refinement of reconnect and recovery behavior
- Testing around session closure and client shutdown
- Smaller interface and workflow improvements identified through real-world use
The objective remains to remove the kinds of edge cases that are acceptable during Alpha but become increasingly disruptive once more users begin relying on the application regularly.
Web and Product Infrastructure
September also included significant work on the web infrastructure supporting CoCast and the broader Apex ecosystem.
For CoCast, the website continued moving from a primarily informational presence toward something capable of supporting broader product use.
Work included:
- Continued development of the CoCast Explore experience
- Expansion of News and FAQ content
- Login and account interface improvements
- Mobile layout refinements
- General content and navigation cleanup
- Continued preparation for broader product onboarding and support
These updates are part of preparing CoCast not only as an application, but as a complete product experience.
Server Operations and Deployment Preparation
Server and deployment work continued alongside client development.
September included ongoing operational cleanup and preparation around:
- Server configuration and deployment processes
- Backup and recovery procedures
- Process and service cleanup
- Environment consistency
- Monitoring and operational readiness
- Code-signing preparation
- Marketplace-related deployment requirements
- Continued alignment between development and production environments
This work is particularly important as CoCast moves toward Beta, where deployment consistency and operational stability become as important as the application itself.
Apex Engine Platform
Apex Engine development continued in parallel, with attention remaining on the platform systems that support future collaborative development workflows.
Account and Access Infrastructure
Work continued across the Account Management System and related account services, including:
- Continued AMS development
- User and team management refinement
- Authentication and access-control work
- MFA preparation
- Product entitlement planning
- Continued separation of shared platform services from product-specific logic
- Additional work supporting future subscription and access workflows
These shared systems continue to support the broader Apex ecosystem rather than being developed independently for each product.
Apex Engine Web and Subscription Infrastructure
September also included continued work on the Apex Engine web experience and supporting subscription systems.
This included:
- Subscription and licensing page refinement
- Continued work on tabbed pricing and plan presentation
- Account and membership integration
- Founder-level access structure
- Invoice and subscription workflow improvements
- Continued preparation for future Apex Engine and Apex HEL pilot access
The goal remains to ensure that the systems surrounding the engine are ready as development moves toward broader availability.
Apex HEL and HeroEngine
Apex HEL work continued around preparing HeroEngine for integration into the modernized Apex ecosystem.
September activity included continued work and planning around:
- HeroEngine account and subscription access
- Founder-level participation structure
- Pilot preparation
- Hosted service support
- Integration with shared Apex account infrastructure
- Web and licensing updates
- Continued preparation of the surrounding systems required for future access
The work around Apex HEL remains focused not only on the engine itself, but on the account, service, and deployment infrastructure needed to support it properly.
Shared Infrastructure Across Products
September again demonstrated how much of the underlying work is shared across CoCast, Apex Engine, and Apex HEL.
The products serve different immediate purposes, but all depend on overlapping systems in areas such as:
- Authentication
- Account management
- Product access
- Subscription services
- Cloud infrastructure
- Deployment
- Monitoring
- Networking
- User onboarding
- Web services
Developing these systems as shared infrastructure allows progress in one product to support the others while still allowing each development track to move independently.
Looking Ahead Into October
October will continue CoCast Beta preparation, with additional code cleanup, testing, deployment work, and continued preparation for the upcoming SFU architecture.
Apex Engine development will continue across its existing platform roadmap, while Apex HEL work progresses around account, access, subscription, and pilot preparation.
September was not defined by one large feature release. Instead, it was a month of modernization, cleanup, infrastructure work, and preparation.
That work may be quieter from the outside, but it is exactly what is needed to move CoCast from Alpha toward Beta while continuing to strengthen the foundation shared across the broader Apex ecosystem.