‪AIR for mobile remote camera app‬‏ – YouTube

AIR for mobile remote camera app – YouTube.

This video shows an AIR desktop app that is connected (peer-to-peer) with an AIR for mobile app running on 4 different devices.

The mobile apps stream video back to the desktop application and the desktop app can be used to send messages to the camera operators.

The devices tested all handle capturing and streaming 640×480 video at 15 fps. The wifi network is having a little trouble keeping up with 4 streams but works well with fewer streams (or when I’m alone on the network).

Mobile Strategies: Untangling Device Contexts and Use Context

Most conversations about mobile strategies include the following two perspectives: limited resources of devices require new technical approaches, and mobile use cases are different and demand unique content and application features.

As we’ve settled into our new multi-device lifestyles, a new perspective has entered into these conversations: finding different content at the same place on different devices is a problem and flies in the face of web accessibility and common sense.

via Odopod – Mobile Strategies: Untangling Device Contexts and Use Context.

A post I wrote on the Odopod blog.

Think Quarterly nails multi-screen content delivery

Google’s new online magazine, Think Quarterly has done a really nice job delivering a reading experience tailored to personal preferences and readable on a variety of screens.

Each story is accessible in three layouts: faux print magazine, large screen web and small screen web. I personally am not a fan of the magazine approach. For me, it comes across as a gimmick and while I like what they are doing with information visualization and layout, I wish they would have just invested that time into their web page layouts and graphics. Luckily, aside from the opening image of florescent neurons and the sudoku puzzel, all content is available in the other layouts.

Those other layouts are well done and are a good example of the One Web concept at play — each story and URL is rendered in a layout optimized for the device you are using, regardless of how you might find the URL. Technically speaking, the servers are redirecting between different URLs based on browser agents. Google is notoriously obsessed with speed and efficiency so it makes sense that they would accept the risks and additional upkeep that come with browser detection in exchange for the leanest possible files.

Following are some galleries of screen shots taken on my laptop, iPad and iPhone. In each I show the table of contents and a story page from the site. 

Good Linking

Here are some interesting links I’ve clicked on recently:

SXSW 2011: Novelty of iPad news apps fades fast among digital delegates: Some good thoughts on the future of news apps. I personally am pulling for open ecosystems rather than isolation.

ifttt the beginning…: I recently started using this very interesting project and not only is the idea nice, it is executed really well. I setup a couple really handy tasks right away and I’m sure that with a little time to think about how to connect my various accounts, I’ll be doing a lot less copy-pasting.

Updated: The South By Southwest Panels, Illustrated [With 20 New Pics]: Brilliant recaps, way more usefull than slides posted without commentary.

Chicago Tribune Election Center: The Chicago Tribune is trying out media queries to adjust page layout based on screen size. They handle phone resolutions in both portrait and landscape mode, which I’m a big fan of and don’t see often enough.

Report Finds Performance of Web Apps Throttled on iOS Devices: If this is not a shortterm thing, it is going to be a big deal for those of us who want to build apps for multiple browsers using Web Standards. John Gruber points out that nothing is actually slower, Safari just got faster and homescreen or native apps using HTML did not get the upgrade. Potato, Potato. If he is right about why things are slow (security), I hope Apple finds a way around it soon.

Complex 3d projections are becoming more common. I really hope this is not a passing fad. Here’s one from Adidas’ all in campaign and if you are going to be in Sydey this Sunday, I’m sure this one will be absolutely epic.

Mobile web test suite

Peter-Paul Koch published an excellent article on the smartphone browser landscape back in December of last year. It has a ton of great information including advice on building a mobile QA suite. As Peter-Paul points out in his ALA article and an excellent series of articles on his blog, dominant browsers vary region to region. Here is a test suite I recently distilled given my U.S. centric needs:

Primary Phones:

  • iPhone OS4: running Safari and Opera Mini
  • Doid 2 (OS 2.2): running Webkit, Opera Mobile, and Opera Mini
  • BlackBerry Torch (OS6): running Webkit
  • BlackBerry Curve (pre OS6): running BB Browser

Others, included dependent on region and site statistics:

  • Nokia n95 (S60): running Webkit
  • Samsung (Bada): running Dolfin
  • Palm Pre (webOS): running Webkit
  • Windows Phone 7: running IE7

This suite does include browsers that don’t do well with JavaScript (Opera Mini and BB Browser) and phones that use a variety of input devices (touch and non-touch devices as well as hard & soft keyboards). I have not included any of the lowest end browsers (NetFront) because we have not yet worked on a site where significant traffic comes from those devices. For the moment, I’m relying on the powers of progressive enhancement to serve the limited traffic we get from those lowest end devices.