Web Design and Graphics

In creating a website we should plan first what is the purpose of making of this website, what information will be provided and to whom information is addressed. Macromedia Dreamweaver is one website making program that have a lot of menus and tools that can be used to design websites that are more creative, you can create a complete site. To get better results, you must design and plan in advance for your website each existing site pages. you may configure your webhosting for best web performance

When starting to plan to create a website, you need website hosting are expected do it gradually and systematically to ensure your site well and successful. Although you will only make homepage person who will only be seen and visited by friends and your family. For those of you private site lecturer, you can use to provide information and services online teaching for your students.

Determine your site goals is the first step that must be you take to making a website. Ask yourself or your colleagues on a website. What do you expect when you have a personal site? Write down all your goals and expectations so that you can remember when the process of designing websites. Goals will be helpful for you to stay focused and have target of the website you want. A website that provides news with a particular subject is very different from the websites that sell products or commercial.

After you determine what you want to accomplish your website, you must determine who is, or target Your site visitors. Actually this is a stupid question, who alone in the world can visit your site. Many people use browser is different from one another, at different speeds, and have or do not have media plug-in additional (example = speaker). All these factors may affect the use your site. Then you must determine the target audience, after which can design your website. Choose your web hosting directory wisely.

Internet years are like dog years; much, much shorter than calendar years. This directs to the somewhat sore entrance that no web project can function in terms of long timescales. A web -application that gets two years to enlarge will be obsolete long earlier than it is released. In fact, in our experience, the life of a web project is more frequently deliberate in weeks than in months. The pace with which web projects have to be finished clearly puts the association under substantial stress.

Very frequently the clients don’t know precisely what they want to attain through the web application. They might not even have a plain thought of the target users. They very over and over again perplex their own purposes with the user’s causes for using the application. They are concerned about hackers and viruses, but want to present highest entrance to their users. The difference between yesterdays internet projects and the web applications of today is the truth that the latter carry the user’s errands, in dissimilarity to just providing in order and advertising jive.

Web technology, while in a stable state of development, places some serious restraint on web – applications. mainly in judgment to stand -alone applications that run on a normal P C. Very little “cleverness” or program logic can be programmed in the web application, error handling is very poor and the border is made up of chronological conversation. These issue, and many more, can make scheming a usable boundary quite challenging though not unfeasible.

So the average web project is often faced with
- clients and users who frequently have very fuzzy ideas of what they really want to attain.
- a disparity between the client’s and the users’ objectives. – technological fetters that confront the idea of functional applications.
- high expectations the web developers should create something concrete within tremendously short time -spans.

These cost-effective, technological and managerial constraints often result in an approach that can look like the Wild West.

The mobile phone has hard to believe reach – users have their phones with them at home, in the car, at work, in the store. Mobile devices are used on the go, are geographically susceptible, and are chiefly used to regain context-sensitive information swiftly: looking up a phone number, examination an address, reading a restaurant assessment, or finding a map and directions. Because the mobile atmosphere is a overwhelmingly different experience, it does not make sense to basically point mobile users to a fixed website and miss out on the exclusive potential of the mobile environment. Designers must not think of the mobile location as a poor proxy for desktop sites and applications. in its place, we must consider what works best within the context of real-world mobile browsing, and transport happy and functionality customized to the platform. In some cases, this means offering a separation of satisfied and functionality. It might also mean contribution satisfied and functionality sole to the mobile platform. Benefits of the Mobile Web

• Portability
• Location awareness (GPS)
• Accelerometer (measures tilt and motion. It is also competent of detecting turning round and motion wave such as swinging or shaking)
• nearness sensors (The iPhone screen blacks out when you put it to your face)
• Electronic scope
• Picture & video ability
• Phone connection and the ability to move faultlessly from browser to phone
• Multi-touch gesticulation support & content whooshing
• World-wide market dispersion

Challenges of Designing for the Mobile Web

When designing for the mobile Web, broad usability and convenience principles for the desktop surroundings still apply:

• Deliver useful and forceful content
• Give functionality and design that fit the user’s context
• Write standards-compliant XHTML and CSS code
• Follow convenience rule
• Use clear and brief language
• Make the site easy to steer

Some of the confront we face with the mobile platform include:

• difference in machine usability
• lesser screen size
• diversity of screen sizes
• many browsers
• Connection speed and dependability
• Lack of peripherals
• Input dissimilarity
• One-handed organize of devices

The number of users browsing the Web from a mobile device continues to rise, yet most mobile web sites are still sub-par.

The thing is, creating a great web experience for users of mobile devices is much easier than you might think. In this article I’ll introduce seven fundamental steps that, if followed, will help you avoid the pitfalls that have caused many other mobile sites to fail. By the end of this article you’ll know exactly where to focus your efforts in order to build a successful mobile site.

1. Don’t Mix Up Your Markup

A few different types of markup are available for building a mobile web site. You’ll need to choose one that suits the needs of your customers and stick with it.

WML

In the early days of mobile web devices, the only way to surf the mobile web was to browse WAP (Wireless Application Protocol) sites. A WAP site uses WML (Wireless Markup Language) as its primary markup language. WML is an XML markup language based on the card-and-deck metaphor.

Luckily for us, WML has since been superseded by several other technologies — in fact, if you’re just getting into the mobile web game, you can probably ignore WML entirely. WML is mostly used by legacy systems or by sites that explicitly target customers with low-end phones that are six years old or older.

One potential group of customers still using WML browsers, however, is those in developing nations. TheNokia 1100 and 1101, for example, are extremely basic, extremely cheap phones, of which an estimated 200 million units have been solid worldwide, making this phone the best-selling model to date, worldwide. If your site is targeted to this market segment, WML might be the best solution for you.

XHTML

For most sites, we can ignore WML and make use of a markup language with which you’re probably much more familiar — XHTML.

Most built-in phone browsers these days can handle XHTML just fine. A mobile phone recognizes two flavors of HTML:

1. XHTML — the same, basic XHTML rendered by desktop web browsers




2. XHTML-MP — the MP here stands for Mobile Profile

The difference between these two languages is that XHTML-MP consists of slightly fewer elements and tighter restrictions. These differences exist to make it easier for the mobile device to parse and render a web document, but writing XHTML-MP markup shouldn’t introduce any significant changes to your process for writing regular XHTML.

Anecdotally, when my team and I develop mobile web sites we usually use regular XHTML, and this approach has served us just fine.

2. Know Your Phones

As plasma and HD TVs slowly hit the market, broadcasters have run into the problem of where to place their logo and news tickers. Previously, they knew that all TVs were the same 3×2 dimensions, so they knew the relative width of the screen. Now, they’re beginning to feel the pain of dealing with a wide assortment of TV resolutions and dimensions — an issue that web developers deal with on a daily basis.

Of course, the mobile world is even worse! Not only must we cater for different screen sizes and resolutions, but also different shapes, as Figure 1 illustrates. From rectangles that are short and long, to those that are tall and skinny, to perfect squares, the mobile world contains a rich tapestry of variation that almost makes you want to pull your hair out!

If you consider the most common phones available, they can be categorized on the basis of screen size — give or take a few pixels:

• 128 x 160 pixels
• 176 x 220 pixels
• 240 x 320 pixels
• 320 x 480 pixels

Knowing these screen dimensions helps you optimize some of your content, however it’s best to keep the shape and style of your site as minimal and linear as possible. There is no mouse on a mobile phone — only an up-down feature — so you can’t demand that users jump around the page.

iPhone/Internet-tablet versus old green-screen phones

There are a couple of exceptions to the norm in the mobile phone market. They are the really high-end devices like the iPhone or the Nokia Internet Tablet, and the very basic, old “green-screen” monochrome dot matrix devices such as the Nokia 3310,

Low-end mobile phones have several limitations, including screen resolution and a severely limited ability to render XHTML documents. As I mentioned in the previous section, if a majority of your customers fall in this group, then maybe WML is still for you.

At the other end of the spectrum, high-end devices often have the ability to run a web browser that’s comparable to one you might use on a desktop machine. Delivering a quality user experience to these devices can be tricky — while the device may be perfectly capable of rendering a full, traditional web page design, it’s probably transmitting data over a cellular network, which is much slower than standard broadband Internet speeds. So even though the device can handle a normal web site, the customer’s situation and the reason why they’re requesting your services may mean that sending them the normal version of your web site isn’t the best solution.

We’ll see in the next section what this means for the design of your mobile site.

3. Target the Right Customers

The goal for any web site should be to know your customers in order to deliver to them the most appropriate content.

This goal is even more important with mobile sites — not only do you need to know your customers, but you need to know what they are likely to be doing on your mobile site, as well as where they’ll be when they’re doing it. Traditional web site customers are most likely sitting at a desk facing a large monitor that has a decent resolution. Visitors who are browsing your mobile site are unlikely to be in the same circumstances — they might be waiting in line, riding on the train or the bus, running to the departure gate, or lost in an unfamiliar town late at night and trying to get somewhere.

Google is one company that has invested considerable effort into streamlining its web applications to suit mobile users. The web developers at Google have identified and focused on three main groups, and they attempt to target their applications to those customers’ needs. These are three solid categories, and are worth examining for your own mobile site. Let’s look at them now. Buy mobile phone with payday advance