1. Developer effort vs. perceived benefit
Many commenters questioned whether the extra work to support the Duo will translate into meaningful user gains or revenue.
- “But will you gain anything by building for it? Will you see noticeably more users or people choosing another alternative because you didn't specifically building the app for Duo?” – matsemann
- “Nothing ventured, nothing gained.” – reaperducer (replying to matsemann)
- “Duo users also likely have disposable income to spend on in‑app purchases, maybe click on ads… So I do think it's worth building for it.” – busymom0
2. Market niche and Vision Pro parallels
The Duo is repeatedly described as a niche product, with its price and expected sales compared to the Vision Pro’s limited adoption.
- “I'm just gonna ignore this thing and continue as if it never existed. Worked with Vision Pro that no body uses and will work with this.” – khoury
- “It is indeed a niche product. Its price reflects the sales expectations of Apple.” – whatever1
- “'Niche' in this case means ~10M in its first year, compared to an estimated 250M Apple smartphone shipments in 2027.” – CharlesW
3. Technical feasibility, tooling, and early‑release bugs
Developers noted that supporting the Duo isn’t a huge lift if they already handle resizable windows, but they criticized the late release of tools and anticipated initial UI breakage that will improve over time.
- “supporting Duo is not an enormous lift if you're already supporting resizable windows, as developers are required to do for OS 27.” – CharlesW
- “And when did Apple decide to grace us with tools to support the Duo? Yeah, 3 hours ago. This should've been out in June…” – isodev
- “I expect that most apps will look rather broken on release, but it will be smoothed out eventually.” – yreg
- “Sadly, many apps will continue to look rather broken. There are still thousands of apps that still look wrong on iPad 16 years after its release…” – reaperducer