# Lightning Browser: A Lightweight Android Browser Built in Kotlin

> Lightning Browser is an Android-only, Kotlin-based browser distributed through F-Droid and Google Play. Its commit history is current, but the newest tagged release is v5.1.0 from 2019, and that gap shapes what you should expect.

**anthonycr/Lightning-Browser** — A lightweight Android browser with modern navigation

- Repository: https://github.com/anthonycr/Lightning-Browser
- Website: http://acrdevelopment.org
- Stars: 2,433 · Forks: 857
- Language: Kotlin
- License: MPL-2.0
- Published: 2026-09-28 · Updated: 2026-09-28 · Language: en
- Canonical page: https://hysenlabs.com/projects/anthonycr-lightning-browser

## What Lightning Browser Is For

The README describes the project as a lightweight Android browser with modern navigation, and the feature list is deliberately short: bookmarks, history, multiple search engines (Google, Bing, Yahoo, StartPage, DuckDuckGo and others), incognito mode, customizable search suggestions, and a navigation drawer or bottom drawer used for tabs. There is no sync service, no extension store, no reading mode and no desktop counterpart. The repository is Android-only: the top level holds a single app module, a Gradle wrapper and Kotlin build scripts.

The intended user is someone on Android who finds a full browser heavier than they want and who values the drawer-based tab model over a tab strip. The README's tagline is "Speed, Simplicity, Security", but the concrete claims behind that phrase are the short feature list and the permission table, not benchmarks. There is no published performance comparison, so treat the speed framing as a design goal rather than a measured result.

## How the Permission Model and Drawer Navigation Work

The most specific engineering detail in the README is the split between permissions granted automatically and permissions requested only when needed. INTERNET, ACCESS_NETWORK_STATE, INSTALL_SHORTCUT and POST_NOTIFICATIONS are automatic. The rest are gated: WRITE_EXTERNAL_STORAGE and READ_EXTERNAL_STORAGE appear when you download files or import and export bookmarks; ACCESS_FINE_LOCATION is tied to a Location access option that is disabled by default; RECORD_AUDIO, CAMERA and MODIFY_AUDIO_SETTINGS are tied to a WebRTC Support option that is also disabled by default.

That is a real design decision, not marketing. A browser that ships WebRTC off by default trades video calling and some real-time sites for a smaller permission surface, and the README is explicit that you must enable WebRTC Support before sites can use the microphone or camera. ACCESS_NETWORK_STATE is used to stop loading resources when network access is lost, which is a small but sensible behaviour for mobile connections.

The navigation model is the other structural choice. Tabs live in a navigation drawer or a bottom drawer rather than in a tab bar, which the README calls a "unique utilization". On a phone this keeps the viewport clear, but drawer tabs are slower to scan than a visible strip when you keep many pages open. The README does not document a maximum tab count or how the drawer behaves with large numbers of tabs.

## Installing Lightning Browser on Android

The README gives two distribution channels and no build-from-source instructions for end users. The F-Droid listing is at acr.browser.lightning, and the Google Play listing uses the same package name. If you build from the repository instead, the top level contains a Gradle wrapper and Kotlin build scripts, so the standard wrapper invocation applies. The README does not document a required JDK version or an Android SDK level, so check the Gradle files in the repository before assuming a toolchain.

```bash
git clone https://github.com/anthonycr/Lightning-Browser.git
cd Lightning-Browser
./gradlew assembleDebug
```

The wrapper downloads the Gradle version pinned in the repository, then compiles the app module. On Windows use gradlew.bat instead of ./gradlew. The README does not state where the resulting APK lands, so inspect the app module's build output directory after the build finishes.

For a first real use, install from F-Droid or Google Play, open the app, and confirm the two privacy-relevant toggles before browsing. Location access and WebRTC Support should both be off, because the README says they default to disabled. Then open the drawer to see how tabs are presented. When you download a file or import bookmarks, Android will prompt for storage access at that moment rather than at install time, which is the behaviour the permission table describes.

## The Release Gap Is the Main Risk

The repository is not archived, and the last push was on 2026-09-28, so development activity on the main branch is current. The release history tells a different story: v5.1.0 was tagged on 2019-10-01, preceded by v5.0.2 and v5.0.1 in September 2019. There is a multi-year gap between the newest tagged release and the current commit activity, and nothing in the repository explains it. That could mean the project is maintained as source without cutting releases, or that the store builds lag the branch. Either way, if you depend on versioned artifacts, you are depending on something last tagged in 2019.

A second limitation is scope. This is an Android app, not a cross-platform browser. The related searches include Lightning Browser for Windows and for PC, but the repository and README describe no desktop build. If you need a desktop browser, this project is the wrong tool, and no amount of Gradle work will change that.

A third is WebRTC. Because camera, microphone and audio settings are gated behind an option that is off by default, video conferencing sites will not work until a user finds and enables that setting. For a general-purpose browser that is a meaningful capability gap, and the README does not describe a prompt that tells users to turn it on when a site requests media access.

## How It Compares to Firefox for Android and Bromite-Style Builds

Firefox for Android is the obvious alternative, and the difference is architectural rather than cosmetic. Firefox ships its own Gecko engine and a sync account system, so bookmarks and history move between devices. Lightning Browser uses the Android system WebView and has no sync feature in its README. If cross-device continuity matters, Firefox solves a problem Lightning Browser does not attempt.

A second comparison is with privacy-hardened WebView browsers, the category Bromite belonged to. Those projects also wrap the system WebView but focus on ad blocking and fingerprinting resistance. Lightning Browser's README lists no ad blocker and no fingerprinting controls, so its privacy story rests on incognito mode and the default-off permission toggles. That is a narrower position: fewer moving parts, but also fewer protections. If you want a hardened WebView browser, this is not that project, and the README makes no claim that it is.

## Licence and Upgrade Cost

Lightning Browser is licensed under the Mozilla Public License 2.0, and the README carries the standard header: "This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0." MPL-2.0 is a file-level copyleft licence. In practice that means modifications to covered source files must be made available under the same licence, while larger works that combine MPL files with other code can be licensed differently. This is a general description of the licence, not legal advice; read the LICENSE file and, if you plan to redistribute a modified build, get proper counsel.

Upgrade cost is where the release gap bites. If you fork the project, you inherit a Kotlin Android codebase with a Gradle wrapper and a single app module, which is a manageable shape. But you also inherit the question of which branch your users are actually running, since the newest tagged release is v5.1.0 from 2019 while main continues to receive commits. There is no documented upgrade or migration path in the README, and no documented rollback procedure either. Anyone maintaining a fork should decide early whether to track main or pin to a tag, because the two will diverge.

## Conclusion

Adopt Lightning Browser if you want a small Android browser with a navigation-drawer tab model, incognito mode and selectable search engines, and if you are willing to run a build whose latest tagged release is v5.1.0 from 2019 while commits continue on main. Do not adopt it if you need a desktop browser, a WebRTC-heavy experience, or a product with predictable release cadence. Before committing, verify the permission behaviour yourself: install from F-Droid or Google Play, confirm that Location access and WebRTC Support are off by default, and decide whether the storage permissions the app requests only when downloading or importing are acceptable on your device.

## FAQ

### Is Lightning Browser safe to use?

The README documents a permission model where location, camera, microphone and audio settings are gated behind options that are disabled by default, and WebRTC Support must be enabled before sites can use media devices. Storage permissions are requested only when downloading files or importing and exporting bookmarks. The README does not describe an independent security audit.

### What is a good alternative to Lightning Browser?

Firefox for Android is the closest well-known alternative, but it ships its own Gecko engine and a sync account system, while Lightning Browser uses the Android system WebView and lists no sync feature. Privacy-hardened WebView browsers are another category, though Lightning Browser's README lists no ad blocker or fingerprinting controls.

### Is Lightning Browser available for Windows or PC?

No. The repository contains a single Android app module, and the README describes an Android browser distributed through F-Droid and Google Play. Nothing in the repository describes a desktop build.

### How do I install Lightning Browser?

The README points to F-Droid at acr.browser.lightning and to Google Play under the same package name. Building from source requires cloning the repository and running the Gradle wrapper, though the README does not document a required JDK or Android SDK version.

### Why is the latest Lightning Browser release from 2019?

The release history shows v5.1.0 tagged on 2019-10-01, and nothing in the repository explains the gap between that tag and the commits on main. The repository is not archived and the last push was on 2026-09-28, so source activity and tagged releases have diverged.

## Sources

- [anthonycr/Lightning-Browser on GitHub](https://github.com/anthonycr/Lightning-Browser)
- [License: MPL-2.0](https://github.com/anthonycr/Lightning-Browser/blob/main/LICENSE)
- [Project website](http://acrdevelopment.org)
- [README](https://github.com/anthonycr/Lightning-Browser/blob/main/README.md)
- [Releases](https://github.com/anthonycr/Lightning-Browser/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/anthonycr-lightning-browser