UI Outline for Cell phones.

Uploaded on:
Category: Education / Career
Crossing over the abyss between portable (IMS) and web approaches ... PDA-based UI is being supplanted by new era brilliant cell phones iPhone, Danger, Android ...
Slide 1

Slide 2

Multi-mode correspondences UI Design for Mobile Devices

Slide 3


Slide 4

Current UI outline challenges 3G pre-IMS and IMS interchanges capacities Spanning interchanges modes: from store and forward, to close constant, to ongoing Combining IP and circuit exchanged systems Combining different radios: WiFi and versatile VoIP in big business and shopper use cases Bridging the gorge between portable (IMS) and web approaches

Slide 5

State of play VoIP: Ugly look, innocent configuration, missed open doors Failing to make a more adaptable type of correspondence more appealing Failing to tame PBX, VoIP ease of use, openness Mobile: very cleaned, yet restricted Usability for focal capacities is adequate to make the cellular telephone available to each human Doesn\'t incorporate informing, PoC, and continuous voice in a solitary UE

Slide 6

Our unique objectives Bring the cleaned nature of portable UI to VoIP gadgets Make a straightforward, justifiable PBX UI in the portable structure variable Add IM, interpersonal organizations, and "VoIM" to the blend Focus on correspondence – not music, TV, recreations, area administrations, and so on. Do it utilizing a current way to deal with stages and usage

Slide 7

Target applications 3G and IMS WiFi in portable handsets Enterprise VoIP and FMC Consumer pre-IMS mashups of IP and versatile applications

Slide 8

Enablers The new standard is 3G SoCs Ubiquity of utilizations processors and/or virtualization wreck the cell phone/highlight telephone limit PDA-based UI is being supplanted by new era shrewd cell phones – iPhone, Danger, Android Managed dialect framework (Java) + open OS (Linux) = savvy open cell phones

Slide 9

Technologically comparative Transvirtual SavaJe Java FX Mobile Danger Android Blackberry?

Slide 10

Architecture Good UI is more than shallow: The UI originator makes a world for the client to control Architecture must bolster UI plan objectives Abstracting conventions Translating from conventions to things in a "correspondence world" Make it basic and charming

Slide 11

Abstracting conventions Cover every significant convention for communication and close ongoing informing Provide a predictable API Provide a lucid occasion stream Enables building an all inclusive call state machine

Slide 12

Architecture graph

Slide 13

Keep it straightforward No pop-ups, no discoursed No affirmation, aside from when client information can be for all time decimated You can simply do the thing the screen was intended to empower you to do – no "dead spots" One sort of article for each screen Softkeys are route alternate ways – no "verbs" on softkeys Consistency in forward/back/home conduct

Slide 14

The client\'s interchanges world Services: The versatile system, the IP PBX at work, Yahoo IM, GoogleTalk, and so on. Contacts: Contacts have addresses that can be come to by no less than one of the administrations you utilize Sessions: Conversations with contacts The client can have numerous live sessions, and one current (not on hold) realtime voice session There is a background marked by session Some sessions are top choices

Slide 15

Novel, however well known Sessions bring sight and sound, multi-mode, and multi-administration correspondence into the heart of the telephone UI Sessions are nonexclusive, and have uniform and commonplace conduct Familiar operations on versatile calls work the same way Generic operations on articles Never lead the client down a deadlock

Slide 16


Slide 17

Measuring our advancement Is it straightforward? Is it commonplace? Does the client accomplish more – did we effectively give access to control? Is it appropriate to high-esteem issues: IMS, double mode, 3G, endeavor interchanges? How far into mass-market equipment would it be able to go?

View more...