Intermec 730 User Manual page 41

Here are some helpful tips to keep in mind when designing web pages for
iBrowse.
Force the user to follow a specific path
In most situations, the HTML should lead through a narrow path for
entering or processing information. Pages designed for the desktop browser
usually have dozens of links providing a myriad of paths on which to
continue. In the business environment, it is usually more useful to force a
select path. The limited screen area is also a factor.
Design pages to fit on one screen
Scroll bars reduce screen size by at least 15 pixels. On a 700 Color, CK31,
CK60, CN2A, CN2B, and CN30 computers, the display is approximately
235 pixels wide by 290 pixels high. For CK30 computers, the display is
about 160 pixels wide by 140 pixels high. Design screens and images to fit.
Load quickly with low throughput
In a wireless environment, throughput is affected by signal strength. The
lower the signal strength from the access points, the slower the throughput.
For this reason, it is best to design the pages to be as small as possible. Use
graphics sparingly. Find ways to split large pages into two or more pages
that the user can step through. This prevents the user from long waits when
they are in a low coverage area. Optimally, the pages are transferred at 11
Mbps but transfer speed can be as low as 2 Mbps.
Avoid frames and bookmarks
Due to limited screen space and throughput concerns, frames and
bookmarks are not recommended. A page with two frames downloads three
different web pages. A page with bookmarks takes longer to download and
the scroll bar that is at the side of the screen could easily confuse a new user
if they accidentally scroll to a different section of the page. META tags that
work on a per-page basis do not function in frame and bookmark pages.
Support both keyboard and stylus input
When possible, navigate through the web pages using the keypad because it
is more convenient and efficient. The stylus is often lost by users, which
then requires the use of a finger or another object, and a substitute is rarely
small enough to tap on the correct item without several tries. You can set
the META Tag OnKey feature keys on the keypad to run a JavaScript or
navigate to a new page with a single keystroke. You can set up a screen full
of links like a menu so each link is assigned a number. The user could then
press that number on the keypad instead of having to tap on the screen.
When a user is required to tap on the screen, make sure the button or link is
large enough for easy selection with a finger.
Limit the use of JavaScript
Web applications are, by definition, thin clients. Try to push most, if not
all, data processing to the back-end system. Overloading a Windows CE
computer with JavaScript causes performance degradation.
40 iBrowse User's Guide