Example: metaclient://g/?k=compositephone;metaclient.com/wap       The phone and browser being simulated are composites of the most common characteristics of the phones that most people use. This phone doesn't map directly to any particular manufacturer, but is somewhat of a "lowest common denominator" combination between Nokia and ATT&T phones. More specific simulations can be found in the Cell_Phones.bwml set. This device/browser consists of a passive matrix blue-tinted sceen, a numeric keypad, a four direction keypad, and two buttons for WML interaction; accept and cancel. (The WML mappings for the accept and cancel buttons, along with other deails, can be found in the .MCB file.) The device also has a screen that is larger than most phones, for easier development. Some good WAP sites are: mobile.yahoo.com, wireless.ibm.com, wapwarp.com.

Example: metaclient://g/?k=uaprofnokia3350;metaclient.com/wap       MetaClientTM can build browsers from UAProf profiles . Many UAProf profiles are included with MetaClientTM, this one is the Nokia® 3350 profile. The MetaClientTM distribution includes 64 UAProf profiles, each describing different wireless devices.

Example: metaclient://g/?k=uaprofnokia9110i;metaclient.com/wap       An example of MetaClient's ability to build mobile phone simulations based upon UAProf profiles.

Example: metaclient://g/?k=unofficialmotorola120c;metaclient.com/wap       This is an unnoficial simulation of a WML browser running on a Motorola® 120c phone. This simulation is generated by MetaClientTM from an MCB (MetaClient Browser) file. This phone is different from most others because it's directional keypad is only two-way: up and down. As a result, the "*" and "#" keys in this simulation have slightly different mapping to allow for left and right movement while entering text. (This may not be true of the actual phone). Some good WAP sites to try are: mobile.yahoo.com, wireless.ibm.com, wapwarp.com

Example: metaclient://g/?k=nokia3650unofficial;metaclient.com/wap       The Nokia®3650 is an unusual phone. It has an unusual interface, an unusually large, color screen, and it can take digitial photos. It's browser is capable of handling both XHTML Basic and WML, and so is this simulation. Some good WAP sites to try are: mobile.yahoo.com, wireless.ibm.com, wapwarp.com.

Example: metaclient://g/?k=accessibilitycheck;metaclient.com       This code scanning browser checks a page for accessibility problems that may make it unusable for disabled people. Disabled users are people who have phyisical impairments such as poor vision or blindness, as well as users who are temporarily disabled, such as users whare are browsing the web in cars or over the phone.

Example: metaclient://g/?k=searchspider;metaclient.com       This code scanning browser is a simulation of how an internet search engine spider might interpret a web page. This browser is a full implementation of the Talking Search Spider tool at talkingspider.com.

Example: metaclient://g/?k=spamspider;metaclient.com       This code scanning browser is a simulation of how a spam spider (or "spambot") may consume a given web page. Spam spiders are looking for email addresses and personal addresses, with the intent of recording them for a subsequent unsolicited advertising campaign.

Example: metaclient://g/?k=wellformed;metaclient.com       This browser checks a web page for well-formedness.

Example: metaclient://g/?k=validatexhtml;metaclient.com       This browser validates a web page to three XHTML DTD's.

Example: metaclient://g/?k=variableheaders;metaclient.com  Example: metaclient://g/?k=variableagent&p=http;arg?accept=text%2fx-wap.wml&user-agent=UP.Browser;wapwarp.com  Example: metaclient://g/?k=variableagent&p=http;arg?accept=*%2F*&user-agent=Mozilla;wapwarp.com        The arguments contained in the MURL, MetaClientTM will determine what the values of the HTTP "User-Agent" and "Accept" request headers will be. The results are displayed as text. This is a quick way to see what flavors a web server will provide, depending on what browser or device is making the request.

Example: metaclient://g/?k=chtmlpalm;metaclient.com       This browser reduces input HTML into CHTML. This is the behavior of most PDA browsers. In this example, the screen and scrollbars resemble that of an older Palm device. The screen is 160 by 160 with a monochromatic brown tint. Within the past few years, a number of other PDA's have been developed, based on the Palm OS. Companies that produce Palm OS based devices inclide Handspring, IBM, Kyocera, Sony, and Symbol. Many mobile phone manufacturers now sell phones with Palm OS built in. There was also never one dominant browser for the Palm OS that spanned accross the years that it existed.

Example: metaclient://g/?k=compositeppc;metaclient.com       This browser reduces HTML into XHTML Basic (http://www.w3.org/TR/xhtml-basic/). , to simulate the behavior of many PockeyPC browsers. The Pocket PC is among the most popular types of PDA device. Most of the Pocket PC® brands have essentially the same screen/browser capabilities.