Multica Go for Android: Features and Availability

Multica Go for Android is coming soon. This article covers its core features, differences from the iOS version, and how to request early access.

Aug 31, 2026 · 5 min read · 856 Words · -Views -Comments · AI Tutorials

Ever since I released Multica Go for iOS, people have kept asking the same question: when will there be an Android version? It is finally ready for invited testers.

The most important detail comes first: Multica Go for Android is still in closed testing on Google Play and has not been released publicly. If you would like early access, email multicago@1991421.cn to request an invitation. The current target is a public release in September 2026, but the exact timing still depends on testing and Google Play review.

Closed-test page: Multica Go on Google Play

If the page does not show an install button, your current Google account probably has not been added to the tester list. Email multicago@1991421.cn and include the email address you use for Google Play.

Why Build an Android Version?

In What Is Multica, and Why Did I Build the Multica Go iOS Client?, I introduced Multica as a managed-agent platform that turns coding agents such as Claude Code and Codex into teammates you can assign work to.

For me, the point of a mobile client is not to duplicate the entire desktop experience. It is to let me hand off and handle tasks while away from my computer or whenever using a computer is inconvenient:

  • Check the inbox and see how an agent’s work is progressing;
  • Open an issue, reply to a comment, or change its status;
  • Create an issue or chat as soon as an idea occurs to me;
  • Check projects, agents, runtimes, and usage;
  • Switch between servers and workspaces.

The iOS app proved that this workflow is useful, but not everyone uses an iPhone. Building an Android version was the natural next step.

It Is Not a WebView Wrapper

The Android app is designed as a native mobile experience rather than a website packaged as an app. It aims to preserve the same product journeys as the iOS version while following Android interaction conventions.

For example, an iOS-style swipe action may become a long-press menu on Android. QR scanning, widgets, and notifications also use platform-native Android capabilities. The two apps share the same goals, but their interactions do not need to look identical.

What Can the Closed Test Do Today?

The Android app already covers the main day-to-day Multica workflows on a phone:

  • Sign in with an email code and connect to an official or custom Multica service;
  • Save and switch between multiple servers and workspaces;
  • Browse Home, Inbox, Issues, Projects, and Chats;
  • Create and edit issues and work with comments, properties, dates, and attachments;
  • Manage projects and their resources;
  • View agents, runtimes, squads, skills, automations, and workspace members;
  • Review usage and use ChatGPT usage widgets;
  • Use mobile features such as deep links, server configuration sharing, themes, and multiple languages.

The workflow I care about most is completing a small loop entirely from my phone: receive an inbox alert, open the related issue, review the agent’s result, add one more instruction, and let it continue. Many tasks no longer have to wait until I return to my computer.

Is It Identical to the iOS Version?

Not yet.

The Android app prioritizes common phone workflows first. Some details are still being completed, including fuller global search, parts of the issue and chat experience, notification services, voice input, and tablet and foldable layouts.

Some differences are also platform-specific. Apple Handoff does not directly apply to Android, while widgets, push notifications, QR scanning, and launcher shortcuts require Android-native implementations.

This closed test is therefore best suited to people who are willing to report problems and accept that the product is still evolving. If you need a completely stable app with one-to-one iOS feature parity, waiting for the public release will be a better choice.

How to Request Closed-Test Access

The process is simple:

  1. Email multicago@1991421.cn;
  2. Include the Google account email address you use with Google Play;
  3. After I add the account to the tester list, open the Google Play test page;
  4. Install the app and sign in to your Multica account or connect to a compatible self-hosted service.

If you find a problem, please include your phone model, Android version, reproduction steps, and screenshots when possible. Those details make the issue much easier to diagnose.

About the Public Release Date

The current goal is to release the public Google Play version in September 2026. Feedback from the closed test, stability work, and Google Play review may affect the final timing.

After the public release, the Google Play listing will show an install option to users with eligible devices in supported regions.

Final Thoughts

  1. Multica Go for Android has the same goal as the iOS app: helping you manage agents, triage the inbox, and move issues forward while away from your computer—not rebuilding a complicated desktop workspace on a phone.
  2. If you use Android and already have a Multica account or self-hosted service, email multicago@1991421.cn to request access. Your feedback will directly shape the final round of improvements before the public release.
  3. Even with AI helping us today, developing, releasing, and maintaining an app still takes considerable effort. When you run into a problem, friendly and constructive feedback is therefore the most helpful approach.
Authors
Developer, digital product enthusiast, tinkerer, sharer, open source lover