Hacker News Reader

The app can support IPv6 while not actually using it for communication. This would be a matter of allowing people to enter IPv6 addresses, websites, e-mail addresses, etc; logging, and displaying IPv6 addresses rather than hard-coding IPv4-only approaches, etc. Basically, prepare your app so that if your backend supports IPv6, your app already does.

It would be bigger news if iOS 9 required all apps to support not having access to IPv4.

View on HN

There's really no point having IPv6 if you still require IPv4. It's a natural middle step, but you're still burning an IPv4 address.

On the contrary, there are advantages in having your apps/clients support ipv6 even if your backend is not ready to offer v6 connectivity:

1) your app/client will work just fine on ipv6-only networks with NAT64 gateways, making for a better experience for your customers (less breakage on such networks) and will help network operators transitioning to v6,

2) if it does any kind of p2p (think rtp, webrtc, bittorrent, sip, etc.), it will take advantage of nat-free v6 paths for client to client communications, regardless of which address family it uses to talk to the backend.

Reply on news.ycombinator.com