App Store structural remedy activity decelerates as enforcement shifts to port timelines
Every App Store commission argument reduces to a single number. A finding against the current anti-steering terms would make that number the subject of negotiation rather than of architecture.
Enforcement shifted from conduct monitoring to a burden-shifting frame, and the shift itself was the peak of activity. The Commission's choice to test anti-steering provisions against what is necessary rather than against what is permitted placed the burden of justification on the platform, which is the harder position to occupy. Since the investigation opened there has been no further milestone, and the twelve-month preliminary assessment window remains the next scheduled event.
- Formal investigation opened under DMA Article 6
- Necessity of anti-steering provisions is the stated test
- Preliminary assessment expected within twelve months
- Separate monitoring of browser engine compliance deadlines
All Signals (1)
Related Themes
Cluster Debate
The cluster contains one new milestone, the formal DMA Article 6 investigation, and no subsequent action. With a twelve-month preliminary assessment window and momentum declining since the opening, the correct model is a scheduled process, not an accelerating exposure.
- Formal investigation opened under DMA Article 6
- The stated test is whether anti-steering provisions restrict developer choice beyond what is necessary
- A preliminary assessment is expected within twelve months
- Separate browser engine compliance deadlines fall due in the following quarter
The opening was the peak and the quiet is the story. Enforcement moved from watching conduct to making Apple justify its terms, then went silent. Quiet in this docket means the Commission is drafting, and 'active dialogue' has been Apple's answer to four years of enforcement.
- Necessity framing places the burden of proof on the platform
- The twelve-month preliminary assessment window is the next scheduled event
- Apple's response contains no substantive commitment, only active dialogue
- A separate browser engine compliance deadline falls due the following quarter
- Enforcement has shifted to a burden-shifting test on anti-steering provisions
- The process runs on a regulatory calendar, not a company one
- No structural remedy has been imposed in this matter yet
Momentum declined because the next scheduled event is months away. Absence of activity is absence of activity, not a hidden timetable.
Enforcement peaking at the opening and then going silent is how these files age before they produce a number. The Commission chose the hard test before it opened the file.
- Preliminary assessment expected within twelve months
- Apple confirmed the probe and said it remains in active dialogue
The browser engine deadline producing a second action before the assessment window closes would indicate the Commission is pacing a broader file.
Nothing procedural. Every anti-steering argument reduces to the commission rate itself, and that number has not been touched. Watch the rate, not the calendar.
- Separate monitoring of browser engine compliance deadlines
- Anti-steering provisions under examination
This is the quietest cluster in the set, and both agents agree the activity has faded rather than resolved. The disagreement is whether the quiet is procedural or strategic. The unresolved item is the commission rate a remedy would ultimately write down, and the first enforcement step on the adjacent browser engine deadline will indicate whether the Commission is pacing itself or has deprioritized the platform file.