The Vibration API1 is an API specifically made for mobile devices as they are thankfully the only devices that have a vibrate function. The API allows developers to vibrate a device (in a pattern) for a given duration.
Online Tools for Creative People and Web Developper
Test your website on any screen size including desktops, tablets, televisions, and mobile phones.
Prototype iPhone apps with simple HTML, CSS, and JS components.
Swipebox is a jQuery "lightbox" plugin for desktop, mobile and tablet.
The Serval Project consists of two systems.
The first is a temporary, self-organising, self-powered mobile network for disaster areas, formed with small phone towers dropped in by air.
The second is a permanent system for remote areas that requires no infrastructure and creates a mesh-based phone network between Wi-Fi enabled mobile phones, and eventually specially designed mobile phones that can operate on other unlicensed frequencies, called Batphone. The two systems can also be combined.
We have developed software which we’ve called Distributed Numbering Architecture (‘DNA’) that allows people in isolated or temporary networks to immediately use their existing phone numbers.
We believe that for a phone network to be useful, you must be able to call people, and have people call you on numbers that they know. This is especially true in disasters. This is the magic of DNA: it allows people to use their existing phone numbers, so that others can call them easily.
Plutôt que d’utiliser le SSH ou WINSCP pour récupérer des données sur son Samsung, utiliser le logiciel Kies Air. Kies Air est une application Android préinstallée qui permet à un ordinateur via le wifi de se connecter directement sur celui-ci. Venez découvrir cette application magique.
Kies air permet de connecter le mobile à un ordinateur sans câble via le wifi et par l’intermédiaire d’un navigateur internet comme Chrome, Firefox
Designing websites for smartphones is easy compared to retrofitting those already in place. More than that, it’s embarrassing how, almost eight years after CSS gained practical acceptance, a lack of foresight haunts those of us who write HTML.
Converting older websites to responsive design causes headaches not because small screens are difficult, but because most HTML documents were written under an assumption about screen size. Prior to the iPhone’s introduction in mid-2007, designers could rely on windows at least 700 pixels wide (if they ignored accessibility). Conventions like navigation bars, two- and three-column layout and hover effects evolved to fit the mouse-based wide-screen standard. Designers made their upper left corner logos clickable because it was expected.
There’s a debate over which technique of creating mobile-ready websites is the best.
Google advocates creating responsive web designs, while Jakob Nielsen, a renowned usability consultant, endorses the creation of dedicated mobile sites (but he was subsequently slammed by some web designers).
A third option is also gaining in popularity, where the web server renders the appropriate HTML and CSS from the same URL depending on the device a web page on the site is being requested from (which has been referred to as responsive design + server side components).
This article will discuss each of these methods.
Real-world examples of websites using a particular method are provided under each section.
The mobile device used to test and gather data for all examples is an iPhone 4 using iOS 5.0.
As the web landscape becomes increasingly complex, it's becoming extremely important to deliver solid web experiences to a growing number of contexts. Thankfully, responsive web design gives web creators some tools for making layouts that respond to any screen size. We'll use fluid grids, flexible images and media queries to get the layout looking great regardless of the size of the device's screen dimensions.
However, mobile context is much more than just screen size. Our mobile devices are with us wherever we go, unlocking entire new use cases. Because we constantly have our mobile devices with us, connectivity can be all over the board, ranging from strong wi-fi signals on the couch to 3G or EDGE when out and about. In addition, touch screens open new opportunities to interact directly with content and mobile ergonomics lead to different considerations when designing layout and functionality.
In order to create a site that's truly designed for mobile context and not just for small screens, we want to ensure that we tackle the many challenges of mobile development upfront. The constraints of the mobile context force us to focus on what content is essential and how to present that content as quickly as possible. Building fast-loading, optimized experiences mobile first has a trickle down (or up, depending on how you look at it) effect for tablet, desktop and other emerging contexts.
Mobile devices represent an increasingly large segment of all Web traffic. This traffic is so substantial, that APIs and design practices have been created specifically to cater to mobile devices. An example of this is the W3C’s Battery Status API, which allows an application to inspect the state of the device’s battery. This article explores the relatively new API, and shows you how to begin incorporating it into your applications today.