Live data from Hacker News

The Promise of Firefox OS

sergimansilla.com

101–110 of 147 posts

Re: The Promise of Firefox OS

#101

Earlier quoted context omitted.

It has been done several times with some degree of success: - Java Applets - Microsoft Silverlight - Adobe Flash

Premature, propietary, propietary.

> Premature, propietary, propietary.

pro - what?

s/propietary/proprietary/

Re: The Promise of Firefox OS

#102
I can easily see it beating Android/iPhone (or at least competing). I can't wait to get my hands on such a phone and I'll definitely be making apps for it. I think a lot of developers are like myself since 1) it's all JavaScript/HTML5 which is cool and 2) it's by Mozilla and company. Once there are a bunch of apps the people will come, unless the mobile industry decides to make this fail or Firefox OS turns out to be terrible.

Also I think people miss, this isn't just a phone full of webapps, it's about opening up the native functionality of the phone to JavaScript. So operating the camera, accelerometer, contacts list API, etc.

Re: The Promise of Firefox OS

#103
post #66

This is a real question and no trolling: Why is nobody building a second kind of browser, one which is not based on html and css. A browser which is geared towards app execution and development. A browser which can run apps which can be programmed in a way that is similar to programming Android apps. Where I can for example have a footer without doing some css hacks. DNS and most of our backends could still be reused…

Not 100% sure what you mean, but wasn't Java ME a portable solution, a platform geared towards app execution and development? And in a limited sense it even succeeded... Not sure I want a 2nd iteration though.

Java ME doesn't have any of the advantages of the web. Like links or being searchable and so on. It's just another app environment. I am talking about combining the advantages of the web (which is not css/html) with those of successful app development platforms.

Re: The Promise of Firefox OS

#104

Earlier quoted context omitted.

I surf this site on my iphone daily. Yes I occassionally downvote something I did not mean to, yes dead link annoys me if I lose what I typed. But the user experience of sharing and gathering opinions of intelligent well informed people from all corners of the world and backgrounds more than compensates. IMO of course. And thats what I mean - Craigslist is the other "broken" site that does UX well. Its not meant to b…

Please don't say "UX" when you mean "content".

My experience of HN is mostly reading the content.

The User Interface is the text box, the outstanding orange/grey theme. But the experience is, upvote buttons that are too small to use well, and great insightful posts from clever informed people. Also me.

I do mean experience. Its a holistic thing.

Re: The Promise of Firefox OS

#105
post #77

Earlier quoted context omitted.

No adblock on mobile (yet?) :P Rooted Android phones can install apps[0] that block most ads (I think it only blocks connections to the ads and doesn't do any fancy CSS rules). And Firefox on Android has Adblock Plus browser extension which as far as I know blocks ads like it does on the desktop version. No root needed for this. [0]: AdAway (I use this) https://play.google.com/store/apps/details?id=org.adaway Adblock…

Firefox Mobile has Adblock Plus available.

Here's the link to Adblock Plus for Firefox on Android. It works great! :)

https://addons.mozilla.org/en-US/android/addon/adblock-plus/

Re: The Promise of Firefox OS

#106

I still don't understand why Firefox OS will go anywhere when webOS did not. Aren't we talking about basically the same thing? HTML5/JS/CSS? Is it timing, the changed environment that now focuses attention on web apps? Is it the reputation of Mozilla vs that of Palm/HP? I'm not saying web apps won't have a place, I'm just extremely confused about the seeming contradiction or about-face here.

The problem with webOS of course was not the sdk or anything related to how to build an app for that platform. It was just the lack of interest and relevance which is needed to attract developers.

Re: The Promise of Firefox OS

#107

Earlier quoted context omitted.

Please don't say "UX" when you mean "content".

My experience of HN is mostly reading the content. The User Interface is the text box, the outstanding orange/grey theme. But the experience is, upvote buttons that are too small to use well, and great insightful posts from clever informed people. Also me. I do mean experience. Its a holistic thing.

The term "UX" doesn't generally include the content. I don't consider VLC to have bad UX if it's playing a movie I don't like.

Re: The Promise of Firefox OS

#108

Earlier quoted context omitted.

It has been done several times with some degree of success: - Java Applets - Microsoft Silverlight - Adobe Flash

Premature, propietary, propietary.

Java applets were proprietary at the time. The Macromedia Flash Player predates Java applets.

Re: The Promise of Firefox OS

#109
post #52

Earlier quoted context omitted.

Not at all. Dead serious. If HTML/CSS/javascript had been properly developed we wouldn't even have to deal with all the issues surrounding web dev. All these issues have been addressed by OS development decades ago (e.g. duplex connectivity, UX layout, MVC split, performance, just to name a few), yet we still have to deal with them now. Million of man-hours have been wasted due to them.. So no, this is not trolling.…

Mobile apps have made it possible to write your app once and have it work on multiple platforms? Gee, I must have missed that (as I post to HN, a web app that works on multiple platforms).

You mean a mix of server side generated code full of CSS, JavaScript and HTML hacks so that it behaves in a similar way across multiple browsers?

Re: The Promise of Firefox OS

#110
post #36

Earlier quoted context omitted.

I worked as a front-end developer for an adnetwork for two years, so I take a little responsibility for your experience. I tried my best, but there just wasn't that much interest in getting it right. Here's why I think we're all having a hard time with advertising in mobile. Basically, adnetworks are still learning how to do it right, the same way designers and developers are still learning how to do mobile websites…

I'll provide a different option: it takes too much time to get it right! iOS for example provides so many default widget toolkits complete with gradient, sheen, and dropshadow which make it really easy to create a polished experience quickly. The web has no such concept (well, bootstrap is sorta close but not nearly as polished and not for mobile). Why does the web not have these polished frameworks? Simple - ROI. Th…

It does have them. There are many toolkits that provide components for the web. Bootstrap is just one of them and one that has been getting a lot of publicity here for a while because it's new and has a nice design. But there are many out there that cover different aspects of mobile web development: YUI, Sencha Touch/ExtJS, Dojo, jQuery UI/Mobile, Enyo...

And pre-made toolkits still require you to tinker with them to get layouts right, make them fit your design and make ads work OK in them. That's true for both the web and native toolkits.

Post reply on HN