Hacker News Reader

Phone apps in general have a huge problem with extremely high timeouts and no user-facing cancel/retry buttons.

My intuition for whether a request that's not done yet is ever going to complete seems to be much better than what's written into most apps. It's really annoying when I have to entirely kill and reopen the app, rather than just have that one operation retried.

View on HN

The answer to that of course is that the underlying network protocols need to be aware of this dilemma. It's wasteful for every developer to try and solve this problem on their own.

The main culprit here is of course TCP's session based view of the world which was invented for a completely different era. An era when "cable got cut" was a catastrophic event that was almost never going to happen. It's a pity that the native app world is still mostly stuck with TCP/HTTP based networking stack where a UDP/mobile-specific-protocol is what's needed.

Reply on news.ycombinator.com