As long as there are no actual, native iOS, android and PC Apps built on top of IPFS or even an access GUI or interface with browser on those platforms, IPFS can stop dreaming of replacing HTTP.
Apart from mere 1-2% of world population who use internet, no one else is going to download a binary and run a CLI, and visit 127.0.0.1:8080/ipfs.
For majority of people chrome is a gateway to internet (for them Http is a prefix u put in-front of a url) unless ipfs goes to that level, http is as relevant as ever. I know software devs who don’t know they could access files from browser via file:// protocol.
We're actually working on that, and have made progress with Brave and Opera. You're right that for wide, mainstream adoption, we'll need to expand onto platforms like Android/iOS, and that's the dream, honestly. Working on URIs like IPFS:// and IPNS://, which are supported in Brave/Opera to an extent.
It's a long road though, with lots of negotiations with lots of organizations. I do feel optimistic about it though.
Maybe I’m making it too simple but Native iOS, Android and desktop clients be a good start?
Even a good desktop client could drive the adoption like crazy.
Torrents never required any negotiations, it never depended on organisations to implement support.
Just package it enough as a standalone app.
Ipns can follow. If enough people are storing/accessing content in IPFS, organisations all implement interfaces on their own.
