News for hackers. Stuff that matters.
Re:Statements about the Mobile Web by underbluewaters on Friday February 20, 2015 @02:36PM (#9082433)
Let's not kid ourselves here. Most people download exactly zero apps per month:

http://www.slate.com/blogs/future_tense/2014/08/25/a_comscor...

This matches my experience IRL exactly. The whole Native Apps are more popular than the web narrative is a self fulfilling prophecy. People have trouble using websites on mobile because everyone puts up stupid splash pages on sites to force them to download their app. It "educates" people that the web is somehow inferior, when really those sites should be making a proper responsive website so their users can get on with their lives.

Nobody gives two shits about your app and it's smooth animations when they are just trying to pull up a recipe for chicken tikka masala.

Re:Statements about the Mobile Web by chinathrow on Friday February 20, 2015 @03:56PM (#9082943)
Yes... just seen that recently with the mobile site of scribd. If anyone of the scribd team is reading this: Why on earth do you think you can force us to install your native app by blocking reading the full content someone else gave you in order that _I_ can read it?
Re:Statements about the Mobile Web by forrestthewoods on Friday February 20, 2015 @02:56PM (#9082560)
Are native apps more popular than the web? Probably not. Is it harder to make a web app to the same level of quality as a native app? Absolutely.

Making a "proper responsive website" for mobile is far more difficult than it needs to be. Assuming it can even be done. Some things you simply can't do. Can you reach just short of native quality by expending significantly more time and effort? Yes! Is that stupid and wasteful? Absolutely.

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?

Re:Statements about the Mobile Web by Encosia on Friday February 20, 2015 @07:59PM (#9084158)
To underbluewaters' example of just getting a simple recipe on the screen, building a mobile-friendly page to display that kind of content is certainly not hard. For example, this is a recipe page that I personally worked on a few months ago (sorry, we didn't have a chicken tikka masala recipe...): http://tailgating.publix.com/recipes/29/caramel-hickory-chic...

On my phone, that page is every bit as quick as a native app. The presentation doesn't suffer. It's actually quite a bit better than many native apps I've had the misfortune of installing.

More importantly, the content is actually discoverable from web search. The alternative is forcing the user to choose a recipes app from an opaque app store search, wait to download/install it, then search in that single silo of content and hope it has the content they want. Then, rinse/repeat if they don't find a recipe they like. Even if they happen to find a nice native app on the first try that does have a good UI, good content, and the specific content they want, that is a vastly inferior experience.

Can you create a poor mobile web experience? Sure. The situation isn't very much different than janky, slow desktop sites that are laden with too many third-party scripts for ads, tracking, social, etc. Mobile does exacerbate the effect of that kind of sloppiness, but I think that stems from sites where content is secondary to advertising/social, not the feasibility or difficulty of creating a good mobile web experience.

I was going to add a disclaimer to the link above asking folks to be gentle if they peeked under the hood, because I developed that site in an insanely short amount of time for how much content and functionality is there, but maybe that's an important data point in and of itself. If it were so difficult to develop a decent mobile web experience, there's no way I could have shipped that full site in about two weeks of billable hours. Not to mention, we focused a lot more on the desktop layout than mobile, based on analytics. I wouldn't say mobile was an afterthought, but the phone layout was a fairly small fraction of the overall effort.

Re:Statements about the Mobile Web by peterhunt on Friday February 20, 2015 @08:21PM (#9084232)
That app's nav menu feels sticky when you're closing it.
Re:Statements about the Mobile Web by Encosia on Friday February 20, 2015 @08:37PM (#9084292)
It's definitely not perfect. Like I mentioned, it was developed on an incredibly tight budget/timeframe. I wish I'd had budget to polish several things like that throughout the site.

I do still think a user that searches the web for a hickory chicken tailgating recipe is still a lot better served by even that imperfect mobile web page than the alternative native workflow though. Not to say that native isn't ever a better choice for some types of apps, of course, but content like this is exactly the web's sweet spot.

(BTW, I've been playing with React lately and am loving it; great work. Looking forward to giving React Native a shot at replacing Cordova for some of my clients)

Re:Statements about the Mobile Web by tootie on Friday February 20, 2015 @06:47PM (#9083877)
I'm sure I'm in the minorty, but I'm very anti-app. I'll never install an app where a mobile site exists. For one, I get URLs which are great. Find in page always works. I can always see when I'm on https which is a huge plus. Apps are for games mostly or for services who cripple their mobile sites.
Re:Statements about the Mobile Web by thesimpsons1022 on Friday February 20, 2015 @07:31PM (#9084045)
yep. you are in the minority. This whole thread reeks of web devs hating on native mobile for no reason other than being web devs. the only website I use regularly in the browser is reddit and that is because I don't like any of the native solutions.
Re:Statements about the Mobile Web by increment_i on Friday February 20, 2015 @07:57PM (#9084154)
>> "web devs hating on native mobile for no reason other than being web devs."

Well I'm not a web guy, but I can imagine at least one reason: having to learn and work with a slew of proprietary software stacks to deploy the same thing over multiple platforms - the web finally looked like the solution to this problem until about 5-6 years ago.

Re:Statements about the Mobile Web by thesimpsons1022 on Saturday February 21, 2015 @03:24AM (#9085073)
i'm not saying web dev isn't easier to deploy for multiple platforms. I'm saying native is much better to use from a user side.
Re:Statements about the Mobile Web by zhte415 on Saturday February 21, 2015 @02:46AM (#9085018)
Please educate me why. I'm not being funny, I truly don't understand.

I understand some cases: * Need for offline; * Need to work like an IM (instant updates pushed from a server, like a telephone / IM / email service); * Need to avoid latency in user experience (a native game, vs a web-based flash-style game).

But I don't understand any others, and really would like to know.

Re:Statements about the Mobile Web by thesimpsons1022 on Saturday February 21, 2015 @03:39AM (#9085085)
1. you can do much more with interfaces and processing power in native mobile. Even simple apps like piazza or quora, I can't see being implemented nearly as nicely in the web. People think it is all about animations, but it isn't. A small example is how the entire web page has to be loaded each time you click a link on the hacker news mobile site or hit the back button or anything. A mobile app on the other hand would load all the links when you first open the app and when you hit the back button from looking at a link, you'd be met with zero latency.(not to mention persistent settings)

2. With my iPhone at least, I enjoy the predictable user interface that comes with doing stuff inside IOS.

3. I'll be honest. I don't like typing in URLS on my phone, and typing in passwords. It is a real pain when alternatively I could just click an app.

4. I really hate the mobile sites for some companies. The mobile site for my school is awful and always redirects you to some ugly main menus from the page you actually wanted. I would much rather just have the regular website.

Re:Statements about the Mobile Web by throwaway41597 on Saturday February 21, 2015 @04:37AM (#9085160)
Re (1), doing full-page rendering on the server is not up to the current state of mobile apps. You can already partially update a page. Zero latency is on par as well on the mobile web, as a web app can load its code on the first render, store some data for offline (though this is a lot more work than it is on native because of the bad state of web databases implementations) and request data to the server when it doesn't fit on a phone's memory (surely, the native Quora app doesn't store its terabytes of data on every phone)

(2) is bit hand-wavy in my opinion

(3) is spot on, bookmarking to homescreen is something people don't know about; typing a password is okay if it's only once I think

(4) is about prioritizing resources to the most popular platform: a website on desktop, a native app on mobile

Re:Statements about the Mobile Web by tootie on Saturday February 21, 2015 @03:08PM (#9086678)
1) Is the result of shops putting all their dev effort into apps. Performant and high-quality mobile sites is easily achievable if you put in the effort. Native obviously has some advantages that can't be replicated in browser, but in-browser is repeatable across platforms and prevents lock-in (for both site creators and consumers)

2) To each his own. I've never really figured out what a native look and feel was since every app looks different. And it's not like non-native slowed down adoption of the WWW for desktops.

3) Bookmarks. Android at least lets you put a URL bookmark on your desktop too.

4) Same as 1.

Re:Statements about the Mobile Web by zhte415 on Saturday February 21, 2015 @03:49AM (#9085102)
Thanks. I very much appreciate your response. :)
Re:Statements about the Mobile Web by rquirk on Saturday February 21, 2015 @09:05AM (#9085531)
One example - I use the ebay app on Android over the web site. It's miles better due to native integration. It remembers my login better than websites do (probably a security risk, but my phone's encrypted), it integrates photo-taking direct into the app which is handy for selling and buying e.g. buying: if you have a minor dispute with a seller you can just blast off a photo in the built-in messaging system. It sends notifications for watched items. The UI is also better than the mobile site - the click targets are nice and big and the lists scroll quickly - but that could possibly be improved in the site. The native integration is mostly what makes it nice.
Re:Statements about the Mobile Web by leeoniya on Saturday February 21, 2015 @02:45AM (#9085017)
same here. every time a website wants me to install an app that would not benefit significantly from being native, i think "great, what permissions is this shit gonna need?". invariably it's a slew of ones i dont ever want to give it.
Re:Statements about the Mobile Web by acjohnson55 on Friday February 20, 2015 @04:03PM (#9082993)
For most purposes, I totally agree! I think what's really needed are better standards for exposing phone functionality to webpages in a sane and secure way (this already exists for location, for example), and perhaps more seamless interfaces to the web from mobile OSs (navigating to websites, login management, etc.). I don't really buy the mobile native > mobile web > desktop narrative on a universal level. It's certainly true for some experiences but for others the opposite holds.

At the same time, the state of the browser as a graphical environment needs some help. HTML+CSS is a great interface for written content, but when it comes to dynamic graphical interfaces, it's a little insane how much we've tried to squeeze into a glorified desktop publishing engine. I'd like to think the future is something more like mutually recursive embeddings of a graphical language and HTML. We kinda sorta of have that graphical language in SVG, but I think it lacks some of the features that make HTML really friendly.

Re:Statements about the Mobile Web by krschultz on Friday February 20, 2015 @05:15PM (#9083425)
Did you ever think that maybe these companies have data that disagrees with you?

The company I work for has both proper native apps & responsive web sites. We push customers towards the native apps because the difference for us is tens of millions of dollars, at least.

Re:Statements about the Mobile Web by cwyers on Friday February 20, 2015 @04:39PM (#9083225)
From the Quartz article that Slate piece gets almost all its info in:

> Almost all smartphone owners use apps, and a “staggering 42% of all app time spent on smartphones occurs on the individual’s single most used app,” comScore reports.

http://qz.com/253618/most-smartphone-users-download-zero-app...

I'm not sure that this is evidence that people don't want apps. They just don't want a LOT of them. The ones they DO want, they want very badly.

Re:Statements about the Mobile Web by dredmorbius on Saturday February 21, 2015 @05:10AM (#9085208)
Virtually every smartphone comes with numerous pre-loaded apps.

Nothing in the quoted sentence suggests anything other than "people use the apps that come with their smartphone.

Re:Statements about the Mobile Web by Scarbutt on Friday February 20, 2015 @02:48PM (#9082517)
If only all web apps where as simple as providing food recipes.
Re:Statements about the Mobile Web by underbluewaters on Friday February 20, 2015 @03:12PM (#9082662)
Very true. For some apps native is the only solution. I'd wager most apps are on that same order of complexity though.

For example, I don't think Flipboard's use of Canvas to wrap content with fancy animations and magazine-style layout is really a damning indictment of the web platform. It's a failure to understand the medium on their part.

We've got a mature, interoperable, write once run anywhere platform that's completely free to participate in. It has some critical deficiencies I'd like to see fixed rather than abandoned.

Re:Statements about the Mobile Web by Bahamut on Friday February 20, 2015 @09:02PM (#9084356)
My personal viewpoint is that I hate downloading extra apps on my phone, having to mentally manage what permissions I want apps to have, and move into a sandboxed place - it helps decrease the amount of crapware I have on my phone, and having to manage the inevitable rogue app (or few) that destroys performance and battery life, especially if they nag me to update via the App Store (iOS) or Google Play (Android). Phones are not powerful or have good enough battery life for me to want to risk lowering my phone's life while I am out of the house. Unless it is something immensely useful to me and/or performance is that big of an issue, I rather just go to a website. If performance is that bad on a website, I'll open up the link in the browser and just use that my mobile Chrome and desktop Chrome are linked to the same account & open the tab there.

Given this, I never quite understood the gold rush to go appize everything. I may be a web developer now, but if anything, my becoming a web developer has made me use more apps, not less, simply because I make hybrid mobile apps currently.

Re:Statements about the Mobile Web by profinger on Friday February 20, 2015 @03:54PM (#9082926)
YES!! And on top of that, I don't want an app for every damn site that I visit. I hate that! I go to a website and the first thing that I see is "DOWNLOAD OUR MOBILE APP!" usually gets me mad and, if I can choose, I go elsewhere!
Re:Statements about the Mobile Web by rimantas on Saturday February 21, 2015 @04:43AM (#9085170)
Hey, let's compare comparable things. I.e. native apps to web apps, not native apps to web sites, ok?
Re:Statements about the Mobile Web by Immortalin on Saturday February 21, 2015 @07:30AM (#9085371)
Its much harder to create a decent webapp than a desktop app. For example, you can easily drag and drop together a semi-decent UI using winform/Android IDE in a couple minutes. The time it take construct a decent UI for the web is at least a magnitude longer. It's simply easier to delegate the "simple" web stuff to CMSs and move the harder logic bits to a native app where you don't have to worry so much about client-server problems, rendering etc.
Re:Statements about the Mobile Web by whoisthemachine on Saturday February 21, 2015 @10:53AM (#9085789)
Editing Android UI's is one of the most painful programming experiences I've recently gone through.

Microsoft, otoh, has done a great job with UI editors since the Visual Studio 2008 days, especially with WinForms. But it still lacks standard behaviors that HTML has in spades. I constantly find myself surprised by strange/unexpected behaviors with different controls in both XAML and Winforms!

HTML I've been doing for some 15 years, and it's still as easy to understand and edit as ever.

Re:Statements about the Mobile Web by snowwrestler on Friday February 20, 2015 @06:10PM (#9083722)
A few mobile apps are super popular, but they are apps that load webpages inside of them.

For example, I find a lot of stories to read on Facebook and Twitter. On my phone, I use their mobile apps. And when I read a story, what I'm actually reading is a mobile webpage that loaded inside the app's captive browser view (I'm on an iPhone).

So both things are true--I'm spending my time in an app, AND I'm viewing a ton of mobile websites.

Re:Statements about the Mobile Web by hiphopyo on Friday February 20, 2015 @06:21PM (#9083765)
Most of the time, the people who argue against the mobile web are the same people whose livelihoods depend on Java and native apps.

Ruby on Rails vs Java - Commercial #1 of 9: https://www.youtube.com/watch?v=PQbuyKUaKFo

Erase the Native vs. HTML5 Development Debate with PhoneGap: https://www.youtube.com/watch?v=uea1kAXlGIY

Re:Statements about the Mobile Web by bottled_poe on Saturday February 21, 2015 @07:52AM (#9085402)
It's not our livelihoods, it's our sanity. CSS + HTML = ?
Re:Statements about the Mobile Web by mkramlich on Friday February 20, 2015 @09:58PM (#9084483)
indeed. for the vast majority of people and cases some mix of Google/Wikipedia/Facebook/Craigslist/Amazon/Ebay/Tumblr/WordPress/Reddit/Yahoo/3tc is going to scratch their itch just fine. (to name just a few "big hammer" tools/platforms)