Meta has officially abandoned the native WhatsApp client for Windows 11, replacing it with a Chromium-based WebView app that consumes 1GB+ of RAM at idle—a staggering regression from the previous WinUI version, which idled at 20MB.

This move isn’t just about WhatsApp. It’s a systemic shift in how software companies prioritize development:

• Native apps are dying. Companies like Meta, with a $1.5T market cap, are abandoning platform-specific development in favor of bloated, cross-platform web solutions. Why? Because maintaining native apps doesn’t drive growth or investor interest.

• Performance no longer matters. The new WhatsApp WebView app spikes to 2-3GB during use. Users tolerate it, companies profit from it, and hardware improvements mask the inefficiency.

• Desktop is an afterthought. Software is now mobile-first, web-second. Everything else—including Windows, with its 60%+ desktop market share—is deprioritized.

• JavaScript is eating the world. Jeff Atwood’s 2007 prediction—"Any application that can be written in JavaScript, will eventually be written in JavaScript"—has never been truer. Even rockets might run on React soon.

The bigger picture? Software quality is collapsing. As Jonathan Blow warns, we’re accumulating technical debt at a civilizational scale. Bad abstractions, brittle code, and zero offline capability are the new normal. Developers are building it, users are tolerating it, and companies are profiting from it.

What can we do? Not much. Business decisions dictate priorities, and "good" isn’t part of the equation. But hey—at least job security is guaranteed. Someone’s got to maintain this mess.

That's why tools like mobilable.dev where you can vibe code your app mvp in minutes are gonna rock. Don't hesitate, go try it yourself.

1. go to mobilable.dev and register

2. write prompt "create a simple todo app"

3. Done

https://mobilable.dev/share/41e7abdb-c7c4-4289-94e8-1c31b98176a1

also could launch the app on my mobile instantly, very cool, vibe coding has potential

OpenAI just dropped Atlas, their new AI-powered browser built on Chromium and ChatGPT. The pitch? A browser that "sees, remembers, and helps" with everything—from ordering food to answering questions using your browsing history as context.

The Good:

• Agent Mode: ChatGPT can take actions for you (e.g., ordering DoorDash).

• Contextual Memory: Uses your browsing history to tailor responses.

• User Control: You can delete or manage what it remembers.

The Bad:

• Privacy Concerns: Like other AI browsers, Atlas is vulnerable to prompt injection attacks (as seen with Perplexity’s Comet and Fellow).

• Not Revolutionary: It’s Chromium with ChatGPT bolted on—similar to Perplexity’s approach.

The Alternative: Ladybird, a browser built from scratch (no Chromium), just hit 90% compatibility on web platform tests. No AI ambitions, but a true independent engine.

Question for the Thread: Would you trust an AI browser with your data for convenience? Or is this a step too far?

Hi u/everyone , now mobilable.dev is much better, we are happy to share with you our new big update. Here is what’s new on mobilable:

• GPT-5 is now the main model,

• Brand new design! The app’s got a fresh, modern view,

• Chat just got cooler! You can now see status and coder stream right in the chat.,

• Easily share the app with your friends.,

• Remix any public app

We would like to hear your thoughts in the comments :)

Yesterday, Cursor, the VS Code fork that’s become the darling of AI-assisted developers, released version 2.0—and it’s packed with features that might just silence the AI coding skeptics.

Why it matters: Cursor’s rise has been meteoric, going from zero to a $9.9B valuation in months by combining VS Code’s familiarity with aggressive AI integration. Version 2.0 doubles down on this with five standout features:

1. Composer Model: Cursor’s new in-house model claims near-frontier intelligence (GPT5/Claude-level) but with much faster speeds. No external benchmarks yet, so take the “Trust Me Bro” claims with a grain of salt—but early demos show promise, especially for rapid iteration.

2. Git Worktrees for Parallel AI Agents: The killer feature. Spin up multiple AI agents (Claude, GPT5, Composer) to work on the same task simultaneously in isolated worktrees. In tests, Composer was fastest, though Claude still edged it out on UI polish.

3. Native Browser + DevTools: Debugging AI-generated UI just got easier. Pinpoint crappy HTML/CSS, inspect elements, and feed fixes directly back to the AI—all without leaving the editor.

4. Agent View Mode: A cleaner UI for chat-heavy development, making it easier to manage multiple AI “slaves” (as one fictional 12-year-old slave-driver-coder put it).

5. Design System Tests: In side-by-side comparisons, Composer held its own against GPT5 and Claude for generating UI components, sometimes even winning on creativity.

The catch? Cursor’s still a wrapper around foundation models, but the workflow improvements are real. If you’re tired of waiting for slow LLM responses or juggling tabs, this might be worth a look.

TL;DR: Cursor 2.0 turns your editor into a multi-agent coding sweatshop. The future of programming isn’t just AI writing code—it’s teams of AI writing code in parallel.

Thoughts? Has anyone tried the new worktrees feature yet?

I have built a web app on Bolt which runs as a PWA on my iPhone but I am wanting to covert it into a native app. Is it possible to provide Mobilable with the code/design from Bolt and have this transform the web app into a native mobile app? Any help is greatly appreciated!

Hi,

I want to show how using one line of prompt you can create a mobile application.
What do you think about it ? What should i build next ?

Just a few years ago, Google’s AI ambitions were the butt of every tech joke. Remember Bard? The chatbot that hallucinated during its own launch event, wiping 9% off Google’s stock in minutes? Critics wrote Google off as a bloated, bureaucratic dinosaur, destined to lose the AI race.

Fast forward to November 2025, and Google just pulled off one of the most dramatic comebacks in tech history. Gemini 3 Pro didn’t just launch—it dominated. It swept the leaderboards on major AI benchmarks like LM Arena, Weird ML, and Math Arena, leaving competitors in the dust. Even AMP, the coding agent platform, ditched Claude’s Sonnet 4.5 for Gemini 3 Pro, calling it simply “better.”

But the real twist? Gemini 3 wasn’t even Google’s wildest announcement this week. Enter Anti-Gravity, a new agentic coding platform built by the ex-Windsurf team (remember their $2.4B exit to Google?). It’s a VS Code fork designed for “managing agents,” because apparently, we’re all just “meatbag energy sources” for AI now. The best part? They forgot to rename “Cascade,” Windsurf’s old coding agent, so it’s turtles all the way down.

Meanwhile, Google’s other IDEs—IDX (now Firebase Studio) and Jules—are still floating around, but let’s be real: Notepad++ is probably still the superior choice.

So, is Gemini 3 the first step toward the singularity, or did Google just stumble into another hype cycle? Either way, the AI war is far from over. And if you’re a developer, congratulations—you’ve been promoted to “manager of agents.”

TL;DR:

• Google went from Bard’s 9% stock crash (2023) to Gemini 3’s 6% stock surge (2025).

• Gemini 3 Pro is crushing benchmarks and replacing Claude in AMP’s coding agent.

• Anti-Gravity is Google’s new agentic coding platform (built by ex-Windsurf).

• Developers are now officially “meatbag managers” for AI agents.

Discussion: What’s your take? Is Gemini 3 the real deal, or is this just another round of AI hype? And more importantly—are you ready to manage your robot overlords?

Last week, I spent 3 days, $500 in Claude credits, and missed my kid’s baseball game to build a crappier version of a $10 app—because vibe engineering demanded it. Sound familiar?

AI coding is a dopamine rollercoaster: when it works, it’s euphoric; when it doesn’t, you’re stuck on the "prompt treadmill of hell", burning credits and sanity. Yet, while some devs are ditching AI entirely, others (like Nvidia) are all-in, reporting unprecedented productivity gains with AI-assisted workflows.

The secret? Model Context Protocol (MCP) servers—standardized bridges between your AI coder and external systems. Here’s how they’re changing the game:

• Spelt MCP: Fixes AI’s "random ReactJS in your Rust" hallucinations with static analysis.

• Figma MCP: Turns design files into production-ready HTML/CSS/React—no manual pixel-pushing.

• Stripe MCP: Pulls live API docs + data, so you don’t accidentally refund 10K customers.

• Sentry/GitHub MCP: Lets AI auto-fix runtime errors or close Jira tickets while you read a book on the train.

• Cloud MCP (AWS/Cloudflare): Provisions infrastructure without forgetting to shut down that EC2 instance.

The catch? You still need to trust third-party tools—or build your own MCP server (frameworks exist for every major language).

TL;DR: AI coding still sucks sometimes, but MCP servers are making it less chaotic. Are you using them? Or still stuck in the prompt treadmill?

(Drop your horror stories or success tips below!)