The cross-platform messaging layer

iMessage on Android.
Plus Loadit. Plus Veritas. Plus @handle.

Open-source fork of OpenBubbles + PyPush. Each user signs in with their own Apple ID — or registers their Android phone number directly with iMessage via Apple SMS verification, no Apple ID at all. Decentralized; no central server for Apple to nuke.

Connect now Live product

Why Beeper Mini died and Bubbles lives

Beeper Mini was a centralized commercial service. Apple targeted their backend and killed them in days. OpenBubbles is open source, each user uses their own Apple ID or Android number, and there is no central server for Apple to nuke. Apple has chosen not to escalate against open-source code — doing so would attract DOJ antitrust attention they don’t want.

We ride the same model. The Hylaq Bubbles fork stays open source + free. Monetization is the Loadit fees on in-thread payments — same way Stripe makes money from Stripe Checkout, not from the verb “send.”

Three sign-in modes

APPLE_ID

Your @icloud.com or other Apple-account email. Existing iMessage user, just on Android now.

APPLE_PHONE

A phone number already tied to your Apple ID. Common for iPhone users switching to Android.

ANDROID_PHONE

Your Android number registered DIRECTLY with iMessage via Apple SMS verification. No Apple ID needed.

What only Hylaq Bubbles has

Loadit pay-in-thread

Type `$50 to @maria` inside any iMessage thread. It ships as a Drop link with a rich-card unfurl. Recipient claims with their @handle. The first messaging app with native programmable money.

@handle mentions + Veritas-signed senders

Tag any Hylaq user. Recipient sees a verified-human badge. Anti-spoofing native — green-bubble spam dies.

Web push notifications

Get an iMessage alert in any browser the moment it lands — desktop Chrome, Safari, Edge, Firefox. Bodies stay encrypted; we just know one arrived in thread X.

Cross-bridges to Hylaq Line

One Android friend without an Apple ID? The thread automatically splits — iPhone members keep iMessage features; the Android holdout joins via Hylaq Line. Group chats stay intact.

The 40-year arc

Year 1
Android iMessage holdouts
50M+ Android users globally with iPhone friends. Each install onboards a Hylaq @handle that gets reused for Drop, Address, Sign, Hotspot, Grid. Forced multi-product adoption.
Years 2–4
Cross-platform group chats
Hylaq Bubbles + Hylaq Line bridge — every group chat stays rich regardless of phone. The 'one Android friend kills the chat' problem is solved.
Years 5–8
The post-iMessage messaging layer
Apple's iMessage moat erodes (DOJ, EU, RCS-by-default). Hylaq Bubbles is the cross-platform default — Apple users + Android users + every other format converge on @handle.
Years 9–15
Programmable messaging substrate
Every message is signed, every payment is in-thread, every contract is signable, every group is a wallet. The chat IS the financial primitive of the new internet.

Shipped today

5 Prisma models — BubblesAccount, BubblesThread, BubblesParticipant, BubblesMessage, BubblesPushSubscription
3 sign-in modes — Apple ID, Apple-verified phone, Android-direct iMessage registration
Privacy-first metadata only — bodies stay on device + Apple, never persist server-side
6 API routes — account / threads / messages / push subscribe / push key
Web Push notifications via service worker + VAPID — desktop + mobile browsers
QR-code device-pair flow — scan from Hylaq Bubbles Android app to bind @handle
4 consumer pages — landing, connect, inbox, single-thread metadata view

iMessage was never closed by accident.

Apple kept it shut to keep Android users locked out. We took OpenBubbles’ lock-pick and built a programmable money + identity layer on top. The green bubbles die.

Connect now Learn more