If you're talking about the bill that makes something like Airbnb illegal, their founder commented on it during StartUp School. If I remember correctly, he said that the bill was in response to people who would buy apartment buildings and use all the rooms to make them into an unlicensed hotel.
They talked with the sponsor of the bill and he said that they wanted to work with each other, or something to that effect. I haven't looked into it any more than watching his talk, so I could be wrong.
That's not to disagree with you, though. I find it a cowardly move, as well.
Hmm, how do I say this without sounding shameless? I just launched Capturely (http://www.capturely.com) to help people, especially web designers, make Coming Soon pages. It takes care of all the backend stuff for you. I'll stop there, though, before this starts to sound like an ad.
From all the Coming Soon pages that I've looked at (quite a few, lately), they all have the headline, short description and an email form. It's far from real data, but hey, that's how pretty much everyone else does it. I'd be curious to run some real tests though, which, hopefully, Capturely will let me do.
Also (and forgive the nitpick, pretty please) -- on this page: http://www.capturely.com/tour, you should set overflow: hidden, or perhaps adjust those div heights ever so slightly.
I'm seeing a scrollbar on each of the text sections. Using Chromium on Ubuntu.
Someone else in this thread mentioned 'unbounce'. (I can't remember who mentioned, but I'll upvote.)
You should go check out their landing page templates -- they're quite good. In fact, they're so good that I had to go and edit my 'coming soon' page, even though I'd told myself I wouldn't.
Yep, Unbounce does have some pretty great templates. I'm working on a system for templates. If all goes well, I'll get some "whoa, those look great" sorts of templates soon enough.
And thanks for pointing out the Chrome overflow problem. I just fixed it.
Very helpful. The Heroku docs also have a lot of information about the Heroku specific stuff that you might want to read about (like dynos and the backlog).
Asking whether or not we should "scrap" a certain resolution is missing the point. Media queries are far more exciting than "whoa, I can make my page super wide now" will ever be.
And that's a huge problem. The notion of a "pixel-perfect design" doesn't belong on the web. In the case you mention, you're sacrificing accessibility for control over what your users see. You're kind of telling your users that you know what they want better then they do. That they should be able to read the small type you put in front of them, even if their eyes are bad.
CognitiveLens is right. Proportions matter.
(Note: when I say "you", I refer to the "one [who] wants a pixel-perfect layout" which may or not actually be you.)
> The notion of a "pixel-perfect design" doesn't belong on the web.
So, if this is the case, then "px" units and raster graphics should not belong on the Web, too. But unfortunately, they do.
IMHO, the best approach would be to have two zoom modes. Some users prefer scaling text, but keeping images inact (so they won't see upscale ugliness), others prefer "screen magnifier"-like behavior. And none of those behaviors is wrong.
It'd also be nice if you could also pull iTunes data straight from a iOs or android device. I don't believe the APIs exist to do that via a web app, but it'd be nice.
I put it up with only iTunes because, well, I only had the library for iTunes and wanted to see if people used it. I figured iTunes was a good start and will to add more later.
They talked with the sponsor of the bill and he said that they wanted to work with each other, or something to that effect. I haven't looked into it any more than watching his talk, so I could be wrong.
That's not to disagree with you, though. I find it a cowardly move, as well.