Mobile website development Services

MOBILE WEBSITE DEVELOPMENT
Copyright © 2012-2015 Curix Infotech Pvt.Ltd.

Table of Contents
 The Need for Mobile Web
 Mobile Web History
 Mobile Web Standards
 Comparison with Desktop & Mobile Apps
 Best Practices

The Need for Mobile Web
 Limitations of mobile phones
 Limited Processor Power and Memory
 Limited Battery Life
 Limited Input and Output Facilities
 Low Bandwidth
 Unpredictable Availability and Stability

The Need for Mobile Web
 TCP/IP protocol suite was not designed for a wireless
environment
 Bandwidth resource is expensive
 HTML pages are not suitable for use in mobile
devices with limited processor power and screen.

Mobile Web History
 Wireless Application Protocol (WAP) Forum was
founded in 1997 by Ericsson, Motorola, Nokia, and
Phone.com.
 WAP 1.1 was published in 1999
 WAP 2.0 was published in 2001

Mobile Web History
 In 2002, the WAP Forum consolidated into the
Open Mobile Alliance (OMA) and the specification
work from WAP continues within OMA

Mobile Web History
 WAP is designed with two main goals
 to minimize bandwidth requirement
 to maximize the number of supported network types (e.g., 9.6
Kbps in GSM).

Mobile Web History
 WAP protocol stack is a lightweight protocol stack
that is designed to address the limitations of
wireless devices and the wireless network.
 To access ordinary web servers, WAP-enabled
mobile devices can rely on a WAP gateway to
provide protocol conversion between WWW
protocol stack and WAP protocol stack.

Mobile Web History
 WAP tries to utilize existing Internet protocols and
standards as much as possible
 For example XML, HTML, HTTP & TLS

Mobile Web History
 To reduce transmission time, WAP uses binary-
coded WML (wireless markup language) pages.
 Also WAP specifies a caching model and user agent
profile (UAProf) for efficient delivery of device-
specific content.

Mobile Web History
<wml>
<card id=“Card1" title="First Card">
<p>
Hello World!
</p>
</card>
<card id="Card2" title="Second Card">
<p>
WAP is fun!
</p >
</card>
</wml>

Mobile Web Standards
 Various standards involved in:
 Structure
 Presentation
 Client Side Scripting

 XML-formatted markup defines the document
structure
 Handsets may support WML, XHTML, HTML4,
HTML5 in varying degrees
 These XML standards have various versions &
derivations

 Cascading Style Sheets (CSS) control the
presentation.
 Most XHTML-MP mobile browsers support
Wireless CSS, CSS Mobile Profile, and/or CSS 2.
 CSS 3 is new, coming along with HTML5

 Client-side scripting mainly through Java script
 ECMA Script-MP or mobile JavaScript targets
mobile phones
 WML Script is a scripting language which
complements WML.

 XHTML-MP (Extensible Hypertext Markup
Language - Mobile Profile) is a specialization
XHTML designed to incorporate features useful to
mobile devices.
 XHTML-MP 1.0 was defined by the OMA and is
currently (2010) the best markup choice for
HTML-capable mobile browsers.

 Over time, OMA has developed XHTML-MP and
now has a proposed 1.2 version of its specification.
 XHTML-MP comes with a mobile-friendly means
of using CSS to separate presentation from the
markup, just like on the desktop.

Comparison with Desktop
& Mobile Apps
 Client side scripting (like Java script, Java applets)
& AJAX usually not possible
 Does not require installation unlike apps; many
feature phones & smart phones have in-built
browsers
 Minimal or no client side caching

Comparison with Desktop
& Mobile Apps
 Mobile websites require much greater developer
understanding & attention to detail than Desktop
 Also may require use of proprietary technologies
e.g. for Content Adaptation

Best Practices
 While building the mobile information
architecture, think about users’ “click investment”
 You might also want to have condensed versions of
the stories.
 When presenting the information on a mobile
device you will probably want to change the
navigation structure

Best Practices
Figure: Desktop Browser Website

Best Practices
Figure: Mobile Browser Website

Best Practices
Figure: Desktop Web Page Navigation

Best Practices
Figure: Mobile Web Page Navigation

Best Practices
 Content Adaptation – changing content to suit
mobiles
 A .mobi domain is recommended as a clear way to
indicate to the user that a site is mobile-friendly
 .mobi.ke is controlled by Kenic – in charge of
country code top-level domain (ccTLD) for Kenya

Mobile Web Development & Design
Which screen sizes & aspect ratio to target?
 Portrait or landscape
 BB with keyboard?
 iPhone?
 iPad?
• What appears above the fold? Below?
• Does the device support zooming?
Hardware input (scroll wheel, mouse touch)?
 No mouseovers

How to handle transition between mobile and
desktop users
 Auto detect?
 A specific domain?
 How do users get back and forth?
What type of bandwidth will users have access to?
What content to display?
How much content to display?
Text size?

Keep images small
Large buttons
Reduce scrolling (especially horizontal)
Reduce the amount of text
 Or, give users choices and hints
Degrade gracefully
 Indicate when plugins will not function

Sandeep Verma (Director)
Curix InfoTech Pvt. Ltd.
G-19, Sec - 63
Noida-201301
Ph:0120-4331955
Web: http://www.curixinfotech.com
Email: sales@curixinfotech.com

Mobile website development Services

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (12)

Semelhante a Mobile website development Services

Semelhante a Mobile website development Services (20)

Último

Último (8)

Mobile website development Services