Server side redirection script - GitHub
►https://github.com/h5bp/mobile-boilerplate/wiki/Server-side-redirection-script
“Server side mobile redirection script is added at the bottom of the page to detect if user is viewing from mobile device. This is taken from detect mobile browser. If the script detects the user is viewing from mobile phone, they will be redirected to the mobile version of the site.”
Génération perdue : « 52 percent of all children 8 and younger have access to mobile devices at home like a smartphone, video iPod, iPad or other tablet » // Technolog on msnbc.com
►http://beta.msnbc.msn.com/streams/technolog/entries/8507342
Mobile devices have become mini-pacifiers/babysitters for many wee ones: 52 percent of all children 8 and younger have access to mobile devices at home like a smartphone, video iPod, iPad or other tablet, according to Common Sense Media, a nonprofit group that studies children’s use of technology.
Anatomy of a #Perfect #Mobile #Email – Litmus
►http://litmus.com/blog/anatomy-mobile-email
Designing emails that look great no matter where they’re read can be quite the challenge. As more people read email on mobile devices, chances are your recipient might view your email both on a mobile phone as well as on their desktop.
WURFL by ScientiaMobile
►http://wurfl.sourceforge.net
WURFL is a Device Description Repository (DDR), i.e. a software component which contains the descriptions of thousands of mobile devices. In its simplest incarnation, WURFL is an XML configuration file plus a set of programming APIs to access the data in real-time environments. The main scope of the WURFL Project is to be an independent central repository of device information, which Open-Source developers from around the globe can utilize to build their mobile web applications.
Transmedia Design for 3 Screens - Make That 5 (Jakob Nielsen’s Alertbox)
►http://www.useit.com/alertbox/3-screens-transmedia.html
Many people predict that mobile devices will be the only important user #interface #platform in the so-called “post-PC” future. Some even recommend designing websites for mobile first, and then modifying the design for the desktop PC as an afterthought.
I disagree.
Although it makes for a good story to claim that something new will kill the old, things rarely work out that way. As Peter Zollman once said, “with the possible exception of the town crier, a new medium has never put an old medium out of business.” Despite TV, we still have radio — and, for that matter, live theater. In the computer industry, we still have mainframes, and IBM harvests billions each year accordingly.
Si l’on passe outre la « prédictivite », il y a quand même deux grandes tendances qui se dessinent : 1. le web « #desktop » avec des bouts de #mediaqueries dedans, et 2. le web « #mobile » sur des petites interfaces.
On en est encore aux tâtonnements. La preuve avec les sites de journalisme qui pourraient la plupart du temps fort bien s’accommoder d’un zoom sur les contenus ; ça tombe bien, c’est natif à la plupart des navigateurs de #smartphones, le zoom.
Les deux grandes tendances dont je parlais vont avoir du sens avec les services applicatifs en ligne, qui demandent de l’efficacité, là où le surf tel qu’on le pratique sur un ordinateur ne demande pas le même attachement à l’efficacité. Voir à #sérendipité
►http://standblog.org/blog/post/2011/07/25/Some-good-Mozilla-reading
As I said in my Mozilla is changing blog post a week ago, we need to over-communicate. In the spirit of such approach, here are a couple of very important documents I’d like to share with the Mozilla community, users and partners:
Mitchell Baker’s post: Mozilla in the New Internet Era ►http://blog.lizardwrangler.com/2011/07/14/mozilla-in-the-new-internet-era-more-than-the-browser — More Than the Browser. Excerpts:
“The browser is necessary but it is no longer sufficient. There are a number of reasons the Firefox experience needs to expand to fulfill the Mozilla mission.” (...) “the browser is no longer the only way people access the Internet”. (...) “mobile devices mean the entire hardware and software stacks are changing. As a result, the computers many of us use are more closed than they have been in our lifetimes.” (...) “It’s time to expand the Firefox experience to encompass the changing face of the Internet.”
A podcast with Brendan Eich ►http://www.aminutewithbrendan.com/pages/20110721 : We (Mozilla) Fight For the User. It’s in audio format, which makes it a little hard for those whose English is a bit rusty. Luckily, volunteers have made a Transcript of ’A Minute With Brendan’ ►http://piratepad.net/amwb-20110721. It is really thought-provoking! Excerpts:
“Our Mozilla mission obligates us to make the user sovereign over the user’s data and many aspects of the user’s experience, and to keep the web open and interoperable and innovative at all levels”
especially on mobile devices where it’s hard to get Gecko in, or get Gecko distributed, or preloaded as part of the operating system, we can use Webkit. Even use it via HTML and CSS and JavaScript, just use it as an HTML engine, and do some of our new initiatives, new products, new touch-points that users can interact with, as open web apps or as new mobile apps, maybe thin layers of native app around html. Like Firefox Home, the second version that’s being worked on right now.
ARM already is supported well by our JavaScript engine, but we want to be make our code tight on ARM, as fast as possible. We want to avoid using too much battery and while we have a lot of build automation and test automation around our tier 1 platforms like Mac OS on the desktop, Windows and Linux, now we’re going to elevate Android to that position and focus on making it just as awesome.
Because we’re not going to try just one thing, we’re not going to push only the browser, Firefox, onto the mobile devices - we’re also going to try reaching people through lighter-weight means. And then the open web app system is where we hope to make our mark by not just supporting Firefox, but letting open web apps work on all modern browsers.
These quotes are not just random thoughts of two of the most important people at Mozilla, but they expression of what they get from a very important document, written but Jay Sullivan and his team: the Firefox Vision Statement ►https://wiki.mozilla.org/Firefox/VisionStatement , that everyone involved in Mozilla should have read by now.
Voir aussi : ►http://blog.frenchmozilla.fr/index/post/2011/07/21/Mozilla-dans-la-nouvelle-%C3%A8re-Internet-%E2%80%94-Au-del%C3%A0
Working Off the Grid with HTML5 Offline
►http://www.html5rocks.com/en/mobile/workingoffthegrid.html
When your web browser was tied to your desktop, there was never really a time that you couldn’t get an Internet connection whenever you wanted to.
With the significant increase in the ability to access the web on mobile devices — first on laptops, then phones and now tablet devices, it is now easier to access your data and your apps wherever you go. Or is it?
This article was written on a train from London to Liverpool. The train has Wifi, I have a 3G data card, yet I am still never fully connected. Besides, many online tools today can’t handle this intermediate state of connectivity properly.
So how do we solve this problem? It is not simple, but there are steps that you can take today that will let your users use your app whereever they are. Some of these steps have direct solutions implemented in HTML; some will require you to implement some logic, all will help you build a better app.
Understanding the Elements of Responsive Web Design
►http://sixrevisions.com/web_design/understanding-the-elements-of-responsive-web-design
Responsive web design is undoubtedly a hot topic in web design right now. To some degree, the popularity of the concept of responsive web design is well deserved because site users are increasingly diversifying their methods of accessing a website. iPad, iPhone, Android mobile devices, desktops, netbooks — we’re in a time where our web designs must function in a multitude number of ways.
Let us explore the meaning and principles behind responsive web design.
Using #HTML5 #localStorage as a fallback for offline #form submission - MiniApps Blog
►http://miniapps.co.uk/blog/post/using-html5-localstorage-as-a-fallback-for-offline-form-submission
how you might use HTML5 localStorage as a fallback for form data submission when a mobile device is offline without signal.
The demo uses window.navigator.onLine to listen for a boolean value of true or false, determining whether the device is online or offline. When online, the app makes a regular XmlHttpRequest and sends data to a server. If the device loses signal and goes offline, the app queues up and saves submitted data to localStorage as a JSON string. When online connection is next restored, the app then re-sends the queued data to the server automatically. Once the data has been sent successfully, the item is then removed from localStorage.
C’est une bonne idée de conserver en local toutes données avant de les envoyer au serveur, mobile ou pas. #spip