Live data from Hacker News

Ask HN: New attempt at mobile markup – keep or bail?

news.ycombinator.com

101–110 of 299 posts

Re: Ask HN: New attempt at mobile markup – keep or bail?

#103

Keep, but as others suggested it can still be tweaked a bit. I'm on android chrome and below is what I'm seeing, it would be great to remove the white space on the sides like others have shown it is on the iphone... http://imgur.com/zaHK3PC

Agree, I'm getting the same thing on an Iphone 5s. But much better than before!

Re: Ask HN: New attempt at mobile markup – keep or bail?

#105
post #97

Please please keep it. It's not perfect (comment text still small, buttons & links are small, etc), but it's much better than before. There are surely hundreds of web designers who'd be more than happy to submit their proposals for fixing the mobile markup for free. It's disappointing to see that the website that I spend the most time on on my phone still didn't have a mobile markup till today. Thank you for doing th…

This 1000x. As a frontend dev I'd be happy to volunteer to invest the time to make sure this works on the current range of viewports.

Re: Ask HN: New attempt at mobile markup – keep or bail?

#108
Firstly, thanks so much for starting to work on this!

Let me suggest a few things:

* I'm confused as to why you're using tables for layout? Might want to consider something more modern, and use tables just for tabular data, and use divs, classes, and CSS for handling the layout: http://learnlayout.com/ You can get a lot done without using tables and tags, etc.

* The width on your table is 85%, why not 100%? Let that bad boy go to the edge of the viewport, on mobile every pixel counts.

* I'd suggest adding this to your 'body' css, make that content go to the edge of the viewport:

margin: 0; padding: 0;

* I see a lot in inline styles in your table, you might want to consider taking those out, and just throwing them into your CSS stylesheet. Those are the most specific, and override everything. Maintaining that will be hard, and painful. Unless you have some historic, or those are dynamically entered for good reason by your CMS, I'd take them out.

* Things like this could be better improved by removing, and just adding padding to the element you really wanted to add some breathing room around

* 318 points Perhaps this is a personal preference but I prefer classes over ids in CSS. Classes are more easily overridden, and have less headaches than ids on large websites http://csswizardry.com/2011/09/when-using-ids-can-be-a-pain-...

* Reason for these? Looking at it, I'm not sure what value it might provide. If it's something that isn't pertinent to that item on the page, I'd consider not rendering it, as there is nothing in it, and you, as a general rule shouldn't use spans or divs to solely help you lay things out on the page

* As I see you have these there, since you're laying out with a table, I'd encourage you to not do that. Tables are markup heavy, and you'd find you could bring your page weight down if you did not use tables for layout. See http://www.stevesouders.com/blog/2013/05/09/how-fast-are-we-...

Specifically for mobile:

* Responsive Design: https://developers.google.com/web/fundamentals/design-and-ui...

* Touch Targets: http://www.smashingmagazine.com/2012/02/finger-friendly-desi...

I hope some of those tips are helpful. Keep going! Keep learning!

Re: Ask HN: New attempt at mobile markup – keep or bail?

#110
This looks great on my phone; please keep it. The text sizes are awfully small but still really clear and the layout seems to work well.

One caveat is the text entry box for entering a comment is a fair amount wider than the screen in either orientation. I hope this can be fixed.

Post reply on HN