Showing posts with label adobe. Show all posts
Showing posts with label adobe. Show all posts

Sunday, 23 November 2008

Future of Mobile 08: Open Screen Project

Matthew Millar — Director of Mobile and Devices EMEA, Adobe

  • generations of Adobe platforms: PostScript, PDF, Flash, AIR
  • Now see two development areas: Client + Cloud, Device + ??
  • Trying to balance between client & cloud — AIR
    • Rich application on client, but taking advantage of the cloud
  • Massive growth in Flash-enabled devices — expecting to surpass 1 billion next year
    • But 1 billion nowhere near enough in mobile
    • Only 20% of devices, compared to Nokia S40,S60 J2ME 40% Device Platform Fragmentation
  • Open Screen Project:
    • use Flash & AIR as technology foundation Adobe Media Player screenshot what a ridiculous screenshot! How high is the resolution on the phone on the right!
    • Removed license restrictions & fees on use of SWF & FLV/F4V specs
      • Other people could create their own Flash player
    • Working to make Flash Player & AIR updateable over the air
      • No use having old players out in the market
    • Flash Lite player now open too
      • available to developers as OTA download
      • supports S60 and Windows Mobile
      • Now beta, live in 2009
      • See adobe.com/godistribute
    • ARM & Adobe optimizing Flash Player 10 for ARM v6 & v7
      • Full platform, not just Lite
    • Q: What about connecting to hardware APIs, like SonyEricsson Capuchin?
      • Adobe very supportive of Capuchin
      • Will see other manufacturers doing same, e.g. Qualcomm exposing BREW to Flash
    • FlashCast Channels
      • Project with Telenor in Sweden
      • Expecting to launch commercially in Q1 next year, first in Sweden then in other Nordic territories

Tuesday, 8 April 2008

MomoLondon: Mobile User Experience

Last night’s Mobile Monday London was themed on the Mobile User Experience.

Taptu — Steve Ives (CEO & Founder)

  • Live since last October — preparation since April
  • Aim to get mobile search used several times a day rather than
  • Company expertise: mobile user experience (ex-Trigenix) + search algorithms (with experience from Cambridge Computer Lab)

UI design process

12 months, 14 user studies (2 day sessions with 10 users spending an hour each)

  1. concepts
  2. paper prototypes
  3. device prototypes (static pages)
    • used for user studies
  4. two other steps… (can anyone fill them in here)

Main tenets:

  • don’t assume
  • listen to users
  • iterate often

Personas

Built up a fair amount of detail about 4 personas.

  • 20, iPod generation
  • 32, careerist power user
  • 23, unwired social (not a lot of access to the internet during the day or evening)
    • mobile internet is primary access to internet
    • particularly large in Asia
  • 27, digerati — bloggers, influencers
    • 10% size of others but very influential

Prototypes

Paper prototypes done by photocopying framework with title, options and back then annotated.

Device prototypes — high fidelity, device-specific, pixel perfect (no software engineering required)

Design

Three core families, each with different user experience design

  1. low: 176x220
  2. mid: QVGA
  3. high: iPhone

Graphic design comes from within company — authentic and fast turnaround

UE Testing

They set up a portable user-experience lab, since testing users in London (and they’re based in Cambridge). This consisted of a laptop, a portable mixing desk, two video cameras and a microphone. They could take this to any meeting room and hold user testing.

Two cameras: one aimed at user’s face, other mounted on handset; both mixed & recorded together with a separate microphone. Results in movie showing user reaction in a picture in picture format.

Totally regular event to run a user study — expensive and time-consuming, but have committed to do this.

Human Factors International — Scott Weiss

He wrote a book: “Handheld Useability” in 2002

Moving to “persuasive design”: are your users going to come back?

A good way to determine persuasive design is eye tracking, but this doesn’t work on mobile as the eye trackers require a stationary device.

“The minimum number of design & feedback cycles is 3”

If user testing a phone, don’t sit right next to them and breathe down their neck. Instead, sit opposite them and make them show you the phone if they need to.

Moving from design-time to runtime: Future Platforms — Bryan Rieger

Bryan was addressing the disconnect between designers and developers during and towards the end of the design process. The designers come up with something that looks wonderful and flows beautifully, but if the developers just take the assets directly from these mockups, then the application would run like a dog on mobile. The assets would be too large to load quickly and the device would run out of memory.

  • Think about assets, custom fonts, icons for different states.
  • Specify paddings, margins and use native drawing capabilities.
  • Use composite images — combine resources in device rather than beforehand.
    • e.g. transparency overlay, shading for selection, etc

For example, FP reduced the resources in the Locomatrix app from 12K to 2.87K — massively improved performance and could now work on a lower-memory device such as a Motorola PEBL.

Control Java design based on constants provided in a resource file.

The designers and the developers must work together.

Some of this can be used in mobile web as well, especially if the device has CSS2 & CSS3 capabilities.

Panel session notes

“Institutionalizing useability” — book on Amazon for getting user testing introduced into a company

WebX — sharing presentations for remote teams

Design for the mass market if you want to be successful — this means that the interface will need to work on constrained devices (e.g. pepperoniti — most widely used mobile social networking tool, has very primitive UI)

How do you design for location-based interactions? Or RFID or other? FuturePlatforms are trying but are struggling — the tools don’t help, so they’re using sketches and notes on the walls.

In Apple, the chief designer reports to the CEO — that doesn’t happen very often in other companies.

What’s your good (and bad) UI experiences?

  • Marek: N95 Google Reader
    • simple, one graphic, making best use of browser, loads very quickly
  • Scott Weiss: bad user experience — RAZR, almost destroyed a company
    • four soft keys
    • took off menu soft key too late
    • industrial design was spectacular, but user experience was terrible
  • Taptu:
    • BMW idrive — terrible
    • Phillippe Starck video on TED: simplifying product design
  • Bryan Rieger: love the iPhone
    • some of the worst user experiences coming out of Korea to try and copy it (LG & Samsung)
    • touch screen, but some of the screen isn’t touch sensitive and the buttons change under your fingers

Friday, 4 April 2008

OverTheAir: WICD -- Daniel Herzog (Vodafone)

Two profiles: WICD Full & WICD Mobile. Full gives you SVG full and full XHTML, CSS & EcmaScript.

Mobile requires EcmaScript 3rd edition Compact Mobile (no eval) as well as CSS & XHTML

Browsers that support it:

  • Opera 9.5 beta 1
  • Safari 3.1
  • Firefox 3 beta 5 (though not officially, yet)

Big feature in WICD SVG is rightsizing

  • if the browser just defines the width as a percentage
  • go ask the SVG for its aspect ratio
  • assign the height appropriately

WICD also includes media queries. These include things such as dpi which can be very useful on smaller devices. Opera will update media queries in real-time when resizing the browser window :-)

Can interact with SVG and XHTML — e.g. hover over a link and get the SVG to respond immediately; also create SVG animated circular radius over a clicked point on a google map.

SVG has Javascript within it so can encapsulate functions within. Can then address each object’s methods from javascript in the XHTML page.

SVG:

Object.prototype.myAnim = new animatorClass();

XHTML Javascript:

document.objectOfTypeMyAnim.animatorClassMethod(params)

At the moment, designers have Illustrator to create static images. Animations are harder to create. Debugging is now easier using Firebug. There’s another tool called Inkscape available for Linux, Mac & Windows. It’s getting better all the time.

Thursday, 14 February 2008

Experiences from Mobile World Congress

So, back from Barcelona and I’ve got a few minutes to gather my thoughts on what I saw. It’s a lovely city and surprisingly warm in February — we even found time to lie on the beach and enjoy the surf!

Samsung

The new Samsung F480 is trying to be an iPhone beater, complete with a touch screen and only three buttons, but they haven’t quite got the interactiveness of the UI. The interface is still a barrier between your finger and what you want to do.

One cool feature is the widgets screen. You can drag your chosen widgets on to and around the screen from the widget dock (or off the screen again). However, the widgets are built-in to the phone and there’s no facility to write new ones, nor to have widgets that connect to the net (as yet…).

The big adverts were for the SOUL, or U900. I found this phone really hard to use. It uses a four way button with a screen behind it to control navigation — good idea following on from the Optimus keyboard, but it wasn’t very responsive. I often found myself scrolling too far or not enough.

Sony Ericsson

Sony Ericsson seem to have got a really good idea of the people who actually use their phones and are continuing to target them very effectively. They were displaying lots of phones differentiated by use cases rather than by features. They’ve got phones for people who mainly want a music player, phones for people who mainly want a camera and phones for business people who want to sync their contacts and diary but don’t want a computer in their pocket. All of these still have the other features present but they’re less emphasised. It feels like a much better strategy than Nokia’s “let’s put everything in one package and let each user and each operator figure it out differently” approach. And the phones keep on getting slimmer and smaller (again unlike Nokia…).

As per David Wood from Symbian’s comments at MoMo London last week, Sony Ericsson are migrating their Symbian phones towards the lower end of the market just like Nokia. However, unlike Nokia they’re also keeping Ericsson Mobile Platform phones with the same or more capabilities and the lower-end Symbian candybar phones have been carefully designed to be simpler to use than the existing M600 and P-series. They’ve got touch screens, but you can quite easily get around using just the keys, leaving the stylus almost as an optional extra.

One surprise for me was their new Windows Mobile phone, the Experia X1. Why have they gone for Windows Mobile? They were touting their new UI which they couldn’t yet demonstrate… supposedly letting developers create a whole new way of using the phone for different use cases. For example, you could set up your standby screen to be your Google desktop, complete with connected widgets. Is this something they couldn’t do with UIQ?

Nokia

I didn’t spend long on the Nokia stand, but I couldn’t see anything particularly new.

I found out later than the new N78 has an FM transmitter! Could be interesting for social interactions… It’s designed to transmit to your car stereo, but I wonder how tweakable it is.

NTT Docomo

The advantage of having a Mobile World Congress is that you get to see how the mobile market works in other cultures, including those that have been consistently ahead of ours in mobile technology. Japan’s NTT Docomo is one of the leaders here, and they had several displays that gave a new viewpoint on what we do.

  • Underwater phone: mobiles that are waterproof “especially for use in the kitchen”. No great technological advances here, but the sight of a phone in water with bubbles going round it was aesthetically pleasing — who hasn’t wanted to do this to their phone at some point :-)
  • Children’s phone, complete with a wristband phone finder: press the phone finder and your phone will make a noise. The phone can also be used as a safety alarm and can locate the child if they’re in trouble.
  • map i-appli: Direction-finding specifically including your train journeys
    “walk -> ride train -> walk … Complete support of railway networks”

The main thing that strikes me with Japanese interfaces is that they’re really text heavy. The pictoral nature of the language seems to mean that people are used to cramming a lot of information into a small space and the resulting interfaces look almost messy from a Western perspective.

LiMo Foundation

Showing off a fair spread of phones running on LiMo (mobile Linux). Including about 8 Motorola phones and not just the top-end weird ones either — one of them was a RAZR2 and another was a PEBL.

Shame that they haven’t got a decent UI yet…

Danger

Had their own pavilion on the avenue. Useful device with always on connectivity running Java apps written to JavaME with their own specific API extensions. Apps can be running all the time and can receive push events from the network — aimed at IM and similar.

They wouldn’t tell me how many Sidekicks are in the market in the UK (sold by T-Mobile complete with £7.50 web’n’walk as much internet per month as you want). Does anyone know?

Microsoft have just bought Danger (Andy Rubin’s old company)… Is this to compete with Android (Andy Rubin’s new platform)? Will this affect their Java-centric approach?

Other tech

  • Nuviphone
    Lots of advertising leading to a stand with four Nuviphones under glass, all displaying the same two screens (pixel identical). No UI demonstration and no information other than the press releases. Perhaps there’ll be an announcement later in the week…?
  • moduthe modular handset looks like an interesting idea. Other than the little module itself, the handsets they had were all mockups.
  • Readius phone with a folding screen — finally happening after years of promise.
    The screen’s great when it doesn’t have to change — just like paper with no backlight required.
    Not so good at changing though — it’s a very mechanical process and the whole screen has to invert and flash white before it can display something new

Mobile Testing

We’re doing more and more device testing at Kizoom, and it’s not getting any easier. I went around the software developers in Hall 7 trying to find ways of testing mobile applications, both Java-based and browser-based. Here’s some solutions:

  • Mobile Complete
    Scriptable — really good — check it out
    More devices for UK coming, but slowly. Depends on demand.
    Each new device takes 10 working days to set up. The iPhone took at little longer…
  • Zandan — emulate browser but test real network using modems
  • Adobe DeviceCentral — Flash only?
  • Yospace still running device emulators (though don’t advertise it too much any more)

Enough

Of course, thanks to the guys who invited me: the makers of J2ME Polish. They’ve just released version 2.0 which really does enable you to write once and build to most devices, from MIDP 1 through MIDP 2 to Android, Windows Mobile and even a pre-release output on an iPhone!

Friday, 16 November 2007

Future of Mobile: Next Generation UI

by Matt Millar (Adobe)

  • How do we make the content richer?
    • Especially for those people who are paying more for their device/contract
  • 77% of iPhone users said they were "very satisfied" with their device
    • Highest satisfaction level for any mobile device
  • The experience should be expressive, memorable and desirable

    • "Hey, isn't this great! Let me show it to you."
  • Expecting same quality of content as get on TV, PC, etc
    • The mobile is not the only way to get hold of (your) content
  • Animation helps guide and draw the eye towards things of interest
  • Transitions help ease context switches, avoid users losing focus
  • FlashLite 3 will be coming out on first devices Jan/Feb 2008

    • Supports video & up to Flash Player 8 content

    • Most content published on the web seems to be Flash Player 7 & 8

  • Not investing that much in SVG -- going for Flash instead
  • Integration with address book etc: nothing announced at the moment, but may be privately
  • Touch interaction is supported with Flash Lite 2 but devices do not necessarily support the hooks (even the ones with a touch interface...)
    • e.g. LG Prada has a touch-enabled Flash Lite player
  • There are more Nokia S60 devices in the market than there are Macs