|
This section of Mobinomy.com
provides resources for creating dotmobi web sites and web pages. Mobinomy is an
online resource for the mobile economy.
Keywords for this page: .mobi web site, designing dotmobi
web pages, developing .mobi compatible web pages, creating .mobi web sites, dotmobi
web design
..
..
Creating dotMobi Web
Sites
All content for this section is referenced from dotMobi
Switch On! Web Developer Guide from the dotMobi Consortium
Mandatory Registrant
Rules
1. XHTML Mobile Profile
When a dotmobi web site is accessed using a URI that
consists only of a second-level domain name (e.g. example.mobi) or consists
only of the 'www' third-level domain name (e.g. www.example.mobi), the page
delivered as a response must be encoded in XHTML-MP 1.0 [XHTMLMP]
unless the device is known to support an alternative choice of markup. If the
site provides its home page by redirection then all intermediate pages that
are delivered in the course of the redirection must comply with this rule.
2. Second Level Domain Site
Domains that operate a site at www.example.mobi must also
implement a site at example.mobi.
3. Use of Frames
Do not use frames (standard or inline) unless the target
client is known to support them.
Dotmobi Best Practices
1. Overall Behaviour
- Thematic
Consistency of Resource Identified by a URI - Ensure that content
provided by accessing a URI yields a thematically coherent experience when
accessed from different devices.
- Exploit
Client Capabilities - Exploit device capabilities. Do not take a
least common denominator approach.
- Work around Deficient Implementations - Take reasonable
steps to work around deficient
implementations.
- Testing - Carry out testing on actual devices as well as
emulators.
2. Navigation and Links
- Page Content - Ensure that content is suitable for use
in a mobile contexURIs of Site Entry Points - Keep the URIs of site
entry points short.
- Navigation Bar - Provide only minimal navigation at the
top of the page.
- Balanced Structure - Take into account the trade-off
between having too many links on a page and asking the user to follow
too many links to reach what they are looking for.
- Navigation Mechanisms - Provide consistent navigation
mechanisms.
- Access Keys - Assign access keys to links in
navigational menus and frequently accessed functionality.
- Link Target Identification - Clearly identify the target
of each link.
- Note the target file's format unless you know the device
supports it.
- Image Maps - Do not use image maps unless you know the
target client supports them effectively.
- Refreshing, Redirection and Spawned Windows - Do not
cause pop-ups or other windows to appear and do not change the current
window without informing the user.
- Do not create periodically auto-refreshing pages, unless
you have informed the user and provided a means of stopping it.
- Do
not use markup to redirect pages automatically. Instead, configure the
server to perform redirects by means of HTTP 3xx codes.
- Externally
Linked Resources - Keep the number of externally linked resources to a minimum.
..
..
3. Page Layout and Content
- Page Content - Ensure that content is suitable for use
in a mobile context.
- Use clear and simple language - Limit content to what
the user has requested
- Page Size - Divide pages into usable but limited size
portions. Ensure that the overall size of page is appropriate to the
memory limitations of the device.
- Scrolling - Limit scrolling to one direction, unless
secondary scrolling cannot be avoided.
- Navigation Bars etc. - Ensure that material that is
central to the meaning of the page precedes material that is not.
- Graphics - Do not use graphics for spacing. Do not use
images that cannot be rendered by the device. Avoid large or high
resolution images except where critical information would otherwise be
lost.
- Color - Ensure that information conveyed with color is
also available without color. Ensure that foreground and background color
combinations provide sufficient contrast.
- Background
Images - When using background images make sure that content remains
readable on the device.
4 Page Definition
- Title - Provide a short but descriptive page title.
- Structural Elements - Use features of the markup
language to indicate logical document structure.
- Tables - Do not use tables unless the client is known to
support them. Do not use nested tables. Do not use tables for layout.
Where possible, use an alternative to tabular presentation.
- Non-Text Items - Provide a text equivalent for every
non-text element. Do not rely on embedded objects or script.
- Image Size - Specify the size of images in markup, if
they have an intrinsic size. Resize images at the server, if they have
an intrinsic size.
- Valid Markup - Create documents that validate to
published formal grammars.
- Measures - Do not use pixel measures and do not use
absolute units in markup language attribute values and style sheet
property values.
- Style Sheets - Use style sheets to control layout and
presentation, unless the device is known not to support them. Organize
documents so that they may be read without style sheets. Keep style
sheets small.
- Minimize - Use terse, efficient markup.
- Content Types - Send content in a format that is known
to be supported by the device. Where possible, send content in a
preferred format.
- Character Encoding - Ensure that content is encoded
using a character encoding that is known to be supported by the target
device. Indicate in the response the character encoding being used.
- Error Messages - Provide informative error messages and
a means of navigating away from an error message back to useful
information.
- Cookies - Do not rely on cookies being available.
- Cache Headers - Provide caching information in HTTP
responses.
- Fonts - Do not rely on support of font related styling.
5 User Input
- Input - Keep the number of keystrokes to a minimum.
Avoid free text entry where possible. Provide pre-selected default values
where possible. Specify a default text entry mode, language and/or input
format, if the target device is known to support it.
- Tab Order - Create a logical order through links, form
controls and objects.
- Labels - Label all controls appropriately and explicitly
associate labels with controls. Position labels so they lay out properly
in relation to the controls they refer to.
Sources: dotMobi Switch On
Guides & Mobile Web Best Practices from W3C
..
..
.Mobi is the TLD (top level domain) for mobile compatible
web sites. These web sites are expected to make browsing using mobile and
cellular phones much easier and simpler than the available web sites today.
Mobinomy provides information, data, directory and web
links resources for the mobile, cellular and related areas. It is intended to
be useful for people wishing to get mobile phone industry related web sites,
information, news, trends, reviews, web links & web site resources, and
more. It will make an effort to provide resources on cellphone &
accessories suppliers & manufacturers, commercial info such as prices,
great deals & price info for the buyer/buyers, mobile phones
tutorial/tutorials, mobile technology guide/guides, mobile & wireless
tips, faq/faqs on these topics.
|