Kiwi Browser

Kiwi Browser is a mobile web browser based on Chromium (web browser), designed primarily for Android (operating system) devices and notable for integrating built-in ad blocking and support for extensions (computing). It emerged in the late 2010s amid growing attention to privacy-focused alternatives such as Brave (web browser) and revival forks of Mozilla Firefox for mobile. The browser combines components from Blink (browser engine), V8 (JavaScript engine), and elements of Google Chrome while targeting users seeking extension compatibility and customization on Android platforms.

History

Development began as an independent effort by a small team responding to limitations in mobile versions of Google Chrome, particularly lack of extensions (computing) support and aggressive advertising practices associated with platforms like AdMob and networks tied to Alphabet Inc.. Early public builds appeared on third-party app repositories and drew comparisons to forks such as Yandex Browser and Microsoft Edge (mobile). The project timeline intersected with major milestones in Chromium (web browser) development, including updates to the Blink (browser engine) and WebExtensions standards championed by Mozilla Foundation and W3C. Releases tracked API changes in Android WebView and upstream security patches from Google Chrome while community discussion occurred on forums associated with XDA Developers and issue trackers inspired by GitHub projects. The browser’s adoption increased as users migrating from Opera (web browser) and legacy Firefox for Android sought extension support and ad blocking on mobile.

Features

The browser ships with an integrated ad blocker and options to manage pop-up behavior and tracking protection similar to features in Brave (web browser) and Blockada. It supports many desktop-style extensions (computing) originally distributed via Chrome Web Store and created for ecosystems like Mozilla Add-ons. The interface offers tab management influenced by Google Chrome and gesture controls reminiscent of Vivaldi (web browser), with a speed dial inspired by Opera (web browser). Media playback implements features comparable to YouTube (service) background play on Android, and the user agent string handling mirrors techniques seen in User-Agent workarounds used by Safari (web browser) and Microsoft Edge (mobile). Integration with WebRTC and standards from WHATWG enables real-time communication and modern web app support. Accessibility and internationalization draw on patterns from Android Accessibility Suite and translation flows used by Google Translate and Microsoft Translator.

Privacy and Security

Privacy features compete with implementations from Brave (web browser) and privacy tools like TOR Project-adjacent offerings. The browser provides options to disable JavaScript, private browsing modes analogous to Incognito mode in Google Chrome, and controls to clear cookies and site data similar to features in Mozilla Firefox. Security updates rely on prompt incorporation of patches from Chromium (web browser) and tracking of vulnerabilities reported to organizations like CVE and coordinated through OpenSSL-adjacent disclosure practices. Users have evaluated its approach against recommendations from Electronic Frontier Foundation and standards promoted at IETF meetings. Concerns discussed in community fora referenced practices by Google LLC and incident responses modeled after Ubuntu and Debian package maintenance.

Performance and Compatibility

Performance characteristics hinge on the Blink (browser engine) and V8 (JavaScript engine) versions bundled with each release, affecting benchmarks such as those published by JetStream and Octane (benchmark). Rendering and layout performance are comparable to contemporary Chromium (web browser) builds, with variations stemming from processor and GPU drivers on devices from manufacturers like Samsung Electronics, Google (company), Xiaomi, and OnePlus. Extension compatibility depends on adherence to WebExtensions APIs and API deprecations tracked by Mozilla Foundation and Chromium (web browser) mailing lists. Web compatibility testing aligns with resources from Can I Use and standards from W3C, while media codec support reflects licensing and platform support similar to issues encountered by VLC (media player) and FFmpeg-based projects.

Development and Licensing

Development has been community-oriented with periodic binary releases; source components derive from Chromium (web browser), releasing under the mix of licenses that govern Chromium components including BSD license, MIT License, and other third-party licenses familiar from open-source software distributions. Contribution and issue discussion mimic workflows used by GitHub and GitLab projects, and coordination with upstream Chromium mirrors processes found in Fedora and Debian packaging. Legal and trademark considerations reflect precedents set by Google LLC and cases involving open-source licensing adjudicated in venues such as United States Court of Appeals for the Federal Circuit and referenced by organizations like the Free Software Foundation. Ongoing maintenance requires tracking security advisories from CVE databases and patch management practices common to Android Open Source Project maintainers.

Category:Web browsers Category:Android software