Hey r/browsers — I’m the developer of LonoX Browser, an Android browser built on Mozilla GeckoView.
I’ve been reading browser discussions here over the last few days, and rather than just dropping a Play Store link, I wanted to explain what I’ve actually been building, what makes it different, and some of the testing I’ve done before asking people here to try it.
What is LonoX?
LonoX currently uses GeckoView 158 and has its own Android UI and browser features built around it.
Some of the main features are:
Neutral Protection Engine
This brings together protection-related features such as external-link handling, Website Shield and Isolation Mode.
For example, when a link is opened from another Android app, LonoX can let you choose how that external link should be handled, including opening it through Isolation.
Isolation Mode
Isolation Mode is designed for opening a site in a separate browsing context with tighter restrictions.
In Isolation, LonoX restricts things such as:
• downloads
• file uploads
• camera
• microphone
• direct site access to device location
• opening external apps
• Android Autofill participation
• page-initiated sharing
• and more
To be clear, restricting direct access to device location does not mean a website cannot estimate an approximate location from your IP address.
Isolation also avoids carrying that browsing context into normal browser history/session state.
When an Isolation journey ends, LonoX closes the isolated Gecko sessions and clears that isolated context rather than restoring it as a normal browser tab.
Website Shield
Website Shield performs local checks for suspicious navigation and domains, including things such as lookalike domains, mixed-script/IDN patterns and suspicious redirects.
I deliberately keep these local warnings separate from Gecko Safe Browsing.
🟢 Green: No suspicious local signal was detected. This is not a guarantee that the website is safe.
🟠 Amber: LonoX detected something suspicious or unusual.
🔴 Red: Gecko/Safe Browsing identified the destination as phishing, malware, harmful or unwanted software.
Gecko Safe Browsing remains enabled independently of Website Shield.
Customization
LonoX includes customizable themes, accent colors and different visual combinations so users can personalize how the browser looks and feels.
Quick Tabs
Quick Tabs provide faster access to frequently used websites without having to repeatedly search through the normal tab list.
Adaptive Download Engine
For eligible downloads, LonoX can progressively move between sequential and parallel range downloading depending on how the connection and download behave, rather than simply opening the maximum number of connections immediately.
Some other browser-level choices
• Global Privacy Control enabled
• Fission enabled
• Gecko login autofill disabled browser-wide
• HTTPS-only behavior for Private browsing
• Gecko Safe Browsing remains enabled independently of Website Shield
• Separate privacy/session boundaries for Normal, Private and Isolation browsing
What I’ve actually tested
A large part of development has been spent on regression testing and failure cases rather than only checking whether normal browsing works.
Some of the release/device QA has included:
• phishing, malware and unwanted-software Safe Browsing test fixtures
• expired, wrong-host and self-signed TLS certificates
• protection behavior across Normal, Private and Isolation modes
• a fresh-profile immediate-protection test after clearing app data
• protection after force-stop and restart
• Normal ↔ Private cookie separation
• Normal ↔ Isolation cookie separation and Isolation cleanup
• localStorage separation and cleanup across Normal, Private and Isolation
• IndexedDB separation and cleanup checks
• Private/Isolation protection from Android screenshots, screen recording and Recents previews
• external link → Isolation → security warning → End Isolation flows
• website permission behavior for camera, microphone and device-location access
• download pause/resume and recovery scenarios
• completed-download SHA comparison against the same reference file downloaded through Chrome
• Release builds with R8/minification and resource shrinking enabled
• repeated physical-device regression testing after fixes
This is not a claim that LonoX has undergone an independent professional security audit.
These are development, automated/regression and manual-device tests I’ve performed while building the browser.
For transparency, LonoX also has a user-controllable anonymous usage statistics setting, currently enabled by default and switchable off in Settings.
It is used to help estimate active installations and does not include browsing history, URLs or searches.
I’m especially interested in feedback from people who care about browsers:
What would you need to see before trusting a newer Gecko-based browser as your main browser?
And if you already use Firefox, Fennec, Mull, Brave, Cromite, Vivaldi or something else, what would a new browser actually need to do differently for you to consider switching?
I’m the developer, so criticism is absolutely welcome.
If you try LonoX and find any bug, compatibility problem, unexpected behavior, security concern or something that simply feels wrong, please let me know.
I’d genuinely like to investigate issues and improve or fix them as quickly as I reasonably can.
Even small feedback helps.
I’m building this independently, and I’d much rather hear what needs improvement than pretend everything is already perfect.
If you’d like to try LonoX yourself, it’s available on the Google Play Store:
https://play.google.com/store/apps/details?id=com.lonox.browser