mobilite

mobsessed

Page history last edited by Nicola 1 yr ago

Designing for device independence, is it possible, can you achieve low and high-resource design at the same time - including:

1. Backwards compatibility - text, SMS messaging and SMS web

2. Future proofing - multimodal web and multimodal messaging. There are some resources, around about multimodal learning Cisco paper , articles . Multimodal can mean different things to different people - this project looking at multimodal web & messaging only, so I understand it as….a future extension of mobile web and learning - giving people choice over how they interact and use information and in this instance, looking at voice-text only.

A multimodal browser will allow multiple types of input or output using a range of options - keyboard, touch, voice etc I will be looking at Xhtml + Voicexml (x+v) markup languages. I first heard about Voicexml from mobile design expert Barbara Ballard who has written lots about class based design and mobile usability - what kinds of apps are fit for what purposes and contexts etc. Barbara's book - designing the mobile user experience

3. Stand alone app vs web app - in 2008 which is going to be better and for what purpose in terms of creating, distributing and users accessing….who is the target audience for the app and who is creating it, using what device.

4. Mobile app vs pc app - is it needed at all - as above with multimodal what is the context and need.

5. Development of app - open source (Android) v …anything else which isn’t !

Mobilite

mobsessed:blackberry

mobsessed:independence