News for hackers. Stuff that matters.
Re:Statements about the Mobile Web by woah on Friday February 20, 2015 @03:06PM (#9082628)
It's definitely hard to do animations and touch interactions as good as native apps. Making responsive websites is really really easy for an experienced designer and/or html coder.
Re:Statements about the Mobile Web by mbesto on Friday February 20, 2015 @04:20PM (#9083106)
> Making responsive websites is really really easy for an experienced designer and/or html coder.

Migrating old websites that do not respond + adapting web based apps to mobile is however, not very easy. These two cases are probably 90% of the use cases, as opposed to the other 10% that are "really really easy".

Re:Statements about the Mobile Web by tomelders on Saturday February 21, 2015 @02:43AM (#9085015)
You can't retro fit responsiveness. Or at least you can, but it's such a bad idea that no one should try it. It's the quickest route to legacy CSS that no one will every want to touch again.

It means starting again, from design and UX all the way up to build. So for the entity that owns the website/web app it's going to be painful, but for every new website/web app, it's the norm and is pretty easy.

Re:Statements about the Mobile Web by Encosia on Friday February 20, 2015 @08:00PM (#9084166)
I agree with you, but you could say that about any site migration though, right? It's never easy to pull an old site forward to a new design/structure, responsive or not. That's been a huge pain point for as long as large sites have existed.
Re:Statements about the Mobile Web by forrestthewoods on Friday February 20, 2015 @04:18PM (#9083097)
I disagree simply because almost major website has significant usability issues with mobile. Often relating to touch input. I'm genuinely surprised anytime an image gallery is swipeable and it even half works.

It's easy to say that obviously they are shitty designers and/or coders and all they have to do is take the time to do it right. Well doing it right takes too much effort. And doing it right still doesn't get you all the way there. For any site with even a moderate degree of complexity there are always little bugs. It's just a fact of life in the HTML/CSS world.

Re:Statements about the Mobile Web by hiphopyo on Friday February 20, 2015 @04:30PM (#9083162)
> Well doing it right takes too much effort.

Who told you that? It doesn't take any more effort than a normal desktop site given the right tools.

Re:Statements about the Mobile Web by forrestthewoods on Friday February 20, 2015 @04:45PM (#9083271)
No person said it with words. Websites said it with their behavior.

There isn't even a widely supported, idiomatic way to switch between high dpi and low dpi images for crying out loud. It's been at least 5 years since such devices were common and wide spread.

Re:Statements about the Mobile Web by Bahamut on Friday February 20, 2015 @06:51PM (#9083888)
That's not a good enough indicator - it is removed from important context that may be relevant.
Re:Statements about the Mobile Web by milkytoast on Friday February 20, 2015 @07:56PM (#9084143)
img srcset + a polyfill?
Re:Statements about the Mobile Web by hiphopyo on Friday February 20, 2015 @06:08PM (#9083710)
> No person said it with words. Websites said it with their behavior.

No doubt, the majority of mobile websites need their asses kicked.

Re:Statements about the Mobile Web by chinathrow on Friday February 20, 2015 @03:57PM (#9082952)
This. And don't forget fastclick.

https://github.com/ftlabs/fastclick

Re:Statements about the Mobile Web by paulirish on Friday February 20, 2015 @04:43PM (#9083255)
Off-topic but fastclick is mostly uncessary at this point: http://developer.telerik.com/featured/300-ms-click-delay-ios...
Re:Statements about the Mobile Web by chinathrow on Friday February 20, 2015 @05:05PM (#9083373)
"Mostly" - but iOS 8 makes it mandatory, not?

"That being said, it is unfortunate that we still need to include a JavaScript library to workaround a limitation of the mobile web."

Thanks for the great link though!

Re:Statements about the Mobile Web by hiphopyo on Friday February 20, 2015 @04:33PM (#9083189)
Note that this behavior is already default in mobile web frameworks such as jQuery Mobile.
Re:Statements about the Mobile Web by chinathrow on Friday February 20, 2015 @05:07PM (#9083388)
Right. But I guess I can't include jQuery Mobile alongside jQuery on a fully responsive app (no specific mobile version at this point of time), can I?
Re:Statements about the Mobile Web by hiphopyo on Friday February 20, 2015 @06:04PM (#9083691)
Why would you not be able to use jQuery Mobile alongside jQuery in a fully responsive app?
Re:Statements about the Mobile Web by lftl on Friday February 20, 2015 @03:12PM (#9082663)
Absolutely. I think the disconnect is when some people compare native vs. web, they mean a web app that closely mimics a native app. That's absolutely hard to do, and often not worth the effort. But building a responsive website that simply functions well even if it doesn't try to feel native on every platform is not a major undertaking.
Re:Statements about the Mobile Web by hiphopyo on Friday February 20, 2015 @06:18PM (#9083750)
> That's absolutely hard to do, and often not worth the effort.

I'm not sure I agree. The JS libs are out there, you just need to find them.

Re:Statements about the Mobile Web by hiphopyo on Saturday February 21, 2015 @11:30AM (#9085920)
My GitHub search skills aren't the best, but here are some of the nicer ones I've found:

Dynamic Physics Interactions for the Mobile Web: https://github.com/luster-io/impulse

Facebook and Path style side menus: https://github.com/jakiestfu/Snap.js/

Smooth scrolling: https://github.com/cubiq/iscroll

Add to home screen call-out for mobile devices: https://github.com/cubiq/add-to-homescreen

Cross-browser usage of the JavaScript Fullscreen API: https://github.com/sindresorhus/screenfull.js/

Anybody know of any more?