> In case you're still thinking your iPhone is a crappy computer, No, the iPhone in your pocket is already performant enough to function as a full fledged server. It's the network that doesn't support it.
A crappy computer, no; a crappy server, yes. The available network is part of a server. A URL that points to a machine that can't be accessed whenever the owner goes into a tunnel, is a URL nobody will link to.
(Another part of the evaluation of "a server" is the available concurrent I/O throughput. There is a reason the term "slashdotted" exists, and thinking an iPhone—or even a home PC—makes a good server for serving anything with any exponential-interest-curve potential is it. This is also the reason why nobody has built the sequel to Iridium using cube-sats.)
> Unless this comes as completely free AND it comes built into the device
Yes, that's exactly the future that cloudlet advocates like IBM are talking about:
1. the ISPs run compute clusters at the edge, including both setting up traditional co-los, and making their in-home gateway modems into compute hosts as well;
2. the device/"cloud" providers (Apple, Google, etc.) make agreements with said ISPs to pay for time on those edge-clouds;
3. the device/"cloud" providers resell (possibly at a loss, to encourage lock-in) the use of the aggregate edge-cloud to the app developers on their platforms; or, they let developers use the edge-cloud in their apps for free, and pass the costs onto only heavy users, the same way they do with document storage today;
4. the users of these devices suddenly have cloudlet-enabled apps, and most don't have to pay a cent more.
Amusingly, you can already see that the device/"cloud" providers are trying to short-circuit this whole process, skipping the ISP step, by simply selling people consumer-electronics devices that could sit in their homes, connected to ZeroTier-like overlay networks, hosting mobile cloudlets. You know, like the Google Home and Amazon Echo.