11–20 of 60 posts
Instapaper solves your reading later problem nicely. I'd give it a try - a simple bookmarklet and you can read whenever, wherever you want.
At some point an article floated through here suggesting that the iPhone interface isn't simple. Rather, the author argued, it's the fact that it's very fun to use that contributes to its success.
I can't find the article right now, but I do agree with the author. The iPhone/iPad lacks affordances and all sorts of cues about what the hell you're supposed to DO with the thing. Again, my experience is that folks find it incredibly unintuitive (although they enjoyed it immensely when they 'got it').
I recognize my sample size is extremely small. However these constant assertions that Apple has managed to create an instantly usable and discoverable user experience are based on even more tenuous science. Does anyone have any hard data or usability testing they'd like to share? :)
The Safari refresh thing has always bugged me on my iPhone, but I think it's slightly more acceptable since I have an always-on connection and just have to wait 10 seconds for a page to reload.
Perhaps Apple's way of getting me to cough up the extra $130 for the 3G...
The author gushes about how awesome it is to browse the web on the ipad and then pigeonholes it because he couldn't recall a tab while he was away from an Internet connection, a closet case if there ever was one. It seems self defeating to focus on such a minor annoyance. This thing is an amazing piece of hardware, and no it's not perfect.
Instapaper is an app that's about $5. It solves all my offline reading needs for me. I've never looked back since.
This is FUD. The multitasking to be introduced in the next iteration of the ipad OS will almost certainly allow for the presence of tabs. I agree that right now it's somewhat annoying to have tabs lose state once and a while when I'm browsing, but since I only use my ipad at home where I have a persistent and fast wifi connection it's not an issue to wait a second for the page to reload. The author gushes about how a…
I get the sense that the phrase "dirty secret" is being watered down in the same sense that the word "evil" is being watered down to simply mean "something I disagree with."
Earlier quoted context omitted.
It's just the problem with the interface design paradigm that says a user should be able to do anything immediately without instruction. If you want to cache, you need to have an understanding of how the Internet works, so it's "too hard" for "most people" to understand or care about.
You're missing my point: the OS should be able to cache the (up to n ) pages that haven't been explicitly closed by the user in the HD, and when there's a page fault in main memory when a user tries to access the ones the 256MB can hold, the OS should go to the disk and grab that page, and swap out another page that's currently in RAM with the requested page. Bam, no re-downloading the page. Should be over in under a…