Firebase Studio on iPad: What Works in 2026

Firebase Studio on an iPad is a half-answer: it opens in Safari because it is a browser app, but Google built it for a desktop browser and has not shipped real iPad support. The official Firebase Studio roadmap still lists "Better support for IDX running on iPads and Chromebooks" under the status "Future," and the whole product is scheduled to sunset on March 22, 2027. You can build mobile apps with Firebase Studio, but using the IDE itself from an iPad is the part that does not really work yet. If your goal is to actually code on a tablet, the honest answer is a native app plus a persistent cloud Linux box, which is what we build at Cosyra.

This guide separates the two questions people are actually asking, because conflating them is where most write-ups go wrong. One question is "can Firebase Studio build mobile apps?" — yes, it does Flutter, React Native, and Expo. The other is "can I sit on the couch with an iPad and use the Firebase Studio IDE?" — that is the gap. We cover what is shipped, what is only on the roadmap, what the 2027 sunset means for anyone learning it now, and the alternatives that run natively on an iPad today. For the Apple-specific agent-coding story see our Claude Code on iPad guide; for the head-to-head feature-by-feature read against the native-app alternative, our Cosyra vs Firebase Studio comparison covers pricing, sunset, and where each tool wins; and for the same browser-IDE-without-a-mobile-app pattern in other products see Gitpod on iPad (now Ona), Coder on iPad (whose official docs document the Safari PWA bugs on the same page as the install), and Cosyra vs GitHub Codespaces on mobile.

Can you use Firebase Studio on an iPad?

You can open Firebase Studio on an iPad, but you cannot meaningfully work in it the way you would on a laptop. It is a browser-only IDE built on Code OSS (the open core of VS Code) running inside a Google Cloud VM, with Gemini wired in. There is no native iOS, iPadOS, or Android app of any kind. Loading a full desktop IDE in iPad Safari gives you a cramped, touch-hostile surface: the file tree, command palette, and panels assume a mouse, a keyboard, and a wide window.

Google is candid about this in its own roadmap. The relevant line is:

"Better support for IDX running on iPads and Chromebooks" — status: Future.

Two things stand out. First, it is still called "IDX," the deprecated Project IDX name, which signals a low-priority legacy entry rather than active work. Second, the roadmap carries an explicit disclaimer that it is "not exhaustive, nor a guarantee we'll complete everything." Pair that with the sunset date below and the realistic read is that proper iPad support may never ship. We think that is the part most "Firebase Studio on iPad" posts bury, and burying it does the reader a disservice.

What actually works on a tablet today?

The only shipped feature that touches mobile at all is a preview convenience, not IDE access. From the same roadmap, marked "Completed": "QR Code to open preview URL on mobile device." That lets you scan a code on your desktop and open the running preview of the app you built on your phone. It previews output. It is not a way to run or edit in the IDE from the tablet.

On a phone the experience degrades further. When Firebase Studio launched, a well-known developer tried it in Mobile Safari and reported on Hacker News that it "clearly wasn't designed with mobile in mind," and that the preview panel rendered blank until he switched back to a desktop browser. His exact frustration was that he does most of his prototyping on a phone, and the tool did not meet him there. That single comment captures the whole gap better than a spec sheet would.

To be clear about what does work, because the honest version of this matters: Firebase Studio genuinely builds mobile apps. It ships Flutter, React Native, and Expo templates, an in-browser Android emulator for testing what you build, and Expo Go phone previews. If your task is "scaffold and prototype a mobile app with an AI agent and a desktop browser," it is a capable tool. The trap is assuming that "builds mobile apps" implies "runs on a tablet." Those are different sentences.

Firebase Studio sunsets on March 22, 2027

This is the fact that should weigh on any tablet decision. Google's migration page states plainly that Firebase Studio is sunsetting on March 22, 2027, and that new workspace creation is disabled on June 22, 2026. The recommended paths off the product are Google AI Studio for browser-based prototyping and Antigravity for code-first, agentic development.

Investing weeks learning a tool's quirks on an iPad only to migrate off it within a year is a poor trade. The roadmap item that would make iPad use pleasant is unshipped and non-binding, and the product carrying that roadmap has an end date. We would not tell a friend to build an iPad workflow around Firebase Studio in mid-2026. That is an opinion the Firebase team would push back on, and we will hold it anyway: a tablet workflow you cannot fully use today, on a product scheduled to shut down, is not where your setup time should go.

What about a Chromebook?

A Chromebook is the better of the two devices in that roadmap line, simply because it runs a desktop-class Chrome browser. The IDE is more usable in a real Chrome window than in iPad Safari, and several community write-ups note Firebase Studio "works better on Chromebooks currently." But it is the same unshipped "Future" roadmap entry, and the same March 22, 2027 sunset applies. A Chromebook does not change the deprecation math; it only makes the interim experience less painful. If you are on a managed school Chromebook, the browser route also sidesteps the locked-down Linux toggle, which is a real plus there.

How do you actually code on an iPad instead?

The pattern that works on an iPad is the one Firebase Studio is missing: a native app talking to a persistent cloud Linux environment. The iPad's job is to be a good client to a real Linux box, not to pretend it can run a desktop IDE in a browser tab. Once you accept that, the "iPad is bad for coding" complaints mostly dissolve.

That is what we build. The Cosyra iOS app is a universal binary that runs natively on iPad with full iPadOS multitasking — Split View, Slide Over, and Stage Manager on M-series iPads. You get a persistent Ubuntu 24.04 container with Claude Code, Codex CLI, OpenCode, and Gemini CLI already installed, 30 GB of storage, and hibernation that resumes exactly where you left off. The same container is reachable from iPhone, iPad, and the web, so we start a task on an iPad on the couch and pick it up on a phone in a waiting room without re-cloning anything.

Step 1: Install Cosyra from the App Store

Open the App Store on your iPad and install Cosyra. The same listing covers iPhone, iPad Pro, iPad Air, and iPad mini. Sign in with Apple, Google, or email, and the app provisions a fresh Ubuntu container on first launch.

Step 2: Add your model API key

Cosyra is bring-your-own-key, so you pay Anthropic, OpenAI, or Google directly rather than through us. In the terminal:

Step 3: Run an agent

Clone a repo and start a session:

How do the iPad coding options compare?

Lined up against what matters on a tablet — a native app, a persistent environment, and whether the tool is on a deprecation clock — the options sort out clearly. The table covers the realistic paths as of 2026-05-28.

Where Firebase Studio wins

A fair comparison names what the other tool does better, so here it is, with no hedging. Firebase Studio beats Cosyra on these axes, and if they describe your situation you should use it:

• Price. Firebase Studio is free during its availability (3 workspaces), against our $29.99/month after the trial. On cost alone, it wins.
• Firebase and Google Cloud integration. Emulators, App Hosting deploy, and Blaze billing live in one place. We do not replicate that, and if your whole backend is Firebase, that integration is worth a lot.
• The App Prototyping agent. Its no-code prompt-to-app flow (Next.js web output) is a lower-floor workflow than our terminal-first agents, and is genuinely better for non-developers prototyping a web app.
• In-browser Android emulator. Testing a Flutter or React Native build without leaving the browser is a real convenience we do not offer.

Who should pick which?

Here is the decision framework we would give a friend, with the tablet question front and center.

• Pick Firebase Studio if you are on a laptop or desktop, you are building or prototyping a Flutter / React Native / web app, your backend is Firebase, and you want a free, integrated, browser-based environment for the next year. The sunset is far enough out to ship a prototype.
• Pick Cosyra if the device in your hands is an iPad or an iPhone, you want a real terminal and AI coding CLIs you drive yourself, and you want a persistent box that is not on a shutdown clock and follows you across devices.
• Try Firebase Studio first if you are a non-developer who wants prompt-to-app prototyping, you already live in the Firebase console, or your only device is a desktop Chrome browser and cost is the deciding factor. In those cases its strengths line up with your needs.

Frequently asked questions

For the wider picture, our guide to AI coding agents on mobile maps every agent across phone and tablet, and the mobile coding terminal pillar covers the terminal-on-a-device decision end to end. For the phone-shaped version of this same Firebase Studio question see Firebase Studio on a phone, and if you are weighing iOS terminal apps specifically, see the best terminal apps for iPhone.