Design Principles Behind Firefox OS Explained
At MozCamp Warsaw, a presentation was given on the design principles behind the core Firefox OS experience. Layering of applications (if you're wondering why the Firefox mobile interface has that weird curve by the tab control, you'll find answers here), an emphasis on content over visual frills for their own sake, consistent iconography, and clean typography dominate.
I like!
can you run Chrome on it?
I'm guessing the main principle is to find ways to annoy people who liked the previous versions and to hide stuff from them.
How very Microsoft of them.
I see even classic Slashdot is now pretty much unusable on dial up anymore.
is anything like their punctuation, grammar or spell-check, I see bad things in the future.
We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
It's almost a tit for tat copy of Windows Phone, in so many ways.
The price is always right if someone else is paying.
Cache everything 40 times.
Use MB sized buffers for chunks of data less than a kB.
Cache all traffic in memory.
Cache all images in memory multiple times, especially large ones.
Cache all ads in memory.
Pre-load all links and cache in memory to give the illusion of speed.
Multiply all memory allocation sizes by 100.
Did I mention to cache everything in memory? I did mean everything.
You're holding it wrong. If you hold it right, that won't happen.
EmacsM-^H Firefox would be a great OS if only it had a decent text editorM-^HM-^H web browser.
Designing an OS? Are you serious? Have you ever looked at the documentation on Firefox beyond the user stuff? Mozilla's support for using Firefox on more than one computer at a time is so bad that the web is littered with abandoned effort after abandoned effort from end user to do it for them!
How on earth do they think they are going to support an operating system which /requires/ management when they can't even support a browser that requires management? You shouldn't have to go dozens of web sites to track down the settings and troll developer forums to get the settings needed to mass deploy an application.
Mozilla, you really, really need to spend some time talking to people in the enterprise and learning what their needs our for managing fleets of computers. I've been on more than one meeting where Firefox was axed from deployment - even though every single person in the room personally used it, preferred it, acknowledged it was more secure - strictly because it is completely unmanageable for an enterprise. Don't get me start on their administrative toolkit either. It isn't close to usable and doesn't begin to cover what is needed.
I'm sorry, until you can get your act up to speed for a single application support at least somewhere to the level of say, Microsoft, Adobe, Oracle, your simply being absurd. It's not about the technical capabilities of your applications, it's about the ability to use and administer it on an enterprise scale.
I'm sorry, the enterprise experience with trying to manage Firefox is so bad that the idea of a Firefox Operating System is going to cost the poor person who suggests it their reputation at best.
I started to dislike Firefox's layout when they moved the "Home" button to the right side...away from the tabs and menu where my mouse would normally be.
Visually it looks really nice and it's not being developed by an advertising agency so that's a huge bonus. I'm definitely going to give it a try.
Comment removed based on user account deletion
So are you saying my HTML5 app will only work well on one mobile platform?
Will all those nice design principles be applicable directly to Android, iOS and WP?
You sound more like a memory chip salesman than a software developer actually.
Why would you say that ? It can run on an Android Linux kernel or even the less obvious choice of running it on the Raspberry Pi:
https://developer.mozilla.org/en-US/docs/Mozilla/Boot_to_Gecko/B2G_build_prerequisites
http://www.tomshardware.com/news/Firefox-OS-Mozilla-Raspberry-Pi,16883.html
You did not read Slashdot yesterday ?:
http://mobile.slashdot.org/story/12/07/06/1551237/telefonica-shows-prototype-firefox-os-phone
The plan is to release a phone early next year:
http://crave.cnet.co.uk/mobiles/firefox-os-will-be-on-zte-phones-early-next-year-50009258/
New things are always on the horizon
Why are we still complaining about how much memory ANYTHING takes up anymore?
How much will it take to replace my 1GB Eee900 (with 1G and almost impossible to upgrade to 2) with something which isn't any heavier? A lot more than $79, that's for sure.
Also, how do I plug that $79 DIMM into my android phone?
Your friendly neighborhood software development manager.
Ah, so you're personally responsible for the bloated monstrosities that pass a programs these days.
Please, PLEASE quit your job.
SJW n. One who posts facts.
Here is the entire design document in one sentence:
Make the app look like an Android app, make the home screen look like iOS (but circles instead of rounded squares).
Comment removed based on user account deletion
However it definitely seems a blend of Windows Phone meets iPhone with a little Android thrown in (just kidding).
Even if this fails as a product, it is important to get Apple aware that there are competitive forces out there creating better UI paradigms then "just a grid of app icons".
Mozilla should take great care however because a circle is just a rounded rectangle with corner radius = 1/2 height of rectangle.
I haven't thought of anything clever to put here, but then again most of you haven't either.
This is a mobile OS.
We used to say that all programs evolve until they can send email.
Are we going to need a new saying: "Every web browser grows until it becomes an operating system."
Coder's Stone: The programming language quick ref for iPad
I hope they didn't use the same implementation of malloc/free as the browser:
void free(void *p)
{
}
These are styling principles.
Yes, I know the entire commercial world in 2012 has decided to remap the dictionary and call "design" what the world of commerce in 1982 would have called "style", and "architecture" and "engineering" what the world of 1982 would have called "design". And product designers no longer actually design things but just draw sketches of what the colouring of the pictures on the skin of the 3D printer will look like, while the product architects, who don't have architecture degrees, build flowcharts for the engineers, who don't hold engineering degrees, to build.
But darnit, I still remember when "design" meant how a product works at a technical level, and that's what I came to the article expecting to read, and that's the opposite of what I got.
Get off my perfectly manicured ironically Le Corbusier-inspired post-post-postmodernist lawn.
You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
As someone who switched from a browser based OS, WebOS, to iPhone 3GS, and now to Android, I can tell you I will never go back to another laggy HTML based OS. If anything, I'd like to see Android move away from its VM based apps to something like Apple's native apps. Many apps ran better on my 3GS than they do on my much more powerful S3. Mozilla is going the wrong direction on this one. Native > Java > JavaScript
The whole idea of using HTML, CCS, and JavaScript as the back end technology for a low-end smartphone is nuts. Even the best HTML rendering engines are CPU and memory hogs. CSS was never designed for and is nearly impossible to hardware accelerate, and JavaScript is notoriously difficult to optimize and even the best VMs like V8 run orders of magnitude slower then Native code, while the VM itself takes up a massive amount of memory.
I get that Mozilla wants to put Firefox on a phone. Fine, but first, focus one building a competitive browser. At the end of the day, I want a responsive fast phone, like the iPhone or Galaxy S3, not some dog slow HTML monstrosity.
Mozilla please just invest your limited resources on making a lean browser that can compete with Chrome!
Limited, if any skeuomorphic textures and graphic effects as they are deemed a distraction
Thank Jebus for that...
Obviously, humor is not your strong suit.
Oh, to have mod points...
I think your understanding is wrong. See https://blog.mozilla.org/blog/2012/07/02/firefox-mobile-os/ (yes, it's basically a press release, but it's a convenient one-stop shop for a list of people who have plans, theoretical or not, to ship Firefox OS devices).