Web Apps Development Best Pactices | Hackonten
Upcoming SlideShare
Loading in...5
×
 

Web Apps Development Best Pactices | Hackonten

on

  • 724 views

Slide for Hackonten (www.hackonten.com)

Slide for Hackonten (www.hackonten.com)

Statistics

Views

Total Views
724
Views on SlideShare
723
Embed Views
1

Actions

Likes
1
Downloads
6
Comments
0

1 Embed 1

http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial LicenseCC Attribution-NonCommercial License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • When page content exceeds the size of the screen, its content can extend outside the screen, however it should extend below the screen only.
  • Element margins, sizes, and spacing should be aligned and consistent throughout a web app. For example, margins on the left and right of a content area should be consistent.
  • One icon should be used to convey the same concept, for example, use the same icon to indicate refresh on all screens.

Web Apps Development Best Pactices | Hackonten Web Apps Development Best Pactices | Hackonten Presentation Transcript

  • Web Apps Development Best PracticesMohamad IqbalNokia Developer Certified Trainerhttp://about.me/ciebalhttp://nice.or.id/ciebal
  • Architecture Nokia Browser for Series 40 Proxy Server Nokia Browser forWWW Series 40 Client HTML, CSS, Optimised content (HTML, (Phone) Javascript, Images, XML, CSS, JSON, etc compressed images)
  • Platform Services• Messaging• Location• Telephone
  • Developer Kit• Nokia Web Tools 1.0• Nokia Web Tools 1.5• Nokia Web Tools 2.0 (beta)
  • Comparison Nokia Web ToolsFeature Version 1.0 Version 1.5 Version 2.0Symbian Applications SupportedEfficient proxy based web apps Supported Supported SupportedMWL support Supported Supported SupportedModern UI with floating icons Supported SupportedGeolocation API support Supported SupportedWeb app image caching Supported SupportedSMS URI support Supported SupportedFull Touch Simulator Supported
  • Web Technologies• HTML 4.0• CSS 2.1• Javascript 1.8• DOM Level 1 and 2
  • Series 40 Web App UX Guidelines
  • Screen Orientation320x240 pixels 240x320 pixels
  • Screen Orientation Full Touch 240x400 pixels
  • Navigation Controls The app logo should Paging controls should The icon in the top rightalways be in the top bar be displayed directly of the header can be below the app header. contextual.
  • Scrolling
  • Focus on discrete tasksStart the task Choose a category Choose a sub- Browse the results category
  • Align elements
  • Use a common set of icons
  • Accommodating Screen Orientationif (screen.width > 240) {document.write(<link rel="stylesheet"href="../../basicLandscape.css" type="text/css" />);}else {document.write(<link rel="stylesheet"href="../../basicPortrait.css" type="text/css"/>);}
  • SMS URI Scheme<a href="sms:+62812345678">Onenumber, no body text</a><ahref="sms:+62812345678?body=hello%20world">One number with bodytext</a>
  • SMS URI Scheme
  • Telp URI Scheme<a href="tel:+62812345678">CallMe</a>
  • Image Caching• All static images used in a web app are included in its .wgt file• There are no unused images in a web app’s .wgt file• All images in a .wgt file are scaled to the size used by the web app
  • Remote Device Access
  • Thank You! 