Genie 7110 Usability Design Philosophies, Specialise your application for the specific browsers

Page 10

2

Usability Design Philosophies

Creating Usable Applications

Crea ting Us able Applications

When developing applications, these are the most important factors to consider: who the user is, what problems the user is trying to solve, and how to solve them most efficiently. Here are some key principles for creating usable applications:

■Specialise your application for the specific browsers.

To create a more usable application, determine the type of browser in the code. With that information, develop customised versions that increase usability by taking advantage of unique browser features.

■Know your customer.

Users turn to an application to solve a problem and, in some environments, to communicate or be entertained. For instance, the user’s goal might be to purchase an item or to upload and download information while in the field. Build the application to help the user accomplish that goal. If the user’s goal is to find a stock quote, display the quote right away. Use the quote display screen as the entry point to any other information the user might want.

■Get to the value quickly.

Deeply embedded information can cause the user to forget the goal and become frustrated. This frustration will cause the user to avoid the application in the future. Provide commonly used options quickly rather than requiring users to navigate deep menus.

■Limit the application to only necessary functionality.

Remember that the browser does not have the display and navigation capabilities of a PC. In addition, while browsing on the handheld device, the user is looking to find or submit information in the shortest possible time. Scale down the application to meet only the goals of the user, and do not include extras. Provide access to the most commonly used features through menu choices, links, or options.

■Make the application easy to navigate.

Minimise the number of steps it takes to access information. Eliminate or combine cards if this can be done without losing important information, choices, or content. Create multiple paths to access information, if possible. For example, if the application provides weather content, allow the user to search by postal code or city. In this way, the user has the choice of entering a short code rather than long strings, which are hard to type on the phone.

■Make the application consistent.

Consistent applications are “intuitive” for the user. Make the texts descriptive and easy to follow. Labels should explain the actions they cause. Order lists logically, so that items and links are easy to find. Although images and icons provide added information to help make pertinent information stand out, be careful not to overuse them.

■Avoid text entry.

Avoid queries that force the user to enter alphanumeric text. Use menus or partial text searches to avoid or minimise text entry.

6

Genie Application Style Guide

February 2001

Page 9 Page 11
Image 10
Page 9 Page 11
Contents Genie Application Style Guide Legal Notice Contents Contents Style Guide Overview Organisation of this GuideWhy S pecialise? Style Guide OverviewTesting on SDKs Style Guide Overview Usability Design Philosophies Know your customer Usability Design PhilosophiesSpecialise your application for the specific browsers Get to the value quicklyPersonalise the service according to the user Browser TemplatesNo ki a 7110 Browser Template Up to four lines of text or selection items may be visible Browser Proper ties for PhonesApproximately 15 characters can be displayed on one line Number of characters Openwave Browser Proper ties Each phone has a fixed key mapped to backward navigationSecond softkey is reserved for Back Nokia Browser Proper tiesMitsubishi Trium Browser Proper ties Screen displays approximately 18 characters on one lineTimers are supported Phone has a fixed key mapped to backward navigationUsability Design Philosophies Define a backward navigation action for each card Shared Feature Set Navigation GuidelinesNavigation Guidelines ExampleNavigation Guidelines Never define a prev as having no actionDo not rely on font properties to convey added information Always define an action for do type=accept Openwave Navigation GuidelinesLimit the length of labels Navigation Guidelines Example Include a descriptive header of 15 characters or fewerMM/YYYY Navigation Guidelines Nokia Navigation Guidelines Provide an action or link on every cardNever define an action of go or noop to the prev task It is not necessary to define a label for a do type=prevProvide backward navigation for each card Avoid using WML ScriptsMitsubishi Trium Navigation Guidelines Limit the number of softkey actions to oneSort items contextually Shared Feature Set Menu GuidelinesMenu Navigation Do not put more than 9 items on a single cardOpenwave Menu Guidelines Menu NavigationMenu Navigation Allow users to perform multiple actions on a selected item Menu Navigation Do not wrap items on a menu Nokia Menu GuidelinesEach menu should be a list of anchors Mitsubishi Trium Menu Guidelines Menu Navigation Shared Feature Set Calling Guidelines Making Phone Calls from BrowserEmbed code to make the phone call Example Openwave Calling GuidelinesMaking Phone Calls from the Browser Provide a Call anchor labelList the numbers for only one contact on one card Nokia Calling GuidelinesMitsubishi Trium Calling Guidelines Embed code to make the phone callMaking Phone Calls from the Browser Using Multiple Selection Lists Openwave Multiple Selection List GuidelineNokia Multiple Selection List Guideline Mitsubishi Trium Multiple Selection List GuidelineBackward Navigation Shared Feature Set Backward Navigation Backward NavigationBackward Navigation Example Always provide a label for a do type=prevDo type=options label=Done go href=home.wml Provide delete shields Retain data in wizard formsOpenwave Backward Navigation Use activities when neededMitsubishi Trium Backward Navigation Wrap the text Shared Feature Set Text Display GuidelinesDisplaying Text Define the primary label for navigationDefine labels for links Displaying TextDefine a Skip link to go to next related item Use links sparinglyOpenwave Text Display Guidelines Use mobile originated prefetch to access the next cardIncorporate Done softkeys when possible Do not use links on cards used to display resultsNokia Text Display Guidelines Mitsubishi Trium Text Display Guidelines Displaying Text Data Entry Queries Shared Feature Set Data Entries GuidelinesInclude a descriptive label for the do type=accept task Data Entry Queries Do not mask alphanumeric passwordsOpenwave Data Entries Guidelines Define only one action label for entry cardsNokia and Mitsubishi Trium Data Entries Guidelines Data Entry Queries Formatted Entry Fields Shared Feature Set Formatted InputCreate informative titles Restrict the length of the string, if required Openwave Formatted InputPrefill known data Nokia Formatted Input Do not include symbols in the formatsPhone number entries, use appropriate formatting Emptyok=false attribute has no effect Mitsubishi Trium Formatted InputHandsets vary with their treatment of format strings Use a wizard form whenever possible Shared Feature Set Wizard FormsForms Link cards in a logical orderNokia Wizard Forms Openwave Wizard FormsForms Mitsubishi Trium Wizard Forms Do not provide a do action as wellProvide an appropriate label for the primary action Shared Feature Set Elective Data FormsOpenwave Elective Data Forms Display the user’s entered data on the formNokia and Mitsubishi Trium Elective Data Forms Forms Openwave Imag e Suppor t Shared Feature Set Imag e Suppor tIcons and Images Use preloaded imagesMitsubishi Trium Imag e Suppor t Nokia Im ag e Suppor tGif image format is supported Cache Shared Feature Set CachingOpenwave Caching Cache Example Nokia CachingMitsubishi Trium Caching Force the reloading of the deck for dynamic data ExampleCookies and Subscriber ID Shared Feature Set CookiesShared Feature Set Subscriber ID Cookies are not stored in the phoneCookies and Subscriber ID Labels and Links Done Used to allow the user to cancel the operationOK Used to select a menu choice in a choice card Co nfli cti ng Labels and Li nks Labels and Links Back Not used for entry query cardsIdentifying the Browser PerlIdentifying the Browser Java ASPIdentifying the Browser a Java Identifying the Browser Differences between Browser Types in Same Class Tables are formatted acceptably by the browserTable B-2. Mitsubishi Trium browser types Nokia 6210, 6250 and 7110 with version 5.00 or greaterBehaviour Earlier browser type Later browser type Is labelled OK all others are labelled with Differences between Browser Types in Same Class

7110 specifications

The Genie 7110 is a versatile lifting solution designed to enhance productivity and safety in various work environments. Known for its robust construction and innovative features, the Genie 7110 is a popular choice among contractors, maintenance teams, and rental companies.

One of the standout features of the Genie 7110 is its remarkable working height, which can reach up to 11.7 meters (38 feet). This impressive reach allows operators to easily access hard-to-reach areas without compromising safety or efficiency. Additionally, the platform provides a spacious working area, accommodating multiple users and tools, making it ideal for both indoor and outdoor applications.

The Genie 7110 incorporates state-of-the-art hydraulic technologies that ensure smooth and precise movements. The lift's controls are designed for intuitive operation, enabling even inexperienced users to navigate the machine with ease. Safety is paramount, and the Genie 7110 includes several safety features, such as a tilt sensor, a secondary guarding system, and automatic descent when the platform is overloaded.

Another characteristic that sets the Genie 7110 apart is its compact design. Its narrow width allows it to fit through standard doorways and be maneuvered in tight spaces, making it a perfect choice for urban settings or congested job sites. Moreover, the machine can be driven at full height, giving operators the flexibility to move between tasks without needing to lower the platform.

The Genie 7110 also boasts durable construction materials that withstand the rigors of daily use. The heavy-duty steel frame provides stability and strength, while the platform's non-slip surface enhances safety for workers. Additionally, the lift is equipped with high-quality tires that ensure traction and stability on various surfaces.

Powering the Genie 7110 is an efficient electric motor, which offers quiet operation and reduces emissions, making it an environmentally friendly option. The machine’s maintenance-proven design simplifies servicing, reducing downtime and increasing productivity on the job site.

In summary, the Genie 7110 is a reliable and efficient lifting solution that combines height, safety, and ease of use. Its innovative features and technologies make it an essential tool for professionals looking to complete their tasks effectively while ensuring the safety of their teams. Whether for construction, maintenance, or warehousing, the Genie 7110 stands out as a premier choice in the category of aerial work platforms.
Top Page Image Contents