David Singleton and Hugo Barra spent years building the Android ecosystem — the developer tools, the distribution, the business models that made an operating system into a platform. Now they're trying to do it again for AI agents, and this time Meta is buying the ticket.
Dreamer, the consumer agent operating system Singleton co-founded with Barra and Nicholas Jitkoff, announced March 23 that its full team has joined Meta Superintelligence Labs under Chief AI Officer Alexandr Wang. The deal, which the company described as technology licensing plus talent rather than a pure acqui-hire, gives Meta access to a platform that was still in open beta as of February 2026 — roughly five weeks before the announcement. as first reported by Silicon Angle
The three co-founders bring deep Play Store credentials: Singleton was CTO at Stripe but previously VP of Engineering at Google overseeing Android development; Barra led product management for the Android OS at Google before building Xiaomi's global smartphone business and later Meta's VR products; Jitkoff was a principal designer on Material Design and later led design at Figma. according to CapitalG's investment announcement. A fourth name appears in that same CapitalG post — Ficus Kirkpatrick, listed as a co-founder and described as a creator of the Danger Hiptop (the original T-Mobile Sidekick), an original Android team engineer, and the engineering leader who built Google Play into a multibillion-dollar business. Meta's announcement made no mention of Kirkpatrick. The discrepancy is unresolved; Kirkpatrick did not respond to a request for comment.
Dreamer raised $56 million in seed funding at a $500 million valuation in November 2024, co-led by Index Ventures and CapitalG, Alphabet's growth investment fund. Angel investors included Andrej Karpathy, Alexandr Wang, Andy Rubin, Dave Burke, and product designer Soleio — a roster that reads like a who's who of platform-builders. per CapitalG and Silicon Angle
The product architecture is where it gets interesting for builders. Dreamer's core concept — which Singleton articulated in a final interview with Latent Space before the Meta announcement — positions a component called Sidekick as the kernel of a personal agent system, with agents themselves treated as users. Agents run in isolated VMs and expose functionality through MCP tool servers, the Model Context Protocol standard that has become the dominant integration layer for agent-tool interaction. A news agent can recruit a read-it-later agent, which generates an audio summary, which posts to Slack — without anyone pre-designing that chain. as demonstrated in the Latent Space interview
This is the architecture that matters, not the app gallery or the consumer UI. The question for developers is whether the MCP-based tool model translates into a real ecosystem — one where tool builders can get paid per usage, as Dreamer announced it was piloting. Singleton compared the moment to the early web: multiple protocols competing, none dominant, HTTP and HTML eventually winning but other approaches entirely viable at the time. in the Latent Space interview
The platform war frame is what Sonny flagged and it holds up. Meta projects $115 to $135 billion in capital expenditures for 2026, following $72 billion in fiscal 2025 — a scale of infrastructure investment without obvious parallel in the consumer internet. according to WinBuzzer. Dreamer brings a consumer-grade agent OS built by people who understand distribution, developer ecosystems, and the network effects that make platforms valuable. Whether Meta is acquiring a platform or just acquiring the team that knows how to build one is the unresolved question — and it matters enormously for what gets built on top.
The open beta was live for approximately five weeks before the Meta announcement. The Builders in Residence program and $10,000 prize for the best new platform tool by mid-April were announced in that same window. as described in the Latent Space interview The timing raises a question the announcement didn't answer: does Dreamer's tool marketplace and per-usage payment model survive the transition to Meta's infrastructure, or does it become collateral damage in the integration?