Archive for February, 2010
There has been much complaining on the web about how iPad doesn’t support multitasking, and little analysis of why Apple doesn’t allow it. Adam C. Engst wrote up a great analysis of the types of benefits that multitasking can provide and what technology is required to achieve those benefits.
I’d like to approach the question of multitasking from the user’s perspective and not from a technology standpoint. How would allowing third-party background processes impact the user experience?
Games Don’t Want Multitasking
Game consoles don’t allow third-party background processes, period. Even first-party background processes are limited. Xbox 360’s dashboard and PS3’s XMB is the interface to access system functionalities while playing a game. Both systems also reserve a small amount of memory and CPU to run system functionalities.
The reason why consoles take such extremes to limit multi-tasking is to give games consistent hardware performance. Games typically pushes the performance of the system to the limit. When a game updates at 60 frames per second, a small decrease in performance will drop the frame rate to 30, which is immediately noticeable by the player.
Now imagine a game developer writing games for the iPad. It would be impossible to squeeze every ounce of performance out of it if at any point a random third-party application can wreck your performance and turns your game from running smoothly to slowing to a crawl.
For this reason alone, I don’t think any iPad application should expect to be running in the background at all times.
Multitasking on iPad
Believe it or not, there exists an API that manages multitasking on the iPhone. It is called Audio Sessions. An application can claim exclusive access to hardware audio codecs and stop the iPod application from running in the background by setting the appropriate audio session category.
I think this could be a glimpse into how Apple will implement multitasking on the iPad. Apple can define a set of categories for multitasking and each application will set it’s category to the most appropriate one.
Here are some categories which I think might be usedful:
- Multitask Session Default – allow other application to run in the background with the current application. Quit the current application when the home screen is brought up.
- Multitask Session Background – allow other applications to run in the background and also wants to keep running when another application starts, maybe quit if an exclusive application starts.
- Multitask Session Background Resume – Same as background, except restart the application in the background when possible, i.e. after an exclusive application stops.
- Multitask Session Exclusive – Do not allow other applications to run in the background. Quit the current application when home screen is brought up.
By defining the multitasking behavior through the API, Apple will still have complete control over the user experience, without exposing the complicity of managing processes to the users.
The Apple Way
I am just conjecturing how Apple might add multitasking to the iPad. I don’t have any sources inside Apple. However I believe that Apple will provide the best possible user experience when using the iPad. If they determine that multitasking will decrease the overall user experience then they will not add it.
Like the Cut-and-Paste complaints of a few years ago, Apple will wait until it finds the best possible way of introducing a functionality before adding it. That is the Apple way.
In part 1, I wrote about how to create a static home page for the top level of your website, with all of your blog related pages under “/blog” path. This article is about building out the rest of your site using static pages and adding a navigation menu by selecting the right theme.
Before moving on, you should add a few more pages to your site, something like this.
- Subproduct 1
- Subproduct 2
Of course you should change the names of the pages to suit your needs. Make sure Products is a parent page to Subproduct 1 and Subproduct 2 by setting the Parent attribute of the sub pages.
Finding a Theme
Now that you have some content on your site. It is time to find a theme that you like and to display the site navigation in a way you require.
The important part of selecting a theme is to make sure it uses the page hierarchy as navigation items instead of the post categories. So when previewing the theme, make sure the navigation looks like this:
Instead of this:
You want to provide easy navigation to your pages first, and your blog second. Another thing to look for is a drop down menu to display hierarchy of pages.
It is much easier not use the drop down menu feature than to add it later by hacking CSS to add it to the theme you selected.
Managing Your Navigation Menu
Now that your navigation menu is tied to your page hierarchy, you should use a plugin to manage it easily. I use a plugin called pageMash. It allows you to hide pages you don’t want to display in the navigation menu, as well as drag and drop to modify the page hierarchy.
In addition to managing the page hierarchy, you also need to manage the label of the page in the navigation menu vs the title of the page that’s displayed when you view the page. My about page’s actual title is “About AlwaysOn Technologies” but navigation label is just “About”.
This ability is added by another plugin, All in One SEO pack. This plugin has more features than I can get to in the article, you can dig deeper into it in tutorials. All we are going to do for now is set the Title, which will be label displayed on the menu.
Adding a Contact Page
To making contacting you easier, you need a contact page where users can send message directly without having to fire up an email client. Thankfully, there are plenty of plugins that will create a contact form for you. The one I used is Contact Form 7 which uses markup to create the form so it is very flexible.
By now, you should have a functional website that the users can actually navigate and contact you. The next article will be about sending your site information to search engines and leveraging social media.
WordPress is a popular and well supported blogging platform and I’ve been using it for years for blogging. Now I am using it to build up a small website.
I am getting ready to launch an iPhone application called Cloud Browse and need a web presence to promote my company and the product. Since I am going to blog on this new site, using WordPress to do everything makes a lot of sense.
I am going to write step by step how I got my site up and running, along with the plugins I used to and why I chose them. My site is very simple so hopefully it will be useful to others to get started before diving deeper with other articles.
The Basic Steps
Disclaimer: I am using WordPress 2.9.1, so if you are using an older version, the steps I am using may not work for you.
A plain WordPress install already include all you need to get a simple site up and running. Assuming you want a home page at http://example.com, and the blog at http://example.com/blog, just follow the steps below. I’ll describe what each step in detail after.
- Add two pages called “Home” and “Blog”
- Go to Dashboard > Settings > Reading and set the Front Page Display to “A static page” with Front Page as “Home” and Post Page as “Blog”
- Go to Dashboard > Settings > Permalinks, change Common settings to “Custom Structure” to “/blog/%year%/%monthnum%/%day%/%postname%/” and set Optional > Category Base to “blog/topics” and Optional > Tag Base to “blog/tags”
If you’ve been following the steps, now you should have a basic web site displaying the “Home” page at the top level, and a regular blog under “/blog.” Read on to dive into what each of the steps actually did and how to customize each step.
The Gory Details
- The Home and Blog pages are required for step 2. The title of the home page isn’t important, but the contents of the page is what gets displayed at the top level of the site.The title of the Blog page is important since it is what determines the path the blog shows up under, more specifically, it is the slug of the page that determines the path. So if you want your blog to show up under “/diary” then make sure you name your page “Diary.”
- Front page displays is the important setting that allows the blog section of your site to be separate from the rest of the pages. WordPress will show the Front page as the top level content and the list of of blog postings when viewing the Posts page. WordPress won’t even display the contents of the Posts page so don’t bother putting any content in it.
- Using a custom permalink structure is important for two reasons. One is so users can see the title of the post within the url, which is also important for search engine ranking, and the second is so all blog posts shows up under “/blog”. You can customize the structure but be sure to start with “/blog.”Setting the Category base and Tag base is again to keep all blog related urls under “/blog.” If you don’t set this, the default url would look like “http://example.com/categories/a-category.”
Now you’ve got enough knowledge to start a basic site using WordPress. The next article will focus on creating a site structure by adding more pages and setup the navigation menu.