[Feature Request]

[ADIVIDAN1012]

🚀 Feature Request: Native Android Support for BrowserOS

Context

BrowserOS provides a powerful, privacy-first, agentic browsing experience by running LLMs locally and automating tasks. Currently, this experience is limited to desktop operating systems (Windows, macOS, Linux).

Motivation

To truly fulfill the mission of providing a decentralized, powerful, and private AI-powered browser, BrowserOS must meet users where they are: mobile devices.

1. Market Reach: Android represents the largest mobile operating system globally. A native Android version would dramatically expand the user base for BrowserOS and its open-source philosophy.
2. Continuous Agentic Workflow: Many users perform research and automation tasks on the go. Mobile support would enable agents to monitor sites, fill forms, or summarize content regardless of the user's location, maintaining a continuous workflow.
3. Local AI on Mobile: Modern Android devices (especially flagship models) are increasingly capable of running smaller, local LLMs via tools like Ollama/MLC. An Android app would enable true, on-device, private AI agents without reliance on cloud APIs.

Problem Statement

The core agentic value of BrowserOS is currently inaccessible to the majority of global internet users who primarily browse on an Android device.

• Current State: User must switch back to a desktop environment to use the full power of BrowserOS agents.
• Desired State: Users can install a dedicated BrowserOS application from the Google Play Store (or sideload) and continue their agentic workflows on their Android phone or tablet.

Proposed Solution / Technical Considerations

Given that BrowserOS is a Chromium fork, the most viable path is to leverage the existing Chromium codebase designed for Android.

1. Utilize Android Chromium Port: Adapt the existing desktop application components to work within the Android port of Chromium.
2. Kotlin/Java Wrapper: Create a native Android wrapper (using Kotlin/Java) to manage the browser view, system permissions, and device-specific integrations (e.g., system notifications for agents).
3. Mobile Agent UI: Redesign the agent UI (side panel, command bar) to be touch-friendly and accommodate smaller screens (potentially using a bottom sheet or a full-screen overlay for command input).
4. Local LLM Integration: Prioritize connecting the agentic features to an on-device LLM framework (like a mobile port of Ollama or a dedicated Android ML model) to preserve the core privacy-first ethos.

Requested Action

We request the core development team to add Android Support to the roadmap for BrowserOS. This represents a significant undertaking but is necessary for the project's long-term growth and mission alignment.

[shadowfax92]

Thank you for the detailed feedback, but Android support is not on our roadmap right now. I think we want to stay laser-focused on providing a great desktop experience before moving into other platforms. We'll add it to our backlog, and this is definitely six months to a year away. 🙂