net mobile

8/7/2019 net mobile

1/21

Introduction to .NET Mobile

Background

Cell phones (mobile telephones) have become part of our life style, and new mobile devices like thePalm Pilot, the Pocket PC, and the upcoming Auto PC is about to be added to the list.

One exciting thing about these new mobile devices is their ability to connect to the Internet and toexecute web applications.

Mobile applications can now be developed to deliver any types of data to any user any place in theworld.

Different mobile devices support different programming languages. Some support WAP and WML,some support HTML or a limited version of HTML, and some support both or a different language.

To support all types of mobile devices, developers must create one different application for eachlanguage.

With .NET Mobile, Microsoft has introduced a new platform for development of mobile applications.

This tutorial is about how to develop mobile applications with an extension to the .NET Framework,called the Microsoft Mobile Internet Toolkit (MMIT) or simply .NET Mobile.

.NET Mobile

.NET Mobile is an extension to Microsoft ASP.NET and the Microsoft's .NET Framework.

.NET mobile is a set of server-side Web Forms Controls to build applications for wireless mobiledevices, like web phones and PDAs.

These controls produces the different output for different devices by generating WML 1.1, HTML 3.2,or compact HTML.

How Does It Work?

The following table shows how the .NET Mobile works:

Mobile Devices

The Internet

Internet Information Server - IIS

The .NET FrameworkASP.NET

.NET Mobile

A web client requests a web page

The request travels the Internet

The request is received by IIS

The request is handled by the .NET framework

The requested page is compiled by ASP.NET

8/7/2019 net mobile

2/21

.NET Mobile handles any mobile device requirements

The page is returned to the client

Software Requirements

To develop mobile applications with .NET Mobile, you must have the following components.

1. Windows 2000 Professional or Server with IIS 52. All Windows 2000 service packs3. The ASP.NET framework4. Microsoft Mobile Internet Toolkit (MMIT)5. Internet Explorer 6.0 or 5.56. Your favorite WAP simulator.

You need Windows 2000 to develop .NET applications. You must also install all the Windows 2000service packs.

IIS 5 (Internet Information Server) is a part of Windows 2000.

If you want to read more about how to install .NET go to our ASP.NET tutorial.

You also have to install MMIT (.NET Mobile) and a newer version of Internet Explorer

Internet Explorer and MMIT can be downloaded fromMicrosoft MSDN.

How To Start

Developing a mobile web application with ASP.NET is very easy:

1. Create an ASP.NET page

2. Include System.Mobile.UI3. Add Mobile Controls to the page

See the details in the next chapter.

The Mobile ASP.NET Page

Mobile Controls are the main building blocks of mobile applications.

Mobile Controls are similar to Web Controls in ASP.NET.

If you are not familiar with ASP.NET development, you should leave this tutorial and study ourASP.NET tutorial first.

This ASP.NET page displays Hello W3Schools as an WML card in an WML enabled cell phone:
http://www.w3schools.com/aspnet/default.asphttp://msdn.microsoft.com/http://msdn.microsoft.com/http://www.w3schools.com/aspnet/default.asphttp://www.w3schools.com/aspnet/default.asphttp://msdn.microsoft.com/http://www.w3schools.com/aspnet/default.asp

8/7/2019 net mobile

3/21

Hello W3Schools

The Page directive tells ASP to use (inherit) mobile page handling instead of regular page handling

(like the one used for traditional browsers)

The Register directive defines the prefix that will be used for mobile controls. We have used"Mobile", but you can use any prefix you like.

The element tells the server to create a mobile form control.

The element tells the server to create a mobile label control with the text HelloW3Schools.

The Mobile ASP.NET Output

When the ASP page executes, it will produce this output to a WAP enabled mobile phone:

Hello W3Schools

While this output will be produced for a Pocket PC:

Hello W3Schools

Conclusion

.NET Mobile will generate WML code for cell WAP enabled cell phones and HTML code for devices likethe Pocket PC.

By detecting the browser, .NET Mobile will output correct content, providing developers with apowerful tool to develop single applications that will serve many different mobile devices.

Mobile applications can be tested and viewed with different emulators.

8/7/2019 net mobile

4/21

Using your Browser

Since mobile web pages detect your browser, you can test your mobile applications with a standardbrowser.

When a mobile web page detects a standard web browser it will produce HTML output. This willwork for Internet Explorer or any other browser that supports inline frames.

The Microsoft Mobile Explorer Emulator

Microsoft Mobile Explorer (MME) is a micro browser used in many PDA devices and pocket PCs.

The emulator can be downloaded from http://msdn.microsoft.com/downloads/default.asp

Openwave Simulators

The Openwave mobile browser is the most common browser used in Internet enabled cell phones.

An emulator can be downloaded from http://www.openwave.com

The Nokia Mobile Internet Toolkit

This toolkit contains emulators for most of the different Nokia devices.

The toolkit can be downloaded from http://forum.nokia.com

The Pocket PC 2002 SDK

The Pocket PC 2002 Software Development Kit includes an emulator that uses a virtual machine torun the Pocket PC 2002 operating system on your PC.

The SDK can be downloaded from http://msdn.microsoft.com/downloads/default.asp

.NET Mobile Forms are specialized web forms designed to work on different mobiledevices.

Mobile Pages

A mobile page is much the same as an ordinary .NET web page. It is a text file with an aspxextension, and it can contain a variety of web controls.

The difference is the page directive that identifies the page as a mobile page, and the controls usedon the page, which are mobile controls.

The mobile controls can be programmed device-independently, and the page will produce an outputthat suits the device that access it.
http://msdn.microsoft.com/downloads/default.asphttp://www.openwave.com/http://forum.nokia.com/http://msdn.microsoft.com/downloads/default.asphttp://msdn.microsoft.com/downloads/default.asphttp://www.openwave.com/http://forum.nokia.com/http://msdn.microsoft.com/downloads/default.asp

8/7/2019 net mobile

5/21

Mobile Forms

Each mobile page must have at least one mobile form, and each mobile form can have a number ofmobile controls.

Note that mobile pages can have multiple mobile forms. This is due to the nature of mobile devices.Mobile devices have small screens and it is very normal to navigate between screens with a simplelink.

Automatic Paging

.NET Mobile supports automatic paging for different mobile devices.

The paging is handled differently for each control. For example when paging takes place the controlsincluded in a panel control will stay together.

Displaying Text

This mobile page uses a TextView control to display a large amount of text:

This is a very long text to demonstratehow text can be displayed over several screens.This is a very long text to demonstratehow text can be displayed over several screens.This is a very long text to demonstratehow text can be displayed over several screens.This is a very long text to demonstratehow text can be displayed over several screens.

When this page is displayed on a mobile device, the navigation and display functions of the pagewill be compiled differently for different devices with different display characteristics.

When the text is displayed on a pocket PC with a small display, the user will be able to scroll thetext with a scroll bar, but on a cell phone the text will be displayed over several screens with propernavigation tools added.

Note that all mobile controls must have the runat attribute set to "server", in order to secure properrendering of the page for different devices.

8/7/2019 net mobile

6/21

Single Forms

This mobile page has one form:

Hello W3Schools

Multiple Forms

This mobile page has two forms:

Hello W3Schools2

Hello Again1

Links

Note the element in the example above. The link control lets the user navigatebetween the two mobile forms.

Mobile Controls exposes device independent programmable events.

Programming Events

Mobile controls has an object model with programmable properties, methods and events.

For a complete overview please refer to the reference section.

8/7/2019 net mobile

7/21

Submitting Text

This page has to forms:

Dim age

Sub AgeClick(sender As Object, e As EventArgs)age=text1.TextActiveForm=Form2End SubSub Form2_Activate(sender As Object,e As EventArgs)

message.Text="You are " & age & " years old"End Sub

Age?

When a page has two forms, the first form is always opened by default.

The first form has a label with the text "Age?", an input box to input the age, and a submit button.

The second page is activated by the submit button on the first page, and displays a response.

When the application runs on a mobile device, the two pages will display like this:

Form 1

Age?

Submit

Form 2

8/7/2019 net mobile

8/21

You are 11 years old

Input Controls are used to collect input from the mobile user.

Input Controls

There is a number of mobile controls that support user input.

The most common input control is perhaps the TextBox control, which was demonstrated in theprevious chapter. The TextBox control is perfect for simple user input like names, numbers,

identifications and keywords.

For larger amount of input a TextView control is a better choice. The TextView control allows longmulti-line input like the one you need for SMS or other messages.

Numeric Input

The numeric attribute of the textbox control can be set to true or false to specify whether thetextbox should accept only numeric input.

Note: This behavior will normally work on cell phones by changing the input mode from letters tonumbers. For HTML browsers however, this behavior is normally not supported.

Password Input

The password attribute of the textbox control can be set to true or false to specify whether thetextbox should be treated as a password field.

A password field will hide the input by displaying * (stars) instead of ordinary text.

List Controls

TextBox and TextView controls are well suited for entering input, but sometimes you want the userto select from a list of predefined values.

The SelectionList Control supports drop down lists, check boxes and radio buttons. This topic iscovered in another chapter.

The List Control supports selection from menus and lists. The List Control is covered in anotherchapter.

8/7/2019 net mobile

9/21

User Interface Controls

User Interface Controls are controls which display the user interface:

Name Function

Command Performs an action

Form Defines a container for mobile controls

Image Defines an image

Label Defines a text

Link Defines a hyperlink

List Defines a list

MobilePage Defines a container for mobile controls

ObjectList Defines a list of data objects

Panel Defines a container for other controls

SelectionList Defines a list to select from

StyleSheet Defines styles to be applied to other controls

TextBox Defines a single line input boxTextView Defines a multi-line input box

For a full control reference, including properties methods, events, and more examples, please referto the "Mobile Reference" page.

Validation Controls are used to validate the data entered by a user.

Validation Controls

Validation controls are used to validate the data entered by a user.

Validation controls allow you to validate an input control (like a TextBox), and display a messagewhen validation fails.

Each validation control performs a specific type of validation (like validating against a specific valueor a range of values).

By default, page validation is performed when a command control is clicked. You can preventvalidation when a control is clicked by setting the CausesValidation property to false.

Validating Input

This page has two forms:

8/7/2019 net mobile

10/21

Sub Page2(Sender as Object,E as EventArgs)If Page.IsValid ThenActiveForm=f2text2.Text="You are " & age.text & " years old"

end if

End Sub

You must be at least 18

Age?

Submit

The first form has a label with the text "Age?", an input box to input the age, and a submit button.

The second page is activated by the submit button on the first page, and displays a response.

If the input validates as error, an error message is displayed.

When the application runs on a mobile device, the two pages will display like this:

Form 1

Age?

Submit

Form 2

You are 21 years old

8/7/2019 net mobile

11/21

The ValidationSummary Control

The previous example used a CompareValidator control to validate an input field. The field tovalidate was defined by the attribute ContolToValidate.

You can also use a ValidationSummary control with the attribute FormToValidate, to validate all theinput of a form.

This way you can display a summary of errors instead of one error at the time.

Validation Controls Reference

Name Function

CompareValidator Compares two values

CustomValidator Provides custom validation

RangeValidator Validates a range

RegularExpressionValidator Validates an expression

RequiredFieldValidator Validates required data

ValidationSummary Displays a validation summary

For a full control reference, including properties methods, events, and more examples, please referto the "Mobile Reference" page

The Mobile List Control supports different input and display properties.

Selecting from a List

This page has to forms:

Sub Show_Price(sender As Object,e As ListCommandEventArgs)text1.Text=e.ListItem.Text & "=" & e.ListItem.ValueActiveForm=f2

End Sub

8/7/2019 net mobile

12/21

The first form has a list of cars.

The second page displays a price. This page is activated when a car is selected on the first page.

When the application runs on a mobile device the two pages will display like this:

Form 1

VolvoBMWAudi

Form 2

Volvo=$30,000

The SelectionList Control supports drop down lists, check boxes and radio buttons.

The SelectionList

This mobile page uses a SelectionList to let the user select a car:

8/7/2019 net mobile

13/21

Sub Car_Click(sender as Object, e as EventArgs)ActiveForm=f2t1.text=cars.Selection.Value

End Sub

When this page is displayed on a mobile device, the navigation and display functions of the pagewill be compiled differently for different devices with different display characteristics.

Fore some devices, like a handheld PC, it might display a dropdown list to choose from. For a cellphone it might display a list of options to select from.

.NET Mobile displays different types of images for different types of devices.

The Image Control

Different mobile devices have different display capabilities.

The Image Control allows the developer to specify different types of images for different types ofdevices.

Image Types

Some mobile devices will display GIF images. Other mobile devices will display BMP images orWBMP images. The Image Control allows you to specify different images for each preferred image

type.

This mobile page displays an image:

8/7/2019 net mobile

14/21

Namespace="System.Web.UI.MobileControls"Assembly="System.Web.Mobile" %>

When this page is displayed on pocket PC, a GIF image will be displayed. On a cell phone a WBMPimage or a BMP image will be displayed, according to the characteristics of the cell phone.

Utility controls support complicated user interfaces with minimum of code.

The AdRotator Control

This mobile page displays different advertisements:

This is the ad file called "advertisements.xml":

image1.gifimage1.bmpimage1.wbmphttp://www.1.comVisit 1

image2.gifimage2.bmpimage2.wbmphttp://www.2.comVisit 2image3.gif

8/7/2019 net mobile

15/21

image3.bmpimage3.wbmphttp://www.3.comVisit 3

The Calendar Control

This mobile page displays a calendar:

Sub CalChanged(sender as Object,e as EventArgs)lab1.Text="You selected " & c1.SelectedDateActiveForm=f2End Sub

In this example a calendar is displayed in the first form. When the user select a date from thecalendar, the selected date is displayed in a new form.

The PhoneCall Control

This mobile page will display the text "Tove's number" and dial the number (555) 555-5555 whenthe user selects the text:

8/7/2019 net mobile

16/21

PhoneNumber="(555) 555-5555"Text="Tove's number"AlternateFormat="{0}" />

The attribute "AlternateFormat" has the value "{0}". This displays the text from the attribute"Text".

If you use the value "{1}" it will display the text from the attribute "PhoneNumber".

You can also use a construct like this: AlternateFormat="{0} is {1}". This will display the text"Tove's number is (555) 555-5555".

Utility Controls

Name Function

AdRotator Displays advertisements

Calendar Displays a calendar

PhoneCall Calls a telephone number

For a full control reference, including properties methods, events, and more examples, please referto the "Mobile Reference" page.

.NET Mobile Reference

Main Mobile Objects

.NET Mobile supports three main objects:

The Mobile Page

The Mobile Form

The Mobile Panel

The Mobile Page is the container for the application.

Each Mobile Page can have one or more Mobile Forms.

Each Mobile Form can have zero ore more Mobile Panels.

Mobile Forms and Mobile Panels are used to group Mobile Controls.

Mobile Controls

Mobile Controls are grouped into:

User interface controls

8/7/2019 net mobile

17/21

Validation controls

Utility controls

UI Controls

UI controls are controls that displays the user interface:

Name Function

Command Performs an action

Form Defines a container for mobile controls

Image Defines an image

Label Defines a text

Link Defines a hyperlink

List Defines a list

MobilePage Defines a base class for all mobile pages

ObjectList Defines a list of data objects

Panel Defines a container for other controls

SelectionList Defines a list to select from

StyleSheet Defines styles to apply to other controls

TextBox Defines a single line input box

TextView Defines a multi-line input box

Validation Controls

Validation controls are used to validate the data entered by a user:

Name Function

CompareValidator Compares the value of one input control to the value ofanother input control or to a fixed value

CustomValidator Allows you to write a method to handle the validation of thevalue entered

RangeValidator Checks that the user enters a value that falls between twovalues

RegularExpressionValidator Ensures that the value of an input control matches aspecified pattern

RequiredFieldValidator Makes an input control a required field

ValidationSummary Displays a report of all validation errors occurred in a page

Utility Controls

Utility controls support complicated user interfaces with minimum of code:

Name Function

AdRotator Displays advertisements

Calendar Displays a calendar
http://www.w3schools.com/dotnetmobile/control_command.asphttp://www.w3schools.com/dotnetmobile/control_form.asphttp://www.w3schools.com/dotnetmobile/control_image.asphttp://www.w3schools.com/dotnetmobile/control_label.asphttp://www.w3schools.com/dotnetmobile/control_link.asphttp://www.w3schools.com/dotnetmobile/control_list.asphttp://www.w3schools.com/dotnetmobile/control_mobilepage.asphttp://www.w3schools.com/dotnetmobile/control_panel.asphttp://www.w3schools.com/dotnetmobile/control_selectionlist.asphttp://www.w3schools.com/dotnetmobile/control_stylesheet.asphttp://www.w3schools.com/dotnetmobile/control_textbox.asphttp://www.w3schools.com/dotnetmobile/control_textview.asphttp://www.w3schools.com/dotnetmobile/control_comparevalidator.asphttp://www.w3schools.com/dotnetmobile/control_customvalidator.asphttp://www.w3schools.com/dotnetmobile/control_rangevalidator.asphttp://www.w3schools.com/dotnetmobile/control_regexpvalidator.asphttp://www.w3schools.com/dotnetmobile/control_requiredfieldvalidator.asphttp://www.w3schools.com/dotnetmobile/control_validationsum.asphttp://www.w3schools.com/dotnetmobile/control_adrotator.asphttp://www.w3schools.com/dotnetmobile/control_calendar.asphttp://www.w3schools.com/dotnetmobile/control_command.asphttp://www.w3schools.com/dotnetmobile/control_form.asphttp://www.w3schools.com/dotnetmobile/control_image.asphttp://www.w3schools.com/dotnetmobile/control_label.asphttp://www.w3schools.com/dotnetmobile/control_link.asphttp://www.w3schools.com/dotnetmobile/control_list.asphttp://www.w3schools.com/dotnetmobile/control_mobilepage.asphttp://www.w3schools.com/dotnetmobile/control_panel.asphttp://www.w3schools.com/dotnetmobile/control_selectionlist.asphttp://www.w3schools.com/dotnetmobile/control_stylesheet.asphttp://www.w3schools.com/dotnetmobile/control_textbox.asphttp://www.w3schools.com/dotnetmobile/control_textview.asphttp://www.w3schools.com/dotnetmobile/control_comparevalidator.asphttp://www.w3schools.com/dotnetmobile/control_customvalidator.asphttp://www.w3schools.com/dotnetmobile/control_rangevalidator.asphttp://www.w3schools.com/dotnetmobile/control_regexpvalidator.asphttp://www.w3schools.com/dotnetmobile/control_requiredfieldvalidator.asphttp://www.w3schools.com/dotnetmobile/control_validationsum.asphttp://www.w3schools.com/dotnetmobile/control_adrotator.asphttp://www.w3schools.com/dotnetmobile/control_calendar.asp

8/7/2019 net mobile

18/21

PhoneCall Calls a telephone number

Mobile Internet Toolkit 1.0 Devices

The Mobile Internet Toolkit 1.0 was released January 15, 2002. The following devices where

supported in this first release:

Device Browser

Alcatel One Touch 701 Openwave UP.Browser 4.1.19

Audiovox CDM-135 Openwave UP.Browser 4.1.2

Audiovox CDM-9000 Openwave UP.Browser 3.1.11

Audiovox CDM-9100 Openwave UP.Browser 4.1.21c

Benefon Q Microsoft Mobile Explorer 2.01

Casio Cassiopeia E-125 Microsoft Pocket Internet Explorer 2000 (4.01)

Compaq iPAQ H3630 Microsoft Pocket Internet Explorer 2000 (4.01)

Compaq iPAQ H3650 GoAmerica Go.Web 5.0.1


Compaq iPAQ H3650 Omnisky 2.0


Ericsson R280LX Openwave UP.Browser 3.03

Ericsson R320 Ericsson R320/R1A

Ericsson R380 Ericsson R380 2.0

Ericsson R520m Ericsson R520/R201

Ericsson T20s Ericsson T20/R2A

Fujitsu F503i ACCESS Compact NetFront 2.0

Handspring Visor Prism Blazer 1.0

Handspring Visor Platinum Qualcomm Eudora Internet Suite 2.1Handspring Visor Platinum Omnisky 2.1.0.15

Hitachi C407H UP.Browser 3.1

HP Jornada 720 Microsoft Pocket Internet Explorer 2000 (4.01)

IBM WorkPad c505 ilinx Xiino 1.01J

Kyocera QCP 3035 Openwave UP.Browser 3.1.17

Kyocera QCP 2035A Openwave UP.Browser 3.1.17

Kyocera QCP 6035 Qualcomm Eudora 2.0

LG V111 Openwave UP.Browser 3.1

Mitsubishi D502i ACCESS Compact NetFront 2.0


Mitsubishi T250 Openwave UP.Browser 3.1.11A

Motorola i1000plus Openwave UP.Browser 4.1.17

Motorola i2000plus Openwave UP.Browser 4.1.17

Motorola i50sx Openwave UP.Browser 4.1.21b

Motorola i85s Openwave UP.Browser 4.1.21b

Motorola TimePort P7382i Openwave UP.Browser 4.1.19i

Motorola TimePort P7389 Openwave UP.Browser 4.1.16g
http://www.w3schools.com/dotnetmobile/control_phonecall.asphttp://www.w3schools.com/dotnetmobile/control_phonecall.asp

8/7/2019 net mobile

19/21

Motorola TimePort P8767 Openwave UP.Browser 3.1.10

Motorola StarTAC 7868W Openwave UP.Browser 3.1.02

Motorola T2288 Openwave UP.Browser 4.1.8

Motorola V100 Openwave UP.Browser 4.1.22

Motorola V120c Openwave UP.Browser 4.1.21b

Motorola V2288 Openwave UP.Browser 4.1.16f

Motorola V60c Openwave UP.Browser 4.1.21b

NEC N210i ACCESS Compact NetFront 2.0


Nokia 3330 Nokia 1.0 (3.12)

Nokia 6210 Nokia 1.0 (4.27)

Nokia 7110 Nokia 1.0 (5.01)

Nokia 9110i Nokia 1.1

Nokia 9210 Symbian Crystal 6.0

Palm m505 MyPalm 1.1

Palm VIIx MyPalm 1.0

Palm Vx AU-Systems 2.12181.1

Palm Vx GoAmerica Go.Web 3.0.6

Palm Vx Omnisky 2.0.0.4

Panasonic P210i Original Equipment Manufacturer's Version


Personal computer Microsoft Internet Explorer 5.5

Personal computer Microsoft Internet Explorer 6.0

RIM Blackberry 857 GoAmerica Go.Web 1.8.004 (HTML)



RIM Blackberry 950 GoAmerica Go.Web 6.010.0 (HTML)RIM Blackberry 957 GoAmerica Go.Web 1.6.000 (HTML)

RIM Blackberry 957 GoAmerica Go.Web 6.0.10.0 (HTML)

Samsung SCH-6100 Openwave UP.Browser 3.1

Samsung SCH-850 Openwave UP.Browser 3.1

Samsung SCH-8500 Openwave UP.Browser 3.1.140.TC14

Samsung UpRoar M100 Openwave UP.Browser 3.1

Sanyo C401SA Openwave UP.Browser 3.2

Sanyo SCP-4500 Openwave UP.Browser 3.1.04

Sanyo SCP-5000 Openwave UP.Browser 3.2

Sharp J-SH04 Original Equipment Manufacturer's Version 3.0

Sharp Zaurus MI-E1 Original Equipment Manufacturer's Version 6.1

Siemens C35i Openwave UP.Browser 4.1.8c

Siemens S35i Openwave UP.Browser 4.1.16

Siemens SL45 Openwave UP.Browser 4.1

Sony CLIE PEG-N700C ilinx Palmscape 4.0SJ

Sony CMD-Z5 Microsoft Mobile Explorer 2.0 r54ue

Sony CMD-J5 Microsoft Mobile Explorer 2.0 r54ue

8/7/2019 net mobile

20/21

Sony SO503i ACCESS Compact NetFront 2.0

Sprint Denso Touchpoint 120 Openwave UP.Browser 3.1

Sprint Denso Touchpoint 2200 Openwave UP.Browser 3.1

Sprint LG Touchpoint 3000 Openwave UP.Browser 3.1

Toshiba J-T05 Original Equipment Manufacturer's Version 3.0

Device Updates

Updates to the Mobile Internet Toolkit will be released when support for new devices are ready.Please refer to the following pages for updates.

Mobile Device Update 1

An update to the Mobile Internet Toolkit was released May 13, 2002. This update providedadditional support for the following devices:

Device Browser

@Migo PD-600C Microsoft Pocket Internet Explorer 2002 (4.1)

Alcatel One Touch 311 Openwave UP.Browser 4.1.23a

Alcatel One Touch 501 Openwave UP.Browser 4.1.19e

Alcatel One Touch 511 Openwave UP.Browser 4.1.23a

Audiovox Maestro Handheld Pocket PC Microsoft Pocket Internet Explorer 2002 (4.1)

Casio BE-500 OEM 1.00.62(J) (HTML)


Ericsson T20e/ec Ericsson T20/R2A

Ericsson T29s/sc Ericsson T20/R2A

Ericsson T39m/mc Ericsson T39/R202Ericsson T65 Ericsson T65/R101



Handspring Treo 180 Blazer 2.0

Handspring Visor Platinum Blazer 2.0

HP Jornada 567 Microsoft Pocket Internet Explorer 2002 (4.1)


Mitsubishi D503iS ACCESS Compact NetFront 2.0

Motorola i80s Openwave UP.Browser 4.1.23

Motorola i90c Openwave UP.Browser 4.1.23

Motorola Talkabout 191 Openwave UP.Browser 4.1

Motorola Timeport 270c Openwave UP.Browser 4.1.21b

Motorola TimePort T260 Openwave UP.Browser 4.1.8

Motorola V50 Openwave UP.Browser 4.1.16s

Motorola V200 Openwave UP.Browser 4.1

NEC FOMA N2001 ACCESS Compact NetFront 2.0


8/7/2019 net mobile

21/21


NEC N503iS ACCESS Compact NetFront 2.0

Nokia 3285 Openwave UP.Browser 3.1.11A.1

Nokia 6310 Nokia 1.0 (4.10)

Nokia 8310 Nokia 1.0 (3.07)

Nokia 9110i Nokia 1.1 (HTML)

Nokia 9210 Symbian Crystal 6.0 (HTML)

Palm m505 Blazer 2.0

Palm VIIx AvantGo 4.0

Palm Vx GoAmerica Go.Web 6.0

Panasonic GD95 Original Equipment Manufacturer's Version


Panasonic P503iS Original Equipment Manufacturer's Version

Panasonic P821i ACCESS Compact NetFront 2.0

Samsung SGH-A300 Openwave UP.Browser 4.1.19k

Samsung SGH-A400 Openwave UP.Browser 4.1.19k

Samsung SPH-N200 Openwave UP.Browser 4.1.22b

Samsung SPH-i300 Openwave UP.Browser 4.1.22c1

Sanyo C1001SA Openwave UP.Browser 3.2

Sanyo SCP-4700 Openwave UP.Browser 4.1.24f

Sanyo SCP-6000 Openwave UP.Browser 4.1.23a

Sharp J-SH07 Original Equipment Manufacturer's Version 3.0

Sharp SH821i ACCESS Compact NetFront 2.0

Sharp Zaurus MI-E21 Original Equipment Manufacturer's Version 6.2

Siemens ME45 Openwave UP.Browser 5.0.1.1.102 (GUI)

Siemens M35 Openwave UP.Browser 4.1.16m

Siemens S40 Openwave UP.Browser 4.1.16Sony C1002S Openwave UP.Browser 3.2

Sony PEG T600C ilinx Xiino 1.0.6a4SJ

Sony SO210i ACCESS Compact NetFront 2.0

Sony SO503iS ACCESS Compact NetFront 2.0

Sprint LG Touchpoint 5200 Openwave UP.Browser 4.1.22b

Toshiba Genio e550x Microsoft Pocket Internet Explorer 2002 (4.1) ja

Toshiba J-T06 Original Equipment Manufacturer's Version 3.0

http://www.w3schools.com/dotnetmobile/mobile_lists.asp

net mobile

Documents

Transcript of net mobile