Ericsson R380 manual General Usability Aspects

Page 6

GENERAL USABILITY ASPECTS

When it comes to designing any kind of electronic service, simplicity is the key to gaining acceptance and appreciation from users. Simplicity is even more important in a mobile environment since the user often needs to concentrate on other things as well as using the terminal.

Keep information and text short and meaningful. Since overview is crucial, keep lists and menus fairly short. Do not force the user to scroll through more than 4-5 displays (corresponds to 25-35 lines). Try to avoid long words and abbreviations because the screen real estate is limited. Hard to understand abbreviations might be misinterpreted. Try to use short and meaningful words instead.

Remember that there is a size limit to what can, in practice; be sent to the terminal in one deck. Keep the size of the decks at less than 3.800 bytes (images not included). Images should not be more than 3.800 bytes per image. Use images to supplement text rather than replace it.

Depending on service, it could be wise to stay well below the above-mentioned limits from a usability perspective. We recommend user testing on all services being done in a live environment.

Use few levels in menu hierarchies since:

1.The user can easily get lost in complex and deep menu systems.

2.Depending on the bearer and the structure of the WML code, it could be slow to move down through a multi-level menu system.

Use header texts since headers are used as card titles, which describe the contents of a card. Card titles should say something about the context the user is currently in. Card titles are also a navigational aid for users, helping them to remember where they are in an application.

Use links to access more information. Links are a powerful tool for linking different information items and preventing long pages of text.

Tip: A R380 browser can be identified at the server side by the contents of the HTTP/1.1 header User-Agent request field. At the server side knowledge of the identity of the requesting browser then can be used in order to start WAP services tailor-made for this particular browser.

The above-mentioned identity of the R380 browser is: “R380 2.0 WAP1.1”

Unfortunately no standardized method exist in order to pull out this information. The methods are different depending brand and version of the Internet server used. Please consult your Internet server documentation for details on how to make use of the information contained in the HTTP header fields.

4

Page 5 Page 7
Image 6
Page 5 Page 7
Contents Mobile Phone R380 Design Guidelines For WAP Services Page Contents Who Should Read this Guide? Overview of ContentsPreface Related PublicationsTerminology AbbreviationsDefinitions General Usability Aspects Browser Area User Interface IssuesBrowser Display Card Title BarOn-screen Keyboard NavigatingToolbar Using Text Design ComponentsFont Size and Font Style Line Spacing and Line Breaks Text formatting exampleLine break example Paragraphs Paragraph exampleIndented Paragraphs Fieldset exampleSingle Choice Lists Using Select ListsCard Title Bar MultipleMultiple Choice Lists Option elementAn example of a single choice list Using Buttons Optgroup elementAn example of a multiple choice list Type Using Input FieldsLabel Do exampleUsing Images ValueAn input example Vspace AltSrc HspaceUsing Hyperlinks An image exampleHyperlink example Using Images as Hyperlinks Using TablesAn image hyperlink example Align Columns Polar Weather table examplePizza Penguin table example Pizza Penguin Example
Related manuals
Manual 7 pages 50.51 Kb

R380 specifications

The Ericsson R380, launched in 2000, stands as an iconic device in the annals of mobile telecommunications. Often celebrated as one of the first smartphones, the R380 was distinguished by its innovative design and features that laid the groundwork for future handheld devices.

One of the defining characteristics of the Ericsson R380 was its form factor. It featured a clamshell design, which provided a compact and portable solution for users. When closed, the device protected the screen and keypad, and upon opening, it revealed a large monochrome LCD display. This dual-display feature made it easy to use, and its robust construction ensured durability in everyday scenarios.

The R380 ran on the Symbian OS, which was a pioneer in mobile operating systems. This allowed the device to support a range of applications, something that was still emerging in the mobile market at the time. The operating system enabled users to manage contacts, calendar appointments, and tasks effectively, enhancing productivity and organization. The device also offered SMS and email functionalities, adhering to the growing demand for mobile communication.

In terms of connectivity, the Ericsson R380 was equipped with GSM technology, which was becoming the standard for mobile networks. It allowed users to enjoy clearer voice calls and better coverage compared to older technologies. Additionally, the phone supported GPRS, enabling users to access the internet and send data more efficiently, a significant leap forward for mobile users.

With a focus on personalization, the R380 allowed users to customize ringtones, wallpapers, and other settings to create a unique user experience. The phone's battery life was commendable for its time, providing extended usage between charges, which was crucial for mobile professionals.

Though it may seem basic by today’s standards, the Ericsson R380 represented a technological breakthrough in the early 2000s. Its integration of telephony and computing set the stage for the smartphones that would follow, showcasing a glimpse of the mobile future that consumers would come to expect. The legacy of the R380 continues to resonate, marking it as a pivotal player in the evolution of mobile technology.
Top Page Image Contents