|
|
|
|
|
by jonsmock
5456 days ago
|
|
All of these arguments are the same arguments you need to think through when determining whether to make a web app vs. a native app on the desktop. They're identical, because the desktop is just another device. I completely agree with all the arguments, except possibly that we should never use hacks. We used (and still use) hacks on the web for desktop use when browsers sucked, and we'll do it on mobile devices, too. It's the way the state-of-the-art is pushed forward; it's inevitable. I think he would agree with me, seeing that he pointed out Scrollability's use on the iPad being somewhat valid. That said, the author's underlying point examines why we use those hacks and to evaluate whether we're solving a non-existent problem. Edit: I might clarify my hacks point. The reason they're inevitable is that they sometimes expose browser deficiencies. A current example would be web sockets. We've been using comet-type hacks in lieu of a real web socket solution (and Chrome has now implemented one). |
|