An Open-Source Quick Share Alternative for Android Without Google
For years, one of the most visible downsides of de-Googled Android, custom ROMs, and Chinese-market builds has been the loss of Quick Share, Google’s seamless nearby file-sharing feature. An independent developer known as Kyujin-cho is now directly targeting that gap with Bada, an open-source file sharing app that implements the Quick Share protocol from scratch. Instead of relying on Google Play Services, Bada runs as a standalone app on devices that lack Quick Share and makes them interoperable with any Android phone that has it enabled. That turns previously isolated phones into full participants in the wider Quick Share ecosystem for everyday Android file transfer tasks. For users who deliberately avoid Google services, or who simply bought hardware that ships without them, Bada is the first practical Quick Share alternative that actually speaks the same language as Google’s own system.
How Bada Recreates Quick Share Without Google Play Services
Bada doesn’t clone Google’s proprietary code; it reimplements the Quick Share protocol based on observed behavior and open documentation where available. Once installed on a device without Quick Share, the app advertises itself over Bluetooth Low Energy for discovery on stock Android and Samsung One UI devices, then hands off actual transfers to Wi-Fi LAN or Wi-Fi Direct. The familiar four-digit PIN shows up on both ends, mirroring the native confirmation flow. Users can share files from any app via the system share sheet, send entire folders with directory structure preserved, and choose a specific destination folder for incoming content. Under the hood, transfers still use Quick Share’s encryption method, so compatible devices treat Bada as a legitimate peer. Crucially, only the non-Google device needs Bada installed—the Quick Share side continues using the standard system interface, keeping the experience intuitive.
Real-World Limits: Interoperability Wins and Early-Stage Rough Edges
In practice, Bada already works for local Android file transfer, but it is far from flawless. Testing shows that sharing from a Quick Share device to a Bada device can be temperamental, especially when using Wi-Fi Direct instead of a shared Wi-Fi network. Transfers to a Windows PC running Quick Share currently fail, even though the PC can see and accept the incoming request. AirDrop and QR-based receiving are not supported yet, and NearDrop compatibility on macOS remains a goal rather than a finished feature. The project is still very young, with a tiny GitHub footprint and active iteration. That means users should expect bugs and be comfortable sideloading an app that is not distributed via mainstream stores. At the same time, its open-source nature lets technically inclined users audit the code and contribute fixes, accelerating its path from proof-of-concept to daily driver.
What Bada Means for Android Fragmentation and De-Googled Phones
Bada’s significance goes beyond convenient transfers between one or two phones. It highlights a growing community push to patch holes created by Android’s fragmented ecosystem and dependence on proprietary Google components. Users of Huawei devices, Chinese builds of Android, and de-Googled setups traditionally accept missing features as the price of privacy or geopolitical fallout. By bringing a working Quick Share alternative to these phones, Bada challenges that assumption and shows that interoperability is technically achievable without Google’s blessing. It also pressures platform owners to consider how tightly they lock key experiences to their services. If independent developers can reverse-engineer and safely interoperate with core features like file sharing, the balance of power shifts slightly back toward users. Bada may never replace Quick Share on mainstream phones, but it sets an important precedent for open source file sharing in a more modular, user-controlled Android future.