BTW, I'm not even speaking to whether x86 can compete at the same power per watt... I think it just won't make sense financially to be out of sync with the industry.
It's worth it for your public API, but it's such a huge time sink for internal APIs.
That sounds wild. Apple says iPad is rated for up to 10 hours of video playback [1]. The display alone should consume more than that.
Airplane mode (turning off most of the wireless) seems to be a big factor as well.
I'm just as astonished as the next guy!
A bit of a turn off for wanting to help on the project....
On use cases, you can give your web app offline support by locally caching data in an SQL database and have it be fully queryable.
Say you are building an app like Notion, they already have "offline mode" for the mobile and desktop apps, this would enable you to build that for the web app.
This is very much one of the final jigsaw pieces needed to make PWAs (progressive web apps) competitive for the majority of use cases. We just need Apple to catch up and fill in a few other blanks too.
A design pattern that is beginning to emerge is "offline/local first". You design your app to fundamentally work offline, using things such as this, and the server component only works to synchronise clients. It's a bit like the design move to "mobile first" that happed 10 years ago, but going to another level.