{"slug": "flet-studio-2-0-from-the-browser-to-the-app-stores", "title": "Flet Studio 2.0: from the browser to the app stores", "summary": "Flet Studio 2.0, released by the Flet team, adds cloud-based packaging and publishing that builds a single Flet app for Android, iOS, Windows, macOS, Linux and the web and ships it to Google Play, the App Store, TestFlight and the Microsoft Store without Xcode, Android Studio, the Flutter SDK or a Mac. The release follows Flet Studio's May launch, a July AI agent addition and a September update giving that agent \"eyes and ears\" to see the apps it builds. Studio 2.0 runs builds on Linux and Windows VMs and real Macs, creates and stores Android signing keys, prepares iOS bundle IDs, certificates and provisioning profiles from a one-time App Store Connect API key, and signs Windows installers via Azure Artifact Signing and notarizes macOS .dmg files with a Developer ID.", "body_md": "# Flet Studio 2.0: from the browser to the app stores\n\nWhen we [launched Flet Studio](https://flet.dev/blog/2026-05-28-flet-studio) back in May, it was a place to\nwrite a Flet app in the browser, run it and share it as a link. In July it got\n[an AI agent](https://flet.dev/blog/2026-07-17-smarter-flet-studio-with-ai-agent), and in September the agent\n[got eyes and ears](https://flet.dev/blog/flet-agent-got-eyes-and-ears) to see the app it builds.\n\nThat first post ended with a promise: \"Further down the road we'd love to take you the rest of the way: packaging and publishing your app straight from the browser. That part's still cooking.\"\n\nIt's cooked! Today we are releasing **Flet Studio 2.0**. It takes your app from the browser to\nyour users: build it for Android, iOS, Windows, macOS, Linux and the web, sign it, and publish it\nto Google Play, the App Store and the Microsoft Store. No Xcode, no Android Studio, no Flutter\nSDK, and no Mac required to ship an iPhone app.\n\n## One app, every platform\n\nIf you've ever packaged a Flet app with `flet build`, you know the drill: install Flutter,\ninstall Android Studio for Android, get a Mac with Xcode for iOS and macOS, a Windows machine for\nWindows, then figure out keystores, certificates, provisioning profiles and notarization. Each\nplatform is its own small adventure.\n\nStudio 2.0 does all of that in the cloud. Open your app, go to **Manage › Publish**, and you get\na page for every platform. Each page has a card for every place the app can go: a store, your\nown devices, or a file you share. Click **Create** and a build machine picks up your app -\nLinux and Windows VMs for Android, web, Linux and Windows apps, real Macs for iOS and macOS.\nYou watch every step and its log live, and **Activity** keeps the history of your runs.\n\nThe cards don't stop at \"here's your file\". Once the app is published, a card shows what's live\nand an **Update** button to publish the app as it is now. Let's go platform by platform.\n\n### Android\n\n- **Share an APK** on your app's download page (more on that below), or send its link to a\nfriend.\n- **Publish an app bundle to Google Play** on any track: internal testing, closed and open\ntesting, or production.\n- Studio **creates the app's signing key** for you, keeps it safe and reminds you to download a\nbackup.\n- Choose which phones an APK supports to keep it small.\n\nSee [Android](https://flet.dev/docs/studio/publishing/android) and\n[Publishing to Google Play](https://flet.dev/docs/studio/publishing/google-play).\n\n### iPhone and iPad\n\nApple's side has always been the hardest part, so we put the most work into it:\n\n- **Connect App Store Connect once** with an API key, and Studio prepares the bundle ID,\ncertificate and provisioning profile for every build. You never open the Apple Developer\nportal.\n- **Publish to TestFlight** for your testers**and to the App Store** .\n- **Install on your own devices** from an install link (an Ad hoc build), and let testers\nregister their iPhones from a link they open on the phone.\n\nSee [iOS](https://flet.dev/docs/studio/publishing/ios) and\n[App Store and TestFlight](https://flet.dev/docs/studio/publishing/app-store).\n\n### Windows, macOS, Linux and the web\n\n- **Windows:** every build makes a one-click`setup.exe` installer next to a portable`.zip` .\nSign it with[Azure Artifact Signing](https://flet.dev/docs/studio/publishing/azure-artifact-signing) , so\nWindows doesn't scare your users with warnings, and publish it to the[Microsoft Store](https://flet.dev/docs/studio/publishing/microsoft-store) .\n- **macOS:** a`.dmg` disk image signed with your Developer ID and notarized by Apple, or a\nrelease to the[Mac App Store and TestFlight for Mac](https://flet.dev/docs/studio/publishing/mac-app-store) .\n- **Linux:** a`.tar.gz` with your app.\n- **Web:** a`.zip` with the static web app to host anywhere.\n\nSee [Windows](https://flet.dev/docs/studio/publishing/windows), [macOS](https://flet.dev/docs/studio/publishing/macos),\n[Linux](https://flet.dev/docs/studio/publishing/linux) and [Web](https://flet.dev/docs/studio/publishing/web).\n\n## A download page for every app\n\nNot every app needs a store. Every app in Studio gets a public **download page** at\n`get.flet.app` with its icon, version, \"What's new\" and the latest Android, Windows, Mac and\nLinux builds. Visitors see the download for their own system first, and on a computer the page\nshows a QR code to open it on a phone.\n\nThe link never changes: put it on your website or on a flyer once, and each new version replaces\nthe app behind it. See [Download page](https://flet.dev/docs/studio/publishing/download-page).\n\n## Store listings and build settings\n\nA store release is more than a binary. Each store wants a description, keywords, release notes\nand screenshots, often in several languages. Studio 2.0 has a **store listing** editor for\nGoogle Play, the App Store and the Microsoft Store:\n\n- **Ask the agent** to write the listing, or to translate it into the languages you need.\n- **Take store-sized screenshots** right from the Preview's phone, tablet and desktop devices.\n- **Import** the listing an app already has in the store, and send it with a release or on its\nown.\n\nEach platform also has a **Settings** tab for everything `flet build` reads from\n`pyproject.toml`: the app's name and version, the icon (in any shape, previewed for each\nplatform), splash and boot screens, permissions, deep linking and Python packages. No more\nlooking up the right `[tool.flet...]` key - Studio writes `pyproject.toml` for you, so a\nproject you download still builds on your machine.\n\nStore accounts, keys and certificates are connected once in **Settings › Publishing** and used\nby all your apps. They are stored encrypted. See\n[Signing keys and publishing accounts](https://flet.dev/docs/studio/publishing/signing-keys-and-store-accounts).\n\n## The agent publishes too\n\nThe agent knows about all of the above. Ask it to \"build an APK\" or \"send this to TestFlight\" and it proposes a run as a card in the chat. Nothing starts until you click it, so the agent never spends your build credits on its own.\n\nIt can change build settings for you (\"add the camera permission\", \"use this picture as the app\nicon\"). And when a build fails, click **Ask AI to fix**: the agent reads the run's log, fixes what\nit can in the app, and suggests a new run.\n\nThe agent got a few other upgrades in this release:\n\n- **Turns keep going when you leave.** Close the tab or lose your connection and the agent\ncarries on. You'll see what it did when you come back.**Stop** ends a turn with a summary of\nwhat got done.\n- **Long chats.** When a chat gets long, Studio suggests starting a fresh one, and**New chat** can carry a summary of the old one over.\n- **The agent takes screenshots on any Preview device** , in portrait or landscape.\n\n## GitHub sync\n\nStudio isn't meant to be the only place your code lives. With 2.0 you can **sync an app with a\nGitHub repository**, in both directions:\n\n- Every change made in Studio is committed to the repository: your edits, settings and each agent turn, which becomes one commit with a message the agent writes.\n- Pushes to the repository show up in Studio, so you can keep working in your local editor, with your favorite local agent, and publish from Studio.\n\nCommits show up in **Versions** next to the versions you save yourself. See\n[GitHub sync](https://flet.dev/docs/studio/github).\n\n## A new home for your app\n\nStudio itself got a makeover:\n\n- **A new app screen** with**Agent** ,**Preview** ,**Code** and**Manage** , on the desktop and\non your phone.\n- **New Preview devices:** Windows 11, macOS, Linux, Android phone and tablet, iPhone and iPad,\nbesides the web. See how your app looks on a phone before you build it for one.\n- **App thumbnails** in your apps list and in the Gallery, with grid and list views.\n- **Accent colors:** pick Pink, Blue or Neon green in**Settings › Appearance** .\n- Studio and the Preview now run on [Flet 1.1](https://flet.dev/blog/flet-v-1-1-release-announcement) .\n\n## Plans and credits\n\nThe agent and builds now share **one credit balance**. Builds are charged by the minute while the\nbuild machine works on your app: 10 credits a minute on Linux (Android, web and Linux apps), 20 on\nWindows and 40 on macOS (iOS and macOS apps), with a 4-minute minimum. Queue time and machine\nstart-up are free, and Studio shows the rate before you start.\n\n- **Explorer** is free and includes 500 credits a month. It builds for every platform and shares\nyour apps on download pages.\n- **Credit packs** are now available on every plan, Explorer included: $20 for 10,000 credits.\n- **Creator** adds publishing to the stores, code signing for Windows and macOS, GitHub sync,\nprivate apps, the Expert agent, two builds at a time and download pages kept for a year. It\ncomes with 10,000 credits a month.\n- **Try Creator free for 7 days** , with every Creator feature and 500 bonus credits. Canceling\nduring the trial costs nothing.\n\nSee [Pricing](https://flet.dev/pricing) for the details.\n\n## Status page\n\nBuilding in the cloud means more moving parts: build machines, Macs, stores. To see whether\neverything is up, there is now a status page at [status.flet.dev](https://status.flet.dev). You\ncan subscribe to get an email when something goes wrong and when it's fixed.\n\n## Try it\n\nThat's a lot for one release, and it's the biggest Flet Studio update so far. The full list is in\n[What's new](https://flet.dev/docs/studio/whats-new), and the step-by-step guides are in\n[Publishing](https://flet.dev/docs/studio/publishing).\n\nOpen [Flet Studio](https://studio.flet.dev), pick an app (or ask the agent to build one) and\npress **Publish**. We'd love to see what you ship! Tell us how it went - and where it got stuck -\nin [GitHub Discussions](https://github.com/flet-dev/flet/discussions) or on\n[Discord](https://discord.gg/dzWXP8SHG8).\n\nHappy Flet-ing!", "url": "https://wpnews.pro/news/flet-studio-2-0-from-the-browser-to-the-app-stores", "canonical_source": "https://flet.dev/blog/flet-studio-2-0", "published_at": "2026-11-11 00:00:00+00:00", "updated_at": "2026-11-11 20:19:46.148509+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "ai-tools"], "entities": ["Flet Studio", "Flet", "Google Play", "App Store", "TestFlight", "Microsoft Store", "App Store Connect", "Azure Artifact Signing"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/flet-studio-2-0-from-the-browser-to-the-app-stores", "markdown": "https://wpnews.pro/news/flet-studio-2-0-from-the-browser-to-the-app-stores.md", "text": "https://wpnews.pro/news/flet-studio-2-0-from-the-browser-to-the-app-stores.txt", "jsonld": "https://wpnews.pro/news/flet-studio-2-0-from-the-browser-to-the-app-stores.jsonld"}}