Monday, May 30, 2005

Design for Weblications (2)


Design Considerations:

  1. Visited Links: No need to change its colors, it’s preferable to specify the same color for the visited and unvisited links (user might fill out the same form many times).
  2. Hyperlinks and Buttons: You can include both hyperlinks for navigating to locations and command buttons for carrying out actions.
  3. Frames: You may use it, the case not sensitive like in content websites.
  4. Searching: web-applications are rarely involved searching except in the online help.
    Page Title: It might be the same page title on every page, perhaps indicating the page application name and version.
  5. Hypertext Linear Tasks: The users perform tasks, which may require linear paths. This requires a design that focuses on navigation among tasks rather than hypertext among pages of content.
  6. Scrolling: If moving from page to page requires lots of background application processing and the pages take a while to download, users may prefer one long form.
  7. Cross-Browser Considerations: Designers can specify a required browser, much like they specify the required hardware or operating system environment to give them more freedom of design.
  8. Browser Button: It’s preferable to hide them and the designer could provide alternative navigation method.
  9. Pull-down Navigation Menus: Not recommended in form pages to prevent the users to leave before completing the forms.
  10. Home Page: Contains the main menu, Product over view, splash screen contained a product graphic and version level also the copyright information and system statistics.
  11. Help: It’s more like the online help for (non-web-based) application.
    Open Browser In Full Screen: To eliminate the browser confusion where reoriented toward delivering a real application.
  12. Minimize the Use of Windows
  13. Use Rollovers: Revealing alternate choices or presenting additional information as it is needed and avoid user confusion by not presenting too many options at once.
    References:
  14. Use Alt-Overs: When the immediacy of a roller is not needed.
  15. Use Auto-complete: (WebDAV Technology) WebDAV notifications use UDP packets to notify the client that the Exchange store detected a subscribed event. The subscription command specifies the UDP port on which Exchange will contact the client computer. The client application must have a UDP listener running on the port specified on the subscription, so that the events will be received. Note that normal firewall configuration blocks UDP packets, so WebDAV notifications typically only work within an intranet, or over a PPTP tunnel.
  16. Use Login / Logout: Use login page and logout link throw the application
  17. Web applications with a Flash interface use the same applications (ColdFusion, Active Server Pages, or JavaServer Pages) to generate dynamic content, but the Flash movie can be updated seamlessly—no page loading is necessary. You can combine the power of the Web application scripting language with the power of ActionScript to change and update your Flash movies.

2 Comments:

At 9:21 PM, Anonymous Laurel Delaney said...

Dear Doaa,

How exciting! I will be sure to let Dr. Ray Smilor of the Beyster Institute and Karen Kerrigan of Women Entrepreneurs, Inc. know about your magnificent work. Feel free to advise your fellow MENA Internet Marketing workshop participants about your new business blog. I will track your mesages in the future for you have much knowledge to share with the world. Thanks for letting me know about this. Congratulations and best wishes for continued success!

Warmest regards,
Laurel
ldelaney@globetrade.com
Chicago, IL USA

 
At 8:37 AM, Blogger Doaa Saber said...

Thanks a lot dear Laurel for your nice comment and I really appreciate your encouragement, I I'll do my best to post all I have in this field and might help others in internet marketing and information design in general, all I need is your cooperation and exchanging experience to make it a success.
Thanks a gain

 

Post a Comment

<< Home