Skip to page content or skip to Accesskey List.
Search evolt.org
evolt.org login: or register

Work

Main Page Content

Making websites: what's your target audience ?

Rated 3.63 (Ratings: 2) (Add your rating)

Log in to add a comment
(7 comments so far)

Want more?

 
Picture of navjotpawera

Navjot Pawera

Member info | Full bio

User since: August 07, 2006

Last login: May 18, 2008

Articles written: 1

When asked the headlined question, most web entrepreneurs would serve an answer detailing a certain demographic of people. A website that sells computers might be targeting people who are in the IT industry, or even home users, while a college website might be catering to the students studying in that college. Every business has a target audience, even if it is "anyone and everyone". The might of the Internet is such that targeting any kind of demographic, be it a local group or even a global community is totally up to the discretion of the website owners. For a majority, this is the deciding factor to step into the on-line world with a website, but most end up being exceptions to the fact themselves. When a website is built that only serves people using a specific combination of web browser and platform, the website is forcing upon itself a demographic that does not always match the audience the business aims for.

Multiple browsers, platforms, media devices

When people started making websites, they were made to work in Microsoft Internet Explorer or Netscape Navigator. But over the time, the Internet has evolved in ways more than one. The way Internet is used has changed, the way people access the Internet has changed, the technologies used on the Internet have changed. People have started using newer platforms like mobile phones, televisions, and gaming consoles to access the Internet. The web browsers have changed, the older ones have evolved and they keep evolving on a daily basis. We now have not just two, but a number of web browsers. We have different web browsers for different platforms and media. This means that people are now using various different combinations of web browsers and platforms to browse websites, and thus the number of people using the "specific combination of web browser and platform" your website is optimized for, has also decreased.

Bringing order to chaos

So, does this mean that you keep track of all new web browsers, platforms and their combinations and optimize your websites to work in all of them? No, the constant evolution of Internet has led to the development of web standards - a central set of standards for various technologies. These are aimed at helping web browser vendors implement these technologies and web developers to use the same technologies. These web standards aim at making the various technologies work the same way on all different platforms, and user agents. In practical terms, web standards eliminate the need to follow the market for newer web browsers, web browser updates, and to update your websites to work with them. They form the converging center, being followed by web browser vendors and web developers alike.

Keeping pace

Hence, these web standards have also led to the evolution of the rules of doing business on-line. Instead of targeting web browsers or platforms, they give you the freedom of targeting the end customers, the real market of your on-line business. Making your websites compatible with web standards rather than a specific web browser would make sure your web sites work not only with majority of the web browsers but are also accessible by people browsing the Internet from various different platforms and media. All this said, there is however still work to be done. As we update our ways of making new websites, web browser vendors are also updating their browsers and tuning them to the latest web standards. So in this stage of transition, we need to make sure that the websites we make, work for all users. Also, we need to make sure the websites work, not only right now but in the future versions of various browsers as well. Here are a few pointers to keep in mind while developing websites today, and making sure they work tomorrow as well:

  • Develop websites using latest standards, and be wise enough to make them fully compliant to the respective standards as well. First make the website web standards compliant and then make alternative workarounds for non-standards-compliant browsers. Not the other way around.
  • To make sure that the websites work for all different users, provide fall back mechanisms for various technologies used on the website. e.g. if your website uses extensive JavaScript, then make sure that users who access your website from sources that do not provide JavaScript compatibility are served an alternative "JavaScript-free" version of the website.
  • When making provisions for fall-back mechanisms, do not filter your users on the basis of the browsers they are using. Instead, your filters should look for the specific properties/ technologies that your website uses. e.g. if different browsers right now support different JavaScript properties, then set up filters detecting for the specific properties and not different browsers.
  • Do not unknowingly cut out users by writing filters such as:
    if (browser is IE) {code for IE}
    if (browser is Netscape) {code for Netscape}
    
    With this code, users with browsers other than IE or Netscape will not be served anything.
    Instead, a better filter would be:
    
    if (property A is not supported){ code for browser not supporting property A }
    else { code for all other browsers }
    

Making sure your websites validate to latest standards is the easiest way to ensure that you are on the right path. This becomes even more essential when you are not a web developer, but are getting your website developed from someone else. Make sure your website is designed for the right target audience, the end customers, and not web browsers.

Related links:

For non-developers:

  1. http://www.webstandards.org/learn/articles/web_standards_for_business/
  2. http://adaptivepath.com/publications/essays/archives/000266.php

For developers:

  1. http://www.456bereastreet.com/archive/200512/ten_reasons_to_learn_and_use_web_standards/
  2. http://muffinresearch.co.uk/archives/2006/03/15/notes-how-to-convince-your-company-to-embrace-standards/
Navjot Pawera is a web standards and accessibility advocate. He works for Opera Software as a Web Evangelist. He maintains a personal-professional website at www.navjotpawera.com

Super stuff. Great article.

Submitted by cianuro on April 5, 2007 - 17:41.

Super stuff. Great article. The fact that standards compliance (And semantic markup) is being echoed can only be a good thing. More and more consumers (Of website design) are now a lot more educated, are demanding proper coding and compliance and that is only a good thing for the professionals in the industry. Also, new laws in various countries dictating that accessibility be law is also "Forcing" compliance. Again, that can only be a good thing.

login or register to post comments

Nice article. It would be

Submitted by EngrTun on April 10, 2007 - 22:38.

Nice article. It would be great if all browser just follow the standards .. its really annoying when a well validated code start messing in other browser. For me, I just test my websites in IE and FF, i hardly care about others.

login or register to post comments

I disagree with you,

Submitted by crazykat on May 3, 2007 - 03:20.

I disagree with you, EngrTun. My designs are tested in IE/FF - but also in all Opera flavors/mac OS/ and the like. Yes, I'm hired to code to standards, but I'm also ethically motivated to make sure my standards are accessible to everyone, even those with sub-standard browsers. IMHO, Kat

login or register to post comments

Its fine that you test in

Submitted by EngrTun on May 3, 2007 - 07:27.

Its fine that you test in other browsers as well, but I don't think there is anything i said you disagree with. I just test in 2 browsers and you test in 5 .. whats the point of disagreement? ;)

login or register to post comments

Here is more to consider about targeting the site

Submitted by Brad Henry on May 17, 2007 - 15:46.

This article makes for a good introduction to what could be a great resource. There are many other factors that go into targeting a website including but not limited to the function of your site. A couple of initial questions to ask would be "Is it an ecommerce site?" "What type of ecommerce system should you go with?" If it's not an ecommerce, is it recreational, informational, or meant for communication? How are you going to make money off your target market? Adsense or some other ad syndication?

Once all the details of how you plan to make money off the site are worked out, you have to lay out the directory and file structure so that it is SEO friendly and that starts with keyword research. Some of the best tools available for that are "Keyword Discovery" and "Wordtracker". By completing this task early in the development process and integrating how your target market searches directly into the directory structure, your site will ultimately be much more targeted.Another area of targeting involves a step that is completely external to your development process which is Link building. I won't go into much detail about that other than say that it is an important aspect of targeting any site.

login or register to post comments

Nice Article.

Submitted by edub on August 30, 2007 - 16:13.

Very nice article, well-written and conceivable. I'm a student and a professional. One thing I find "ironic" from standards-compliant zealot's, whom will not be mentioned, is they don't practice what they preach.

I see deprecated markup, transitional doctypes and inline presentational elements; whilst preaching about separation of content, presentation and behavior via XHTML, CSS and Javascript.

The adage of a well-known author, designer and developer preaches is:

Write once, publish anywhere!

Seems a bit ironic when they're not writing standards-compliant code?

Nice article Navjot. One day we'll get there, hopefully. Cheers, ;{) edub

login or register to post comments

Nice Article.

Submitted by edub on August 30, 2007 - 16:23.

Very nice article, well-written and conceivable. I'm a student and a professional. One thing I find "ironic" from standards-compliant zealot's, whom will not be mentioned, is they don't practice what they preach.

I see deprecated markup, transitional doctypes and inline presentational elements; whilst preaching about separation of content, presentation and behavior via XHTML, CSS and Javascript.

The adage of a well-known author, designer and developer preaches is:

Write once, publish anywhere when designing with standards.

Seems a bit ironic when they're not writing standards-compliant code?

Nice article Navjot. One day we'll get there, hopefully. Cheers, ;{) edub

login or register to post comments

The access keys for this page are: ALT (Control on a Mac) plus:

evolt.orgEvolt.org is an all-volunteer resource for web developers made up of a discussion list, a browser archive, and member-submitted articles. This article is the property of its author, please do not redistribute or use elsewhere without checking with the author.