Ask HN: New attempt at mobile markup – keep or bail?
41–50 of 299 posts
Re: Ask HN: New attempt at mobile markup – keep or bail?
#42Re: Ask HN: New attempt at mobile markup – keep or bail?
#43Actually, I'd like that change on larger devices as well. I've often misvoted on my Surface. As large touchscreens become more popular (iPad Pro, the Surface line, etc), I could see this becoming a problem for more users.
Edit: I see white margins on my iPhone 5, but not on my iPhone 6. It looks like you need to tweak the media query in the following css:
@media only screen
and (min-device-width : 375px)
and (max-device-width : 667px) {
...
The iPhone 5's device width is 320px. Changing that 375 to something lower should fix the issue.Re: Ask HN: New attempt at mobile markup – keep or bail?
#44But, yeah I'd keep it for sure. Definitely an improvement
Re: Ask HN: New attempt at mobile markup – keep or bail?
#45Re: Ask HN: New attempt at mobile markup – keep or bail?
#46Re: Ask HN: New attempt at mobile markup – keep or bail?
#47It's an improvement, keep pressing on. One thing I'd do is find a way to minimize the detail line below the headline. It doesn't need to be as large - it tends to wrap into a second line (at least on my iOS 9.1 iPhone 5s). The detail line also doesn't need to be as verbose, IMO... e.g.: 200 points by foobar 8 hours ago | flag | 192 comments could be simplified to 200 pts by foobar 8h ago | flag | 192c
Although I would recommend keeping the "192 comments" link at least as large as it currently is. That's probably the 2nd-most tapped-on link (after the link to the source itself), and it's fairly difficult to aim correctly on mobile. Making it even smaller will make it harder to tap. https://en.wikipedia.org/wiki/Fitts%27s_law
Re: Ask HN: New attempt at mobile markup – keep or bail?
#48Re: Ask HN: New attempt at mobile markup – keep or bail?
#49This comment form could also use work. It doesn't fit the width of the screen, so I have to pinch/scroll to see what I've written then maneuver back to type. Nor does it auto expand or allow manual resizing. Just trying to scroll risks pull-to-refresh in Chrome for iOS or some embedded WebKit browsers.
I'd also say the navigation could be addressed. The first comment about sizing is a start, but the separate site and account navigation lists don't have enough space now, let alone once you up the font. Some sort of collapsing/hidden/drop down menu might need to be considered if you intend to keep 8 independent links with sufficient padding for accurate tapping.
A good start, but still not there IMO.
Re: Ask HN: New attempt at mobile markup – keep or bail?
#50It would be nice if the mobile experience (or both) would use a simple javascript confirmation box when hitting "flag". Flagging seems like it should be an exceptional action and it simple to just hit "ok" as a confirmation step rather than trying to find what you accidentally flagged on the page to unflag.