4 ms·
Direct link when on iPad: http://onswipe.com/hackernews http://onswipe.com/hackernews Let me pre-empty where I know there's going to be some dislike as a lot o
by jasonlbaptiste 15y ago
Direct link when on iPad: http://onswipe.com/hackernews http://onswipe.com/hackernews
Let me pre-empty where I know there's going to be some dislike as a lot of the HN crowd just wants the normal non-swipeable web. Most of that frustration comes from a > year old version powering Wordpress.com (which we're upgrading). Would love to hear feedback on this specific version of our platform. Most articles in this version should render well, except those that aren't really news or blog content (ie- direct link to webpages).
- kgermino 15y agoIs there a way to see comments or is this articles only? Thanks!
- jasonlbaptiste 15y agoJust articles since this is focused more on reading, sorry :/. That kind of sucks though, since the big value of HN happens to be the discussion. In reality this is meant to be: you want to read all the awesome content making the HN front page without clutter and in one place for your iPad, go to this url.
- wiredfool 15y agoI'm one of those people who hates the wordpress one. I clicked on the link, and had the same "Oh crap, not this" reaction I have with the wordpress theme. Specifics: 1) There were a couple flashes of differently styled content, one on the blog post, then one with a column of text and an image, and then the page. 2) It was slow as hell (several seconds per flash), and I wanted out by the time I saw the first flash of content. Which brings us to the 3) Back button. On an ipad 1, I can't mash the back button fast enough, so I get caught in a redirect hell and have to close out the tab and go back to hacker news some other way. 4) Going to the direct link crashes Safari. I was going to take a video, but I've got kids screaming for breakfast.
- tzs 15y agoYou always say you are upgrading the version on Wordpress.com. When is that ACTUALLY going to happen?
- lazugod 15y agoThe idea of pre-emptying a future discussion queue makes for an interesting pun, but the word is preempt.
- jen_h 15y agoIt looks pretty, but I'm having trouble loading any article sans seppuku (3 out of 4 taps crash Safari when browsing onswipe/hackernews). If I can get an article to load without the kernel assassinating Safari for memory pigginess, attempting to swipe or move around the page will crash it, too. :( No other memory issues browsing other non-Onswipe web sites or using other apps; I'm on a 1st gen iPad running 5.0.1. If you guys aren't stress-testing this on a 1st gen iPad with a goodly number of apps resident in the background, I'd really recommend adding this to your test matrix...
- bwsd 15y agoOnSwipe is a solution looking for a problem to solve and does not bring any additional functionality to a website using it. There are lots of creative and attractive themes out there. Unfortunately, OnSwipe replaces that creativity with a renderer that makes every page look the same (i.e. boring). One of the biggest advantages of the iPad is its full-featured web support on a mobile platform; OnSwipe wipes out this advantage. It removes built-in iPad features (e.g. scrolling, page zoom, etc.) making reading pages awkward and unnatural. And it introduces a cheesy, unnecessary bouncing effect. For this and other reasons I find OnSwipe to be useless and a bane to my web browsing experience.
- falling 15y agoHere's some feedback on this specific version: let me opt out of it globally, on every single website on the Internet. Thank you.
- shinratdr 15y agoYou've offered no specific replies to the multitude of problems in this thread so I figured I might just ask point blank: Is crashing out after a couple swipes on a first generation iPad accepted and not a problem in your eyes? Because EVERYONE with a first gen iPad is having that exact problem, and you've chosen to completely ignore them. Crashing is ALWAYS a bad experience, regardless of what preceded it. It's not subjective, or ambiguous, or possibly the users fault. It's 100% the fault of your memory intensive page, something that you refuse to take responsibility for or acknowledge is a problem. From that, I can only assume this crap is geared towards iPad 2 owners only, giving me a bunch of extra reasons to hate it. Not only are you going to code a convoluted solution to something that isn't a problem for 2% of the web, you're also going to cut that in half to 1% by ignoring original iPads. So frustrating.