gptAssist: a WebView wrapper for ChatGPT that blocks everything else

The problem gptAssist solves: ChatGPT without the browser

Opening ChatGPT in a mobile browser means tabs, history, autofill, and whatever else the browser decides to load. gptAssist takes the opposite approach. It is, in the project's own words, a simple WebView wrapper for ChatGPT, and it blocks all URLs which are not essential. The target user is someone on Android who wants the chat interface and nothing around it.

The README lists the intended shape of the app: a privacy-focused mode that blocks unnecessary URLs and tracking, a focused interface without browser distractions, a toggle between restricted and unrestricted modes, file upload for analysis, voice input, and a lightweight footprint. Those are the promises. The mechanism behind them is narrower than the list suggests, which is worth understanding before you install it.

How the URL blocking actually works

The architecture is a single Android WebView pointed at ChatGPT, wrapped in Java, with the repository split into an app/ module, a Gradle build, and fastlane metadata for F-Droid distribution. There is no API client, no local model, no proxy server. The app renders the same web page a browser would, and the difference lives in request interception.

Blocking is a toggle, not a fixed policy. The README says you switch it on or off with the button at the top right, and that swiping up a bit hides the button. Restricted mode drops requests the developer classifies as non-essential; unrestricted mode lets the page behave normally. That design has a practical consequence: when something in the chat UI fails to load, the first thing to try is the toggle, because the block list is the variable that changed.

The app also states it does not support login via Apple, Microsoft or Google account, and that you should use a web browser for initial sign up. That is a direct result of the same interception layer. Third-party identity flows bounce through domains outside the essential set, so the wrapper cannot complete them. Email and password sign-in inside the WebView is the path the project expects.

Installing gptAssist from F-Droid and signing in

The README points to F-Droid as the distribution channel, with the package name org.woheller69.gptassist. There is no Play Store badge and no APK download link in the README, so F-Droid is the route the project documents. The repository itself builds with the Gradle wrapper checked in at the top level:

./gradlew build

Run that from the repository root if you are building from source rather than installing the published package. The README does not document a build command, so treat the wrapper as the entry point the repository layout implies.

For the normal install path, open the F-Droid client and install the package by name:

org.woheller69.gptassist

That string is the package identifier the README links to on F-Droid. Search it in the client, install, and the app appears as gptAssist.

The first real use has a step outside the app. The README says to use a web browser for initial sign up, because the wrapper will not complete Apple, Microsoft or Google account login. Create the account in a browser, then open gptAssist and sign in with the same email and password inside the WebView.

Once you are in, the top-right button controls blocking. If the chat loads but a feature misbehaves, toggle blocking off, retry, and toggle it back on. The README also notes file upload and voice input as supported, so those are the two features to try first when you want to confirm the wrapper is behaving.

The blocking toggle is a blunt instrument

A URL block list is only as good as its maintenance. ChatGPT is a web application that changes without warning, and each change can introduce a new domain or endpoint the block list has not seen. The README does not describe how the list is maintained, how it is updated, or what happens when a blocked request is actually required for the page to function. That silence is the main limitation.

The toggle mitigates it, but it pushes the diagnosis onto you. There is no log, no blocked-request counter, and no per-domain allowlist documented in the README. If the interface breaks, you either turn blocking off entirely or you live with it. For a privacy-focused app, a full off switch is a coarse fallback: you get either the restricted experience or the unrestricted one, with nothing in between.

The other boundary is identity. If your organisation uses Google or Microsoft single sign-on for ChatGPT, this app is the wrong tool. The README is explicit that those flows are unsupported, and no setting changes that.

gptAssist versus a full mobile browser

The obvious alternative is the browser you already have. Chrome, Firefox and their mobile forks load the same ChatGPT page, support every sign-in provider, and update continuously. What they do not give you is a stripped interface with a request filter between the page and the network. gptAssist trades flexibility for that filter.

The trade runs in both directions. A browser handles a broken page by simply loading it; gptAssist handles it by asking you to flip a toggle. A browser supports Google sign-in; gptAssist does not. A browser is maintained by a large team against every change ChatGPT ships; gptAssist is a small Java wrapper whose block list is not documented as continuously updated.

If your goal is privacy hygiene rather than a dedicated chat window, a browser with a content blocker and a separate profile gets you much of the way there without the sign-in limitation. If your goal is a single-purpose app icon that opens straight into the chat, that is the specific gap gptAssist fills.

Certified Android devices and the 2026 deadline

The README opens with a warning that matters more than any feature: Google has announced that, starting in 2026 or 2027, all apps on certified Android devices will require the developer to submit personal identity details directly to Google, and the developers of this app do not agree to that requirement. The README states the app will no longer work on certified Android devices after that time.

That is not a bug report or a roadmap item. It is a stated end condition. On a certified device, the practical lifespan of gptAssist is bounded by that policy change, regardless of how well the app works today. On uncertified devices, the constraint does not apply in the same way, but the README does not describe support for that path either.

The project is not archived, and the last push was on 2026-05-19, so the repository has seen work in 2026. Recent releases are V2.20, V2.30 and V2.40, the most recent on 2026-03-02. None of that changes the device-policy warning, which is about Google's requirements, not the project's activity.

Licence and what forking gptAssist involves

gptAssist is licensed under GPLv3, and the README notes that the app uses parts from GMaps WV, which is also GPLv3. For an end user this changes nothing. For anyone considering a fork or a redistribution, the copyleft terms apply to the derived work, and that is a question for a lawyer rather than for this article.

The upgrade cost is the part worth weighing. The app is a WebView wrapper, so most of what you see is served by ChatGPT, not shipped in the APK. That means the APK itself rarely needs updating for feature changes, but the block list does, because the page it filters changes underneath it. The README does not document how often the list is revised or how a user would know it is stale. If you install from F-Droid, you get updates when the maintainer publishes them, and the release history shows a cadence of roughly a few releases per year rather than continuous delivery.

Editorial conclusion

Adopt gptAssist if you want ChatGPT on Android without a full browser, you accept the URL blocking trade-off, and you are willing to sign up through a real browser first. Do not adopt it if you need Apple, Microsoft or Google sign-in, or if you depend on certified Android devices past the date Google's identity requirement takes effect, since the README states the app will stop working there. Before installing, verify the current release on F-Droid and read the README warning about certified devices, because that is the constraint that decides whether this app has a future on your phone.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. README
4. Releases
5. woheller69/gptAssist on GitHub