•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the Software Development category of DaniWeb, a massive community of 383,428 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 2,596 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our Software Development advertiser:
Oct 23rd, 2006, 7:20 am
Find out which are the essential design issues when developing applications for handheld devices.
Mobile devices' inherent Web capabilities open a whole new platform for delivering content. Before you dive into developing mobile Web applications, read about some issues that you need to consider.
When targeting handheld devices such as mobile phones and PDAs, there are many design consideration to be taken into account, not least the limitations in terms of screen resolution.
While screen resolution is an issue with regular Web browsing, the actual screen dimensions are important when dealing with mobile devices. Screen-size limitations are an issue because the majority of Web sites are designed to be viewed on desktop-sized displays. Their page layout assumes that users can view large portions of a page at once.
The much smaller page excerpts displayed on a handheld device screen interferes with page functionality and user comprehension. The result is that users have to spend an inordinate amount of time awkwardly scrolling up and down as well as left and right.
Content is king
Due to the space limitations, developers should be conscious of the following tips when targeting mobile devices:
Limit graphics: they are an excellent way to spice up a Web site, but their use is questionable when working with small screens. Also, many handheld devices feature monochrome displays, so rich colour graphics are lost. The most important text or information should take centre stage. If you must use graphics, limit their size to control download times. In addition, effectively use every pixel of a graphic and avoid unnecessary elements. On a final note, take advantage of the alt tag for images so graphic functionality is conveyed when/if images are not displayed.
Limit download times: Travel back in time to the initial days of the Web where dial-up connections with a 9,600baud modem was cutting edge, and you will understand the bandwidth limitations for wireless devices. So, you should develop scaled-down pages that eliminate the bells and whistles and deliver only what is necessary to mobile clients.
Carefully select content: Tailor the content specifically to the target user group by displaying only the most essential data.
Minimise page length and size: Scrolling on handheld devices is often limited, awkward, and it can be hard for users to keep track of their place with scroll keys and other pen input devices. With that in mind, you should limit the amount of scrolling required in a Web application. This may involve splitting normal pages into multiple pages for handhelds.
Architecting the site for handheld devices demands information that is effectively organised to maximise user experience.
Utilise standard HTML: Stick with standard HTML tags to ensure proper functioning of an application.
When developing applications for mobile or handheld browsers, your main focus is on the content. The reduced screen size relegates the extra items to the scrap heap.
Mobile devices' inherent Web capabilities open a whole new platform for delivering content. Before you dive into developing mobile Web applications, read about some issues that you need to consider.
When targeting handheld devices such as mobile phones and PDAs, there are many design consideration to be taken into account, not least the limitations in terms of screen resolution.
While screen resolution is an issue with regular Web browsing, the actual screen dimensions are important when dealing with mobile devices. Screen-size limitations are an issue because the majority of Web sites are designed to be viewed on desktop-sized displays. Their page layout assumes that users can view large portions of a page at once.
The much smaller page excerpts displayed on a handheld device screen interferes with page functionality and user comprehension. The result is that users have to spend an inordinate amount of time awkwardly scrolling up and down as well as left and right.
Content is king
Due to the space limitations, developers should be conscious of the following tips when targeting mobile devices:
Limit graphics: they are an excellent way to spice up a Web site, but their use is questionable when working with small screens. Also, many handheld devices feature monochrome displays, so rich colour graphics are lost. The most important text or information should take centre stage. If you must use graphics, limit their size to control download times. In addition, effectively use every pixel of a graphic and avoid unnecessary elements. On a final note, take advantage of the alt tag for images so graphic functionality is conveyed when/if images are not displayed.
Limit download times: Travel back in time to the initial days of the Web where dial-up connections with a 9,600baud modem was cutting edge, and you will understand the bandwidth limitations for wireless devices. So, you should develop scaled-down pages that eliminate the bells and whistles and deliver only what is necessary to mobile clients.
Carefully select content: Tailor the content specifically to the target user group by displaying only the most essential data.
Minimise page length and size: Scrolling on handheld devices is often limited, awkward, and it can be hard for users to keep track of their place with scroll keys and other pen input devices. With that in mind, you should limit the amount of scrolling required in a Web application. This may involve splitting normal pages into multiple pages for handhelds.
Architecting the site for handheld devices demands information that is effectively organised to maximise user experience.
Utilise standard HTML: Stick with standard HTML tags to ensure proper functioning of an application.
When developing applications for mobile or handheld browsers, your main focus is on the content. The reduced screen size relegates the extra items to the scrap heap.
This blog entry was written by newscop. It has received 2,526 views, 1 comment, and 3 linkbacks.
•
•
•
•
advertising apple blog browser browsers browsing business censorship daniweb data developer development domains firefox google html ie8 india internet iphone legal linux marketing media microsoft mobile money mozilla news office online opera privacy research safety search security software stocks technology video vista w3c web webmaster wikipedia windows yahoo youtube
All Recent Tags Comments (Newest First)
sloper47 | Newbie Poster | Nov 21st, 2006
•
•
•
•
If anyone is availible, I am looking for help testing my mobile pages at www.collegecupcakes.com/mobi It works great on a blackberry and a treo, but Need some more testing against other phones.
Take a look and see if it works.
Let me know what you think
sultan@collegecupcakes.com
Take a look and see if it works.
Let me know what you think
sultan@collegecupcakes.com
Post Comment
•
•
•
•
Only community members can start a blog or comment on blog entries. You must register or log in to contribute.
•
•
•
•
•
•
•
•
DaniWeb Software Development Marketplace
Related Blog Entries
- LinuxWorld Caters to Developers (3 Hours Ago)
- Programmers Blog and Career (5 Hours Ago)
- Deploy .NET 3.5 Apps With No Framework Update (2 Days Ago)
- TI’s Low Power Chips Save Battery Life, Not the Planet (2 Days Ago)
- IE8 Beta Testers wanted, only great people need apply (3 Days Ago)
- Microsoft's Post-Windows Plans Revealed (7 Days Ago)
- To Heck With Vista; I'd Wait for Modori (7 Days Ago)
- Childs Case Exposes Media, City Ignorance (11 Days Ago)
- GUIdancer 2.2 Automates Failure Retires (12 Days Ago)
- Microsoft POIsed to Control an Apache Project (13 Days Ago)
Related Forum Threads
- ASP.NET Web/ Applications Developer - Macclesfield (Software Development Job Offers)
- Looking for examples of Java Web Applications (Java)
- How to Deploy the Web applications(JSP) on weblogic server (JSP)
- Best choise for a local application database (C#)
- [For Hire] $12/hour!! - Quality ASP.NET/MSSQL Developer (Post your Resume)
- Pocket PC/PDA Phone Windows/Verizon HELP!! (Gadgets and Gizmos)
- Coldfusion MX 7 Developer [Seeking Freelance Work] (Post your Resume)
- Security settings preventing me from running web applications containing ActiveX (Viruses, Spyware and other Nasties)
- how well is apache in handling wireless application? (Linux Servers and Apache)
- Microsoft .NET FAQ (ASP.NET)