Merge: The Bridge App That Finally Brings Apple Watch and Android Together
2026-02-21 | ProductHunt | Official Website

Product Screenshot: On the left, an Apple Watch is connected to a Galaxy S24 Android phone; the middle shows Android notifications forwarded to the watch; the right shows Spotify music control. The three core scenarios are clear at a glance.
30-Second Quick Take
What is this app?: It lets you use your Apple Watch with an Android phone—receive notifications, sync health data, control music, and even works the other way (Wear OS watch with an iPhone).
Is it worth your attention?: If you're the type who "loves Apple Watch sensors but refuses to use an iPhone," this is likely the most polished solution available. However, the $60/year subscription and battery drain issues mean it's still a bit away from being "perfect." For developers, the market demand here is real, and the technical barriers are high enough to be interesting.
Three Questions: Is This for Me?
Does it matter to me?
Target User Profile:
- Android users who believe Apple Watch health sensors (ECG, SpO2, Fall Detection) are superior to Wear OS watches.
- Users switching from iPhone to Android who don't want to waste their existing Apple Watch.
- iPhone users who prefer the design and battery life of a Samsung Galaxy Watch.
- Dual-phone users (one iPhone + one Android) who want one watch to connect to both.
Is that me? If you currently use a phone and watch from the same platform, you probably don't need this. But if you've ever wondered, "Why can't this watch connect to the other system?" then you are Merge's target audience.
Common Scenarios:
- Scenario 1: You use a Pixel 9 as your daily driver, but the diving/outdoor sensors on the Apple Watch Ultra tempt you --> Use Merge.
- Scenario 2: Your company issued an iPhone for work, but your personal phone is Android, and you want notifications from both on one watch --> Use Merge.
- Scenario 3: You are strictly an iPhone + Apple Watch user --> You don't need this at all.
Is it useful for me?
| Dimension | Benefit | Cost |
|---|---|---|
| Time | No need to pull out two phones for notifications | Initial setup takes 30–60 minutes |
| Money | No need to buy an iPhone ($800+) just for the watch | $60/year subscription fee |
| Effort | One watch for health data from both platforms | Shorter battery life, occasional troubleshooting |
ROI Verdict: If you already own an Apple Watch and an Android phone, $60/year is much cheaper than buying an iPhone. However, if you haven't bought an Apple Watch yet, it's easier to just buy a Wear OS watch (Pixel Watch, Galaxy Watch) and save yourself the hassle.
Is it a crowd-pleaser?
Why it's satisfying:
- Breaking the Walled Garden: Simply put, it turns Apple and Google's "incompatibility" into a "connection," which feels like a win against tech monopolies.
- Health Data Sync: Heart rate, ECG, and blood oxygen data from the Apple Watch can now flow directly into Android's Health Connect—something previously unthinkable.
Real User Feedback:
"This app really really works well with my Samsung Ultra." — App Store User
"Finally someone managed to break through the ecosystem barriers. I can even receive notifications remotely when I'm away from my phone." — App Store User
Common Complaints:
"Works well if you have a monthly subscription but drains my watch's battery in just a few hours!" — App Store User
"The pricing is just way off... no one is going to pay $60 per year to use this." — XDA Forums User
For Indie Developers
Tech Stack
- Core Protocol: Bluetooth Low Energy (BLE)
- Key Technology: Apple ANCS (Apple Notification Center Service) — the protocol Apple provides for BLE devices to receive notifications.
- Apple Watch Side: Native watchOS App (Swift)
- Android Side: Android App (Kotlin/Java), using Foreground Service for persistence.
- Data Sync: Health Connect API (Android side) for health data synchronization.
- Communication Layer: BLE GATT connection for bi-directional data transfer.
How the Core Features Work
Merge's core logic: Install a watchOS app on the Apple Watch and an Android app on the phone, then connect them directly via BLE.
For the Wear OS → iPhone direction (Merge's original feature), the tech is relatively straightforward: it uses Apple's public ANCS protocol. The Wear OS watch acts as a BLE peripheral connecting to the iPhone, receiving notifications just like a standard pair of Bluetooth headphones. This protocol was designed for third-party accessories.
For the Apple Watch → Android direction (the new feature), the challenge is much greater: the Apple Watch doesn't naturally expose its BLE discoverability, and system-level pairing isn't open to third parties. Merge's solution is to run an app on watchOS that actively initiates a BLE connection to the Merge app on the Android phone, bypassing system pairing limits.
Open Source Status
- Merge itself is not open source.
- Similar Open Source Project: WatchWitch — created by a security research team at TU Darmstadt, it reverse-engineered the Apple Watch wireless protocol stack. However, it requires a jailbroken iPhone and a rooted Android, making it a research project rather than a daily tool.
- Difficulty to Replicate: High. Requires mastery of the BLE protocol stack, dual-platform development (watchOS and Android), and constant adaptation to annual OS updates. Estimated 2-3 people for 6-12 months.
Business Model
- Monetization: Subscription-based.
- Pricing: ~$5/month or ~$60/year, with a 14-day free trial.
- Transition Controversy: Merge started as a free app (notifications only) and later added health sync and music control before switching to a fully paid subscription, which sparked frustration among early users.
- Developer Response: "Developing and maintaining the app requires significant effort, which can only be sustained through subscriptions."
Big Tech Risks
Medium-High.
Apple once publicly stated they spent three years researching bringing Apple Watch to Android but ultimately gave up due to "technical limitations." Apple has no incentive to let their watch support a competitor's phone—which is exactly Merge's moat.
However, the real risk comes from regulation: The EU's DMA (Digital Markets Act) has already forced Apple to open up notification forwarding and proximity pairing for third-party watches in iOS 26.3 (currently EU-only). If these policies expand globally, Merge's core value could be replaced by system-level solutions.
For Product Managers
Pain Point Analysis
- Problem Solved: Breaking the ecosystem barrier between Apple Watch and Android.
- Severity: It's a must-have for cross-platform users. An Apple Watch is essentially a brick without an iPhone for activation. However, this user base is relatively niche.
User Personas
- Core User 1: Tech geeks/enthusiasts who love tinkering with cross-platform solutions.
- Core User 2: "Locked-in" users who switched phones but still have a watch from the other ecosystem.
- Potential Users: 18% of potential smartwatch buyers who hesitate due to platform fragmentation.
Feature Breakdown
| Feature | Type | Description |
|---|---|---|
| Notification Forwarding | Core | Android notifications appear on Apple Watch |
| Health Data Sync | Core | Apple Watch data syncs to Health Connect |
| Music Control | Core | Watch controls phone music playback |
| Find My Phone | Utility | Watch rings the phone to find it |
| Contact Sync | Nice-to-have | Synchronizes the address book |
| Camera Control | Nice-to-have | New feature: watch controls phone camera |
Competitor Comparison
| Dimension | Merge | Bridge (Orienlabs) | WatchWitch (Open Source) |
|---|---|---|---|
| Direction | Bi-directional: AW→Android + WearOS→iPhone | One-way: WearOS→iPhone | One-way: AW→Android |
| Price | ~$60/year | Cheaper, has free tier | Free & Open Source |
| Barrier | Low (Store download) | Low (Store download) | Extremely High (Jailbreak+Root) |
| Features | Notifications+Health+Music+Find My | Notifications+Health+Media | Notifications+Health+Firewall |
| Stability | Medium (Battery issues) | Medium (iOS background limits) | Experimental |
Key Takeaways
- Smart Bi-directional Strategy: Starting with Wear OS → iPhone (technically easier) to build a user base and reputation before tackling Apple Watch → Android (harder) reduced startup risk.
- Lessons from Monetization: The strategy of going from free to paid caused significant negative reviews. A Freemium model from the start would have been much better.
- Middleware is a Good Business: As long as Apple and Google maintain their walled gardens, there will be a market for middleware.
For Tech Bloggers
Founder Story
- Company: Merge Labs Ltd, registered in Givatayim, Israel.
- Origin Story: When the founder switched from Android to iPhone, he found his Galaxy Watch completely unusable. Google and Samsung ended Wear OS support for iPhone in 2021. He thought, "This is ridiculous," and started building Merge.
- Core Philosophy: "The best hardware and the best platforms should work together, regardless of who made them."
Discussion Angles / Controversies
- Angle 1 — The Walled Garden Battle: Apple spent three years researching Apple Watch for Android and gave up, yet a small Israeli team did it? This suggests "impossible" might actually mean "unwilling."
- Angle 2 — Subscription Fatigue: The jump from free to $60/year caused a massive backlash. This is a microcosm of the subscription pricing dilemma for indie developers.
- Angle 3 — EU Regulatory Dividends: The EU DMA is forcing Apple's walled garden open. Is Merge a pioneer or will it be rendered obsolete by regulation?
Hype Data
- PH Ranking: 98 votes (Moderate hype).
- Hacker News: Featured twice in "Show HN" (2023 for Wear OS→iPhone + 2026 for Apple Watch→Android), showing product evolution.
- XDA Forums: 3-page discussion thread with an active community.
- Twitter: @MergeWatch is consistently updated.
Content Suggestions
- Best Angle: "How an Israeli developer used the BLE protocol to break the walled gardens of Apple and Google."
- Trending Opportunity: Tie it into the EU DMA forced-openness topic to discuss the future of cross-platform interoperability.
For Early Adopters
Pricing Analysis
| Tier | Price | Included Features | Is it enough? |
|---|---|---|---|
| Free Trial | 14 Days | All features | Enough for testing |
| Annual | ~$60/year | All features | Depends on your cross-platform reliance |
| Monthly | ~$5/month | All features | Not as cost-effective as annual |
Getting Started Guide
- Setup Time: 15–30 minutes.
- Learning Curve: Low.
- Steps:
- Search for "Merge Apple" on the Google Play Store and install.
- Search for "Merge" on the Apple Watch App Store and install.
- Pair the two apps via Bluetooth.
- Select which notifications to forward in the Android app.
- Start using.
Note: You still need an iPhone for the initial setup and activation of the Apple Watch. Merge does not replace this step.
The Catch & Complaints
- Battery is a major issue: Multiple users report watch battery life dropping from 1+ days to less than 12 hours. The background BLE connection is power-hungry. The developer says they are optimizing.
- Unreliable calling: The calling feature frequently hits network errors; some users say "calls just don't go through."
- No transition for free users: Long-time users who were used to free notification forwarding were suddenly hit with a mandatory subscription, causing a lot of frustration.
- Missing common features: You can't see the weather on the watch yet (developer says it's in progress).
- Cellular watches drain faster: If you have a cellular Apple Watch, it may use the cellular network more frequently when connected to an Android phone.
Security & Privacy
- Data Transfer: Transmitted locally via BLE; does not go through cloud servers.
- Health Data: Synced to Android Health Connect and stored locally.
- Privacy Policy: merge.watch/privacy_policy.html
- Security Risk: While BLE connections use Apple's ANCS encryption, third-party middleware always carries some inherent risk of data exposure.
Alternatives
| Alternative | Pros | Cons |
|---|---|---|
| Bridge (Orienlabs) | Cheaper, has free tier | Only Wear OS→iPhone; no AW→Android |
| WatchWitch | Free & Open Source, has firewall | Requires jailbreak+root; experimental |
| Buy same-platform watch | Most stable, full features | Must give up the watch you love |
| Dual-phone setup | Full functionality | Must carry two phones; high cost |
For Investors
Market Analysis
- Smartwatch Market Size: $44.28B (2026), projected to reach $142B by 2034.
- Growth Rate: 15.68% CAGR.
- Global Users: 563 million (2026), up 23.7% YoY.
- Pain Point: 18% of potential buyers hesitate due to platform fragmentation; this is Merge's addressable market.
Competitive Landscape
| Tier | Players | Positioning |
|---|---|---|
| Platforms | Apple (watchOS) / Google (Wear OS) | Maintaining walled gardens |
| Regulators | EU DMA | Forcing open interoperability |
| Third-party Bridges | Merge (Bi-directional), Bridge (One-way) | Independent middleware |
| Open Source | WatchWitch | Academic/Geek research |
Timing Analysis
- Why now?: Three trends are converging: (1) Apple Watch leads in sensors but only supports iPhone; (2) Android launched Health Connect as a unified platform; (3) EU DMA is mandating cross-platform interoperability.
- Tech Maturity: BLE 5.0+ bandwidth and low power are finally sufficient for real-time sync.
- Market Readiness: Frustration with "walled gardens" is at an all-time high following EU regulation, validating the demand for cross-platform solutions.
Team Background
- Company: Merge Labs Ltd (Givatayim, Israel).
- Scale: Small independent team (exact headcount not public).
- Track Record: Launched Wear OS→iPhone in 2023, major overhaul with health sync in late 2024, and Apple Watch→Android in 2026.
- Note: This "Merge Labs Ltd" is entirely unrelated to the brain-computer interface company "Merge Labs" backed by Sam Altman.
Funding Status
- Undisclosed Funding: Appears to be a bootstrapped indie developer team.
- Revenue Model: Subscription-based (~$60/year).
- Risk: EU regulation might lead platform owners to build their own cross-platform support, squeezing out third-party players.
The Bottom Line
One-sentence verdict: Merge captures a real but niche pain point—cross-platform interoperability between Apple Watch and Android. It has technical moats, but the uncertainty of EU regulation and battery life issues are two swords hanging over its head.
| User Type | Recommendation |
|---|---|
| Developers | Worth studying their BLE+ANCS technical route, but building a similar product has high barriers and regulatory risks. |
| Product Managers | The "bi-directional bridge" strategy is a great lesson—start with the easier direction to build a base before tackling the hard stuff. Also, learn from their monetization mistakes. |
| Bloggers | Great story potential: Walled gardens + small team vs. tech giants + EU regulation. |
| Early Adopters | If you have an Apple Watch + Android combo, it's worth the 14-day trial. But keep expectations in check regarding battery and stability. |
| Investors | The market is real but the window may be limited. EU DMA progress might force Apple to open up natively, which would significantly devalue third-party bridge tools. |
Resource Links
| Resource | Link |
|---|---|
| Official Website | https://www.merge.watch/apple-watches |
| ProductHunt | https://www.producthunt.com/products/merge-connect-apple-watch-to-android |
| App Store (iOS) | https://apps.apple.com/us/app/merge-connect-android-watches/id6698894276 |
| Google Play | https://play.google.com/store/apps/details?id=com.mergecorp.merge |
| Twitter/X | https://x.com/MergeWatch |
| Hacker News Discussion | https://news.ycombinator.com/item?id=47088898 |
| XDA Forums | https://xdaforums.com/t/app-wear-os-merge-connecting-wear-os-to-ios.4616337/ |
| Open Source WatchWitch | https://github.com/seemoo-lab/watchwitch |
| Competitor Bridge | https://olabs.app/ |
2026-02-21 | Trend-Tracker v7.3