2.  Why should it be mobile?  What content should I make mobile?  What need do I serve by making my content available to mobile users?  What value does it add to their lives from a mobile perspective?

3.  Defining the overall goals for the site. Business  What are your organization’s goals?  How does a mobile presence help your organization achieve its goals?  Does it improve my current business reach?  Does it provide new business opportunities?  Is there an opportunity for innovation?

4.  Defining the overall goals for the site. User  How does your audience benefit from a mobile presentation?  What tasks will they accomplish with your mobile content?  Does the immediacy of mobile help the user?  How will they interact with your content?

5.  Defining the overall goals for the site. Technical  Technology and resource opportunities and constraints.  Look at these goals as a triangle or three- legged stool. (business, user, technical)

6.  Understanding the needs of users helps humanize the process and keeps your project in check with their goals.  Users know best and will cast their vote by giving their attention to your site – or not.  Think about how and where people will interact with your content or application.  What content would they want to get through a mobile device?

7.  People accessing the site from a mobile would probably want a textual menu, location and directions, contact information and hours of operation.  Providing the day’s specialties on the site would be a good feature to offer – with the phone number on the same page.  Technological constraints should verify the capabilities of the user's device before offering  features like online ordering and a PDF- based menu.

8.  Knowing your audience is an important principle in developing your mobile web strategy.  It is important that you understand what your audience is looking for. so you can anticipate how they will want to navigate your site, and so provide them with quick and efficient navigation.  Analyzing demographic and market data on your target audience.

9.  In the mobile context it is especially important to structure information as simply as possible.  Placing the right information in the right place is an important part of providing a usable experience

10.  While building the mobile information architecture, think about users’ “click investment”.  Even at 3G speeds data retrieval on a mobile phone takes significantly longer than we are accustomed to on a desktop PC.  Every link should use clear labels to communicate to the user what to expect on the resulting page.

12.  Limit choices. Take the content that’s relevant to a mobile user and discard the rest.  Create a simple site drill-down architecture, nesting content into well- labeled categories.

14.  Limit categories as much possible  Attempt to limit links to ten per page unless you know that the device can present more information well  Provide at least one content item with each category page i.e. avoid empty links  Prioritize links by activity or popularity

16.  Once you determine your content requirements and define your category structure and labels, compile them into a simple site map.  This gives you a high-level overview of your information space.

17.  An important difference between developing for mobile and developing for the desktop is creating the right flow of information for the user.  Due to the limited screen size, the mobile designer might need to spread out information into multiple pages rather than present it on one page.  A welldesigned click stream is an important concept in mobile design and development.

18.  Designing for Different Screen Sizes  Designing for the Right Device. Feature Phones Smart Phones PDA Voice Only Phones  Mobile Web Navigation Paradigm use a simple vertical list of options, often assigning and listing the corresponding numbers (0–9) to the accesskeys for keypad navigation.