Archive for August, 2011

Websites Shouldn’t Look The Same Across Different Browsers…Here Is Why


  

Not long ago, on our sister site Smashing, we had a post discussing the communities adoption of HTML5 and CSS3 before they have become standards, and during that dialog we stumbled across another point that needed a bit more diving into. It was proposed that client’s expectations are somewhat unrealistic when it comes to their websites looking the same across all browsers and systems. This is not only something that the client is more than likely not going to be too happy to hear, but as it turns out, this is also a topic that some of us in the design and development communities are uncomfortable broaching with our clients.

We believe that the client will not want to hear what we have to say or that they will see this as a positive, so we often refuse to speak such evil. Image Credit

For whatever reasons, some members of the community, who may believe in this idea themselves, find it nearly impossible to explain to the client so they make no attempts to. They simply spend countless hours and suffer through numerous headaches trying to appease this unreasonable and unnecessary client standard which is in point of fact, looked on as an impossibility within the community. So why is it that we have a hard time explaining this understood truism to clients? The answers to that question are nearly as numerous as the reasons themselves that a webpage cannot look the same. So we hope to handle this for you.

This post came about with a focus on our clients and getting them to understand this idea, so that we can use this article as a guide for when we need to explain this to them, or as a reference that we can direct our clients straight to for their own benefit. We have approached the post with two basic fronts to take on in this discussion. Why a site can not look the same across different browsers. And why a site should not look the same across multiple browsers. Both of which are important to understand as we move forward in this dynamic and ever-changing landscape.

The Reasons Why it Can Not

First we are going to look at a few of the reasons why a website simply can not look the same across multiple browsers, because at the core, these are really the ones that should matter the most. It would be one thing if we were misleading the client or fooling ourselves into accepting this idea when it actually were possible to achieve, but that just is not the case. And here is why…

Vendors and Standards

One of the main reasons that a site will have some variance comes down to the basics, the multiple vendors and the standards they adopt per each version they release. Given that there are so many different options for browser, each with their own set of out of the box specs, you have to expect that there will be elements and design accents that do not fully display or function the same way across the various machines it will be viewed on. That is just an unfortunate truth of the industry right now.

Instead of looking passed this roadblock at all of the potential and possibility that lies beyond it, we allow these vendors and slow standard adoption to stop us in our progress. Image Credit

Especially given the W3C’s slow process of implementing new standards, vendors are often reticent to dive right in and put these cutting edge techniques into full practice. Which is decidedly their choice, but it has been said that the more the design and development community push the vendors to move forward, the better our chances of getting these new standards put into practice will be. But we need our clients to be on board with us to allow for this growth, and we need to help them to understand this landscape we are working in. One where certain areas of consistency have to be sacrificed.

Plugins and Addons

Not only are there multiple vendors making different browsers for the online market, there are also a massive amount of plugins and addons that will not only enhance the experience for the user, it can effectively alter the look of the sites opened up within its tabs. This is something else that we have to consider when trying to achieve this uniformity of presentation across the vast spectrum of browser options.

One of the main areas where we see concern from clients on this tends to come from that handy little ad blocker plugin which prevents ads from displaying and often times stops pop-ups from showing up on the page as well. When clients are seeing this for the first time, without any kind of heads up or a warning from us, they are not always going to have the best of reactions. This is why it is important to explain to our clients the various ways that their site can be impacted, or even just that they can be impacted by said addons and plugins. This way they have an idea of what to expect.

Individual User Preferences

Not only can the different browsers and browser addons effect the way a site is rendered from machine to machine, but so can numerous other individual user preferences. This can be a wildcard that can have various impacts on the site’s presentation that most clients may not consider when they are planning the approach they want to take on their site. Most of us take our own experience for granted, believing that this is the same experience every user has when they venture out on the interwebs, and that goes the same for our clients. They may be operating under this same assumption and we need to point out how unrealistic and unreasonable this perspective is.

Standard and Widescreen Devices

Another factor that can have more minor impacts on the way the site looks in the browser, but impacts nonetheless, are the plethora of screen sizes from device to device and user to user. From standard to widescreen devices, the screen size can determine how much of your site is displayed at any given time. Controlled by the user, who can freely adjust their browser window to further relegate your site into a smaller viewable surface. Clients might forget to take these considerations into account when they are formulating their ideas to kick off the process.

Sometimes we forget that our setup is not always reflective of every users hardware and we forget that there is more than one kind of display device in use. Image Credit

They need to know about these possibilities and the impacts they could have on the site. For instance on a blog, some designs with sidebars have the sidebar move to beneath the main content area should the browser window be scaled down enough. This is not often something we think about letting the client know, but if they happen across it on their own they may become slightly disturbed with no context or understanding about said positioning adjustments. Though these may not be regular issues faced, these are just further examples of the small details that can impact a site’s presentation from browser to browser.

The Mobile Market Factor

If ever there has been an entire market that has opened up beyond expectations to completely flip this truism on its head and give us an easy example that helps to prove this rule, then the mobile market would be the one. This quickly growing market has taken the web to interesting new heights and altered the basic approaches that we have taken to designing and developing websites And the entire market exemplifies the point we are trying to get our clients to see. Especially in the wake of this unforeseen X factor.

Not only has the mobile web caused us to see this idea much more clearly, but it also allows for the idea to be more easily digested and embraced by our clients. Mobile devices have seen a much more scaled back approach to the web being taken on sites, not just with the appearance, but also with the usability of the overall experience. The way users interact with a site and relate to and receive the content is much different, and thus requires an approach that compliments this smaller, generally touch navigated presentation. Once clients can see and accept this variance, others might be easier to digest as well.

The Reasons Why it Should Not

Now that we have gone over a handful of the reasons why having a site look the same across multiple browsers and devices can not be done, we are going to go through a few reasons why we should not even make this attempt at a visual consistency that will not be achievable. Beyond just the fact that it is not possible, that is…

Usability Matters Most

First up we are going to talk about usability. The look is certainly important to any website, but the look is always trumped in importance by the overall usability of the site. That is just a given. We can have all the fancy design elements in our work that we want, but in the end, how it works is the more vital aspect that needs to be consistently looked after. That is how we should view these projects, focusing not on if they look the same in every browser, but that they basically function the same way in every browser.

We have to remember that the way it looks is not as vital as the way it works. Every cog should be firmly in place. Image Credit

This is the point that we should be stressing to our clients when we are trying to get them to accept and allow for this variance in the look of the site. That these minor differences in the form are not going to be the main focus of the user, and that is who should matter to the client. No, the users are going to be concerned mainly with the function, and so should we. In this case, the appearance of the site is completely secondary.

It is What Necessity Demands

Just as necessity is the key to innovation, it is also key in steering our design and development decisions, or rather it should be. In other words, necessity should always be the key to our motivation when we are designing or developing a project. And just as we discussed, with the mobile web explosion, it is necessary to have and allow for these variances in the sites that we build. Otherwise, we are relegated to a much more stagnant industry that refuses to grow because we are sacrificing innovation to achieve a uniformity that is unnecessary and unreasonable.

So long as we are operating under this principle of doing whatever is necessary to deliver the best possible solution for our client’s and their user’s needs, then we should have an easier time explaining to the client why these differences have to be allowed. There is no since in wasting valuable energy trying to pull off something that is not going to come together in that idealistically dreamy way, when we can clearly see it is not necessary. For it is impossible.

Every User Counts

Another reason that we should easily be able to get the client to see why this approach should not be attempted is because every user counts. In trying to achieve this universal presentation, there are often going to be compromises made that will inevitably slight one segment of the audience in favor of another. However, it does not have to be that way. We need to remember that every user’s experience matters, and they should be able to get just as much enjoyment and use from the site as everyone else.Even if that means helping them along to a better browser that will allow them to do so.

We want to keep each user in mind and try to find the best way to deliver a solid experience to them that we can. Image Credit

This is not always in the user’s control as they are not always using their own machine, however, as long as we provide them with a quality experience then letting them know it could be even easier and more enhanced via another choice of browser is not forcing their hand in any way. We have simply provided them with an alternate course of action in a friendly, unobtrusive manner that shows we care about the experience they had on the site and are looking for ways to give them more. If we hold back anything from a segment of the online audience because others are not caught up with them, then how is that giving every user the optimal site performance? It’s not.

The Hack Factor

Though it is done on a fairly large scale, having to include vendor specific hacks in your code in order to have the site rendered ‘properly’, which in this case just means the same as it does every where else, is not the best course of action. Instead having natural degradations of effects and elements is the more preferred and natural way to have the site coded and presented. Sacrificing this idea of having the site look the same across the board tends to call for a bit of hacked code, which if you or your clients are concerned with validation, may not work to your overall advantage.

A Sign of Being Behind the Times

Another consideration that needs to be made by the client is that if we have to hack, and slight our way to this visual synchronicity then the site may be compromised into a more dated, less than cutting edge style and feel. By not allowing for the pushing of envelopes for those users who can gain the full experience the site could seem like it is somewhat behind the times, at least in comparison to other competitors that your client is up against.

Clients tend to want to put forward an up to date, fresh face to the world. They want to remain relevant, not feel like a relic. Image Credit

Not saying that is how it will always be seen, but there may be instances where it does reflect poorly on the company and their ability to stay ahead of the game and on top of the markets they are operating in. Users are going to be more apt to put their trust in a brand that they view as able to keep up with the changes in technology. If your site gives the impression of being behind the times, then you might find that users are going to be moving on and looking for a company that they feel is more on the edge, not sluggishly bringing up the rear.

Never Fear: Benefits Made Clear

Now sometimes we find ourselves afraid of accepting this idea, believing that we are still somehow compromising the site, but never fear, we have singled out a couple of points to briefly retouch on below to make sure that we drive them home and perhaps help put your minds at ease helping you to see some of the benefits of this acceptance to point out to clients.

Still Connects with Consistency

Though the site may slightly change in appearance between browsers and devices you can still have that connection of consistency through other elements that are able to remain unchanged. So this approach does not sacrifice the consistency that we have all held up as a guiding principle in our work, it just comes at it from a different approach. One that keeps after what tends to matter most to your users, the usability.

Time and Money Saver

By accepting this path of variance the project can actually be offered a bit of a break on the time it takes to put together and test out. Which tends to translate into money saved on the client’s end, which is usually an easy sell. Without having to track down hacks and such to keep the site visually identical between browsers the project can progress more smoothly and in a more timely fashion.

Embracing Innovation

As previously mentioned, by compromising the site to keep up this universal appearance regardless of the browser it is displayed in can make the site feel less than innovative, and can thereby reflect poorly on the client’s business. So by allowing for this visually varied approach you can create a sense of embracing innovation, making the company seem more progressive and forward thinking to some of their users.

That’s a Wrap!

So that is a basic breakdown of the reasons why we can not and should not try to make a website appear the same across the vast spectrum of browsers that populate the market today. Hopefully it has given you some ideas on how to broach this subject with your clients, or allowed for a place that you can direct them to read up on this discussion for themselves. Go ahead and let us know what approach you have taken or would take with your own clients in the comment section below.

Consider Some of Our Previous Posts

(rb)


Techniques For Gracefully Degrading Media Queries

Advertisement in Techniques For Gracefully Degrading Media Queries
 in Techniques For Gracefully Degrading Media Queries  in Techniques For Gracefully Degrading Media Queries  in Techniques For Gracefully Degrading Media Queries

Media queries are the third pillar in Ethan Marcotte’s implementation of responsive design. Without media queries, fluid layouts would struggle to adapt to the array of screen sizes on the hundreds of devices out there. Fluid layouts can appear cramped and unreadable on small mobile devices and too large and chunky on big widescreen displays. Media queries enable us to adapt typography to the size and resolution of the user’s device, making it a powerful tool for crafting the perfect reading experience.

CSS3 media queries, which include the browser width variable, are supported by most modern Web browsers. Mobile and desktop browsers that lack support will present a subpar experience to the user unless we step up and take action. I’ll outline some of techniques that developers can follow to address this problem.

Broken-Media-Queries in Techniques For Gracefully Degrading Media Queries

It Depends

If you’re looking for the more honest, truthful answer to pretty much any question on web design and usability, here it is: It depends.

– Jeremy Keith

There is no one-size-fits-all fix. Each project has its own focus, requirements and audience. This article will hopefully help you make the best decision for your project by outlining the advantages and disadvantages of each solution.

Mobile First

Your chosen implementation of media queries will have a big effect on how you tackle this. Mobile-first responsive design is the process of building a mobile layout first, and then progressively modifying the layout as more screen space becomes available. This ensures that only the minimum required files are loaded, and it keeps the mobile solution lightweight. Mobile first has the advantage of providing a nice fallback for mobile devices that don’t support media queries, such as older BlackBerrys, Opera Mini and Windows Mobile devices. These devices simply see the most basic layout, with no extra work required of the developer. Ideal!

Technique 1: Do Nothing

Sometimes the lazy approach is the best approach. It keeps your code light and maintainable and reduces any needless processing on the client side. Some old browsers run Javascript like a dog, and old mobile phones struggle to run intensive Javascript. The proprietary non-Webkit browser in most BlackBerrys can take up to eight seconds just to parse the jQuery library. If your project has a long tail of users with low-powered mobile devices, then maybe a mobile-first approach is enough for you.

The elephant in the room is Internet Explorer for the desktop. With a mobile-first solution, large screens will display the content in one column, resulting in a painful reading experience for the user, way past the established maximum for comfort: 50 to 75 characters. It might be worth setting a max-width property in your main container and then upping that max-width in a media query.

#container {
 _width: 460px; /* Take that, IE6! */
 max-width: 460px;
}

@media only screen and (width) { /* A quick and simple test for CSS3 media query support. */

#container {
  max-width: 1200px; /* Add the real maximum width here. */
 }

}

Do Nothing If…

  • Your core audience uses modern smartphones,
  • You are required to provide an acceptable experience to a long tail of feature-phone users,
  • The desktop is not a big part of your Web strategy.

Example: jQuery Mobile (“Any device that doesn’t support media queries will receive the basic C-grade experience�).

Technique 2: Conditional IE Style Sheets

Surprisingly, in researching this article, I found this to be the most popular technique in use on responsive websites. Instead of polyfilling support for media queries, you simply load an additional style sheet only for Internet Explorer. For mobile-first approaches, this usually entails loading a basic style sheet that sets up a multi-column layout for large screens. Jeremy Keith documents this approach in detail on his blog. He also adds a condition that doesn’t load the style sheet for mobile versions of IE. Crafty.

It’s a simple and effective technique for supporting Internet Explorer on the desktop, and it supports the mobile-first approach because it loads a light and appropriate linear layout for feature phones.

On the other hand, this technique could potentially degrade maintainability, requiring you to maintain a style sheet of duplicate content. It also adds another HTTP request for IE users, which should be avoided if possible.

I’m surprised that Jeremy Keith advocates this technique. The man who proclaimed on stage that user-agent sniffing is “the spawn of Satan� is using a solution aimed squarely at one browser. Bear in mind that this does not work with browsers that do not support CSS3 media queries. But it can be perfectly acceptable in situations where support for other legacy browsers is not required.

Use Conditional IE Comments If…

  • You are using a mobile-first workflow;
  • Your media queries are simple enough to include in a single style sheet;
  • Desktop Internet Explorer requires a multi-column layout, at the expense of speed;
  • You do not have to support a long tail of legacy desktop browsers.

Example: Huffduffer, a mobile-first approach with an additional column for screen widths over 480 pixels.

Bonus example: Designing With Data by Five Simple Steps. I love these guys.

Technique 3: Circumvent Media Query Conditions

The Opera Developer Blog published an article in 2007 detailing the safe usage of media queries. It helped pave the way for CSS3 media query usage by presenting research on the correct way to write them, a way that prevents browsers from applying the containing CSS when they do not understand a media query.

… Browsers like IE.

But what if, with a mobile-first approach, that’s exactly what we do want? What if we were to write our media queries so that the containing CSS gets applied by IE unconditionally. We could then have our full desktop layout without any additional style sheets to load or maintain.

@media screen, all and (min-width: 300px) {
	div {
		background: blue;
	}
}

As the blog post states:

Now it is no longer the case that IE does not apply the contents of the query. It now doesn’t understand the second part (all and), so it ignores that and happily applies the contents of the query…

Circumvent Media Query Conditions If…

  • You are only required to support modern smartphones,
  • You are building mobile first and require a desktop layout in IE,
  • Loading time and maintainability must be kept to a minimum.

Technique 4: Respond.js

Scott Jehl’s lightweight polyfill Respond.js offers a leg up for browsers that do not support CSS3 media queries. It can be compressed down to as little as 1 KB, and it parses CSS files fast, without needing any additional libraries.

JavaScript reliance aside, Respond.js appears to be a solid solution for full support of media queries. However, the small file size and speed come at a cost. Respond.js was never meant to be a full-featured solution. Its purpose is to provide the bare minimum for responsive layouts to work.

It supports only the min-width and max-width queries, so it’s not the right solution if you are looking at using device-width, device-height, orientation, aspect-ratio, color, monochrome or resolution. Some good use cases here are not supported, one being the detection of high-resolution devices such as the iPhone 4 and non-color devices such as the Kindle.

Respond.js does not support em-based queries, which makes impossible any decent support for font-size user preferences (even more important on a small screen than on a desktop). Products like Readability and Reeder validate this desire among users to control and refine the reading experience. Em-based media queries will become only more important as we head towards a content-first approach to Web design, so they are worth considering.

There are a lot of small bumps and caveats with Respond.js. I recommend browsing the read-me text and the issue queue before settling on it for you project.

Use Respond.js If…

  • Desktop support is your primary concern,
  • You are querying only the width and height of the browser,
  • You don’t want to query the width by ems,
  • You have no problem with non-JavaScript users seeing an unoptimized page.

Example: Aaron Weyenberg, a desktop-centric website with a basic layout.

Technique 5: CSS3-MediaQueries-js

CSS3-MediaQueries-js picks up where Respond.js leaves off. It supports the full range of media queries introduced in CSS3. The “everything and the kitchen sink� approach is great for a developer’s peace of mind. Simply drop it in, and tick the “IE support� box.

But there are significant downsides to consider: this script is not fast; it parses CSS much slower than Respond.js; and it weighs in at a hefty 15 KB.

Pro Tip 1

Let’s be responsible and load this file only if the browser doesn’t actually support CSS3 media queries. Otherwise, you’re wasting good time and data. You can use Yepnope to load the 15 KB file if it detects that media queries are not available.

Here’s a modification of a Yepnope function that I wrote for Modernizr’s media query test. Yepnope now comes bundled with Modernizr.

yepnope({
test : Modernizr.mq('@media only screen and (width)'),
yep  : '',
nope : 'css3-mediaqueries.js',
});

If you don’t require support for non-IE devices, then replace the Yepnope function with a much lighter conditional comment.

<!--[if (lt IE 9) & (!IEMobile)]>
 <script src="css3-mediaqueries.js"></script>
 <![endif]-->

Pro Tip 2

If you are building for mobile first, then adding a min-device-width condition to the Yepnope query is definitely worthwhile. This will prevent the hefty 15 KB file from loading on small screens that will never use it. Win!

Use CSS3-MediaQueries-js If…

  • You are using advanced media queries, beyond simple pixel-width conditions;
  • You are happy to take that 15 KB loading hit;
  • Your audience doesn’t include a long tail of feature-phone users.

Example: Hicksdesign uses complex media queries beyond simple width and height.

In Conclusion

Responsive design is still a new way of thinking. Media Queries are a great tool to enhance the experience of browsing a web site on multiple devices and it’s a great idea to consider devices that do no support them. We would be dreaming if we expected an easy solution from day one but at least we have a range of options in front of us that allow us to find the best solution for the problem at hand.

It’s important to bear in mind that context is key, a well informed decision will always yield better results instead of quickly choosing the most popular solution.

(al)


© Lewis Nyman for Smashing Magazine, 2011.


Phoning It In: Beautiful iPhone Photography


  

Most designers and developers jumped on to the mobile bandwagon as soon as the market broke. So many new avenues were made available, and the field gained a new route of accessibility. Another area that the new smartphone pandemic has impacted is photography.

This is not suggesting that folks running around armed only with iPhones and enthusiasm are going to be dominating the professional photography market, far from it. But a new avenue of accessibility has certainly opened up for so many, and the inspirational wellsprings are overflowing as a result.

With so many fantastic apps on the market, with their one touch photo effects and filters, iPhones and their built in digital cameras have taken the photography world by storm. Producing some truly inspiring results, which we have gathered a collection of for you today. Take a look at the fun and creative life captured on an iPhone followed up by some links to a few apps to take your own pics with.

Gallery of Goods

My Wife by yto

Untitled by Marco Maaß

Instagram’d by Darren Shilson

Untitled by rick1j13

instagram catchup from the last few weeks by philcampbell

Starburst by Jamie Pachomski

instagram catchup from the last few weeks by philcampbell

Sunny-side up by Jamie Pachomski

Probando instagram… + flickr by Juan Pablo Olmo

the color wheel by Jamie Pachomski

Instagram by 246-You

Locomotive of the Arosa-Bahn by Jürg Vollmer

#instagram Shadowy Road by tommy_io

Alpine Architecture 01 by Jürg Vollmer

Instagram pic of Maui by matturick

Rose Garden in Schenkon/LU 01 > Grunge by Jürg Vollmer

Untitled by Krzysztof Urbanowicz

The Orb by simplyrikkles

test instagram by kimi-

First ride @Citytunneln by Eldin Beganovic

Testing Instagram by sthcrft

Jackie Lation by Greg Scott

Trying out Instagram’s tilt-shift filter in Detroit by George Hotelling

Photo by iquanyin moon

Untitled by Krzysztof Urbanowicz

Staring at the Sea by An en Alain

Even instagram uitproberen voor de bui losbarst by Bonny van Sighem

Untitled by keka marzagao

Yay primer instagram en B&W, miren qué bonito. by Nacho el Nacho

Untitled by iquanyin moon

Untitled by Krzysztof Urbanowicz

intergalactic volkswagen beetle by Sweet Cheeks Willie

Untitled by John Nolen

Industrial Art by bitjungle

Instagram by JessicaPenny

Weed by bitjungle

Tira Pinchon by Gary De La Fuente

Untitled by iquanyin moon

Spring by Donny Urrutia

Untitled by iquanyin moon

iPhone Camera Apps

(rb)


Designing For Android Tablets

Advertisement in Designing For Android Tablets
 in Designing For Android Tablets  in Designing For Android Tablets  in Designing For Android Tablets

More than ever, designers are being asked to create experiences for a variety of mobile devices. As tablet adoption increases and we move into the post-PC world, companies will compete for users’ attention with the quality of their experience. Designing successful apps for Android tablets requires not only a great concept that will encourage downloads, usage and retention, but also an experience that Android users will find intuitive and native to the environment.

Android-cover in Designing For Android Tablets

The following will help designers become familiar with Android tablet app design by understanding the differences between the iPad iOS user interface and Android 3.x “Honeycomb� UI conventions and elements. We will also look at Honeycomb design patterns and layout strategies, and then review some of the best Android tablet apps out there.

Note that while Android 2.x apps for smartphones can run on tablets, Android 3.0 Honeycomb was designed and launched specifically for tablets. Future updates promise to bring Honeycomb features to smartphone devices, as well as make it easier to design and build for multiple screen types.

For most of us, our first exposure to tablets was via the iPad. For this reason, it’s reasonable to begin comparing the two user interfaces. By comparing, we can align what we’ve learned about tablets and begin to focus on the key differences between the two, so that we can meet the unique UI needs of Android users. Not only will this help us get up to speed, but it becomes especially important when designing an Android tablet app from an existing iPad one.

It’s Just Like The iPad, Right?

While the Android tablet and iPad experience share many similarities (touch gestures, app launch icons, modals, etc.), designers should be aware of the many differences before making assumptions and drawing up screens.

Screen Size and Orientation

The biggest difference between the two platforms is the form factor. Layouts for the iPad are measured at 768 × 1024 physical pixels, and the iPad uses portrait mode as its default viewing orientation.

With Android tablets, it’s a bit more complicated, due to the multiple device makers. In general, there are 7- and 10-inch Android tablets screen sizes (measured diagonally from the top-left corner to the bottom-right), with sizes in between. However, most tablets are around 10 inches.

What does this mean in pixels? A good baseline for your layouts is 1280 × 752 pixels (excluding the system bar), based on a 10-inch screen size and using landscape (not portrait) as the default orientation. Like on the iPad, content on Android tablets can be viewed in both landscape or portrait view, but landscape mode is usually preferred.

Image 1 in Designing For Android Tablets
The portrait view on a typical 10-inch Android tablet (left) and on the iPad (right).

Image 2 in Designing For Android Tablets
The landscape view on a typical 10-inch Android tablet (left) and on the iPad (right).

However, with Android, screen size is only the half of it. Android tablets also come in different “screen densitiesâ€� — that is, the number of pixels within a given area of the screen. Without going into too much detail, designers have to prepare all production-ready bitmaps for three different screen densities, by scaling each bitmap to 1.5×and 2× its original size. So, a bitmap set to 100 × 100 pixels would also have copies at 150 × 150 and 200 × 200. By making three batches of graphics scaled at these sizes, you will be able to deliver your bitmaps to medium, high and extra-high density tablet screens without losing image quality.

For more information on screen densities and preparing graphics for Android devices, refer to my previous article on designing for Android.

System Bar

While iOS makes minimal use of the system bar, Android Honeycomb expands its size to include notifications and soft navigation buttons. There is a “Back� button, a home button and a “Recent apps� button.

Image 3 in Designing For Android Tablets
The Android Honeycomb system bar.

Android Honeycomb’s system bar and buttons are always present and appear at the bottom of the screen regardless of which app is open. Think of it like a permanent UI fixture. The only exception is a “Lights out� mode, which dims the system bar to show immersive content, such as video and games.

“Back� Button

While the bulkiness and permanence of the Honeycomb system bar might seem an obstacle to designers, it does free up the real estate that is typically taken by the “Back� button in iPad apps. The “Back� button in Honeycomb’s system bar works globally across all apps.

Image 4 in Designing For Android Tablets
The “Back� button in the system bar.

Action Bar

The bulk of the UI differences between platforms is found in the top action bar. Android suggests a specific arrangement of elements and a specific visual format for the action bar, including the placement of the icon or logo, the navigation (e.g. drop-down menu or tabs) and common actions. This is one of the most unifying design patterns across Android Honeycomb apps, and familiarizing yourself with it before attempting customizations or something iPad-like would be worthwhile. More on the pervasive action bar later.

Image 5 in Designing For Android Tablets
The action bar.

Widgets

New to iPad users will be Android’s widgets. As the name implies, these are small notification and shortcuts tools that users can set to appear on their launch screen. Widgets can be designed to show stack views, grid views and list views, and with Android 3.1, they are now resizable.

Image 6 in Designing For Android Tablets
Several widgets on a launch screen.

Notifications

While iOS’ notifications system pushes simple alerts to your launch screen, Honeycomb offers rich notifications that pop up (“toast� we used to call them) in the bottom-right area of the screen, much like Growl on Mac OS X. Custom layouts for notifications can be anything from icons to ticker text to actionable buttons.

Image 7 in Designing For Android Tablets
A notification on Android.

Settings

Access to settings in an iPad app are usually presented in a pop-over, triggered by an “i� button; and settings categories are broken up into tables for easy visual identification. Honeycomb has a different convention. It looks more like the iOS’ “General Settings� screen, where the user navigates categories on the left and views details on the right. This is the preferred (and more elegant) way to present multiple settings in Honeycomb.

Image 8 in Designing For Android Tablets
The settings design pattern in the Calendar app.

UI Elements

As you can imagine, Android goes to great lengths to do everything opposite from its competitor (that’s called differentiation!). Honeycomb has its own UI conventions, and it now has a new “holographic UI� visual language for such routine actions as picking a time and date, selecting an option, setting the volume, etc. Understanding this UI language is important to building screen flows and creating layouts.

Image 9 in Designing For Android Tablets
A sampling of UI elements, taken from a slide in a Google I/O 2011 presentation.

Fonts

How many fonts does iPad 4.3 make available? The answer is fifty-seven.

How many does Android? Just three.

Yep, those three are Droid Sans, Droid Serif and Droid Sans Mono. But there is an upside. While only these three ship with the platform, developers are free to bundle any other fonts with their apps.

Image 10 in Designing For Android Tablets

Anything the Same?

Luckily for designers who are already familiar with the iPad, the two platforms have some similarities.

Touch Gestures

Tap, double-tap, flick, drag, pinch, rotate and scroll at will.

Split View and Multi-Pane UI

The split view is one of the most common layouts for tablets. It consists of two side-by-side panes. Of course, you can add panes for more complex layouts.

Image 111 in Designing For Android Tablets
Ustream’s split-view layout, with categories on the left and content on the right.

Embedded Multimedia

Both platforms allow embedded audio, video and maps.

Image 121 in Designing For Android Tablets
The YouTube app, with an embedded video player.

Clipboard

For copying and pasting data into and out of applications.

Image 13 in Designing For Android Tablets

Drag and Drop

Both platforms have drag-and-drop capabilities.

Image 14 in Designing For Android Tablets
The drag-and-drop feature in the Gmail app.

Design Patterns

Honeycomb continues many of the design patterns introduced in Android 2.0 and expands on them. In case you’re not familiar with design patterns, they are, as defined in Android, a “general solution to a recurring problem.� Design patterns are key UI conventions designed by Android’s maintainers to help unify the user experience and to give designers and developers a template to work from. They are also customizable, so no need to fret!

As mentioned, the action bar is the most prominent Android UI component and is the one we’ll focus on here.

Image 151 in Designing For Android Tablets
The action bar highlighted in the Calendar app.

Icon or Logo

The action bar starts with an icon or logo on the far left. It is actionable; by tapping on it, the user is directed to the app’s home screen.

Image 16 in Designing For Android Tablets
The Calendar app icon.

Navigation

Next, we’ll typically find some form of navigation, in the form of a drop-down or tab menu. Honeycomb uses a triangle graphic to indicate a drop-down menu and a series of underlines for tabs, which typically take up most of the action bar’s real estate.

A left arrow button might also appear to the left of the icon or logo or the label, for navigating back or cancelling a primary action.

Image 171 in Designing For Android Tablets
Three different kinds of action bar navigation.

Common Actions

Common actions, as the name implies, gives user such things as search, share and an overflow menu. They are always positioned to the right of the action bar, away from any tabs.

Image 181 in Designing For Android Tablets
Common actions in the Calendar app.

Overflow Menu

The overflow menu is part of the common actions group and is sometimes separated by a vertical rule. It is a place for miscellaneous menu items, such settings, help and feedback.

Image 191 in Designing For Android Tablets
An overflow menu.

Search

Search is also a part of the common actions group. Unique to search is its expand and collapse action. Tap on the search icon and a search box expands out, letting you enter a query. Tap the “x� to cancel, and it collapses to its single-button state. This is a space saver when many actions or tabs need to be shown.

Image 20 in Designing For Android Tablets
The search function collapsed (top) and expanded (bottom). Tapping the magnifying glass opens the search box, while tapping the “x� closes it.

Contextual Actions

Contextual actions change the format of the action bar when an item is selected, revealing options unique to that item. For example, if a photo app is displaying thumbnails, the action bar might change once an image is selected, providing contextual actions for editing that particular image.

To exit the contextual action bar, users can tap either “Cancel� or “Done� at the far right of the bar.

Image 21 in Designing For Android Tablets
The contextual action bar is triggered when tapping and holding an email in the Gmail app.

Tablet Layout Strategies

Using Fragments and Multi-Pane Views

The building blocks of Honeycomb design are “Fragments.� A Fragment is a self-contained layout component that can change size or layout position depending on the screen’s orientation and size. This further addresses the problem of designing for multiple form factors by giving designers and developers a way to make their screen layout components elastic and stackable, depending on the screen restraints of the device that is running the app. Screen components can be stretched, stacked, expanded or collapsed and shown or hidden.

Image 22 in Designing For Android Tablets
The Fragments framework gives designers and developers several options for maintaining their layouts across screen sizes and orientation modes.

What makes Fragments so special? With a compatibility library, developers can bring this functionality to Android smartphones going back to version 1.6, allowing them to build apps using a one-size-fits-all strategy. In short, it enables designers and developers to build one app for everything.

While Fragments may be a term used more by developers, designers should still have a basic understanding of how capsules of content can be stretched, stacked, expanded and hidden at will.

The most common arrangement of Fragments is the split view. This layout is common in news apps and email clients, where a list is presented in a narrow column and a detailed view in a wider one.

Image 23 in Designing For Android Tablets
The split view used by USA Today

Another way to present a split view is to turn it on its side. In this case, the sideways list Fragment becomes a carousel, navigating horizontally instead of vertically.

Orientation Strategies

While Fragments are great for applying one design to multiple screen sizes, they are also useful for setting orientation strategies. Your screen design might look great in landscape view, but what will you do with three columns in a narrow portrait view? Again, you have the option to stretch, stack or hide content. Think of Fragments like a bunch of stretchy puzzle pieces that you can move around, shape and eliminate as needed.

A Word About Animation

The Honeycomb framework allows designers and developers to use a variety of animation effects. According to the Android 3.0 Highlights page, “Animations can create fades or movement between states, loop an animated image or an existing animation, change colors, and much more.� Honeycomb also boasts high-performance mechanisms for presenting 2-D and 3-D graphics. For a good overview of what Honeycomb is capable of, check out this video.

Learning from Example

Android tablet apps are still a relatively new space, and some brands are only beginning to test the waters. Below is a list of apps for inspiration. You can download any of them from the Android Market or Amazon.

YouTube
Naturally, Google’s YouTube app for Honeycomb is exemplary, showcasing all of the design patterns and UI elements discussed above. To get a good feel for Honeycomb, download this app first and take it for a spin.

Image 24 in Designing For Android Tablets

CNN
The CNN app makes good use of touch gestures (including flicking to view more content), the split view and fonts! A custom font (Rockwell) is used for news headlines.

Image 26 in Designing For Android Tablets

CNBC
Another good news app, with animation (the stock ticker tape) and rich graphics and gradients. CNBC has one of the most visually compelling apps.

Image 27 in Designing For Android Tablets

Plume
With its three-column layout, Plume is a good example of how layouts might need to be changed dramatically from landscape to portrait views.

Image 28 in Designing For Android Tablets

FlightTrack
A data-heavy app done elegantly. Includes nice maps, subtle animation and standard Honeycomb UI elements.

Image 29 in Designing For Android Tablets

Pulse
What else can you say: it’s Pulse for Android tablets! But comparing the Android and iPad versions, which are identical in almost every way, is still fun anyway.

Image 30 in Designing For Android Tablets

WeatherBug
This was one of the first Honeycomb apps in the Android Market. It makes good use of maps and of the holographic UI for showing pictures from weather cams.

Image 31 in Designing For Android Tablets

Kindle
Kindle pretty much sticks to the book in using design patterns and Honeycomb UI elements. The outcome is elegant, while staying true to Android’s best practices.

Image 32 in Designing For Android Tablets

Honorable Mentions

  • IMDb
  • News360
  • USA Today
  • AccuWeather
  • Ustream
  • Google Earth
  • Think Space

Online Resources

Video

Presentations

Blogs

Android Developers

(al)


© Dan McKenzie for Smashing Magazine, 2011.


Extending the Functionality of WordPress Pt.2


  

Previously, on Noupe. We brought you a handful of ways to expand on the functionality of any WordPress based site using some inspired plugins and/or themes to elevate this CMS beyond its humble beginnings as a blogging platform. With ways to turn WP into a Discussion Forum, an Online Shop, and a Helpdesk. Today, that mission continues.

Excerpt from Part One

Theme designers and plugin developers have been pushing the boundaries of what WordPress can do for some time. This has accelerated since the introduction of Custom Post Types into the WordPress core as it allows developers to use WordPress in a lot of weird and wonderful ways.

Today we will begin showing you examples of themes and plugins that let you use WordPress in ways you may have never thought possible.

As we mentioned last week, in this installment we will show you how to extend the possibilities of your WP site to make it a Wiki, an Arcade, a Job Board, a Membership based site, a Review site, or just a Q&A site. Now let’s get at it.

Wiki

Due to the sheer amount of content they contain, Wikis are a good way of making money online (take Star Trek fan wiki Memory Alpha for example). They are also a useful addition to blogs and websites as it allows readers to contribute to the site. As you would expect from a CMS, WordPress handles Wikis easily.

Theme

WikiWP – FREE

In A Nutshell: A free WordPress theme that’s based on the Wikipedia design.

WikiWP

Pros

  • SEO friendly.
  • Clean design (though perhaps a little dated).

Cons

  • Hasn’t been updated for years so new WordPress features aren’t built into this theme.

WordPress Wiki Theme – $30

In A Nutshell: A premium WordPress design that uses WordPress to create a wiki.

WordPress Wiki Theme

Pros

  • 6 colour schemes to choose from.
  • Features sliding sidebar menus and a dedicated FAQ page.

Cons

  • Hasn’t been updated with WordPress 3.0 features such as featured images.

Plugins

Wiki – $39

In A Nutshell: A premium WordPress plugin that lets you convert any post or page into a Wiki.

Wiki

Pros

  • Entries can be edited directly on the page without having to access your admin area.
  • Works with WordPress, WordPress MU and BuddyPress.
  • Perfect for adding a Wiki to an existing website.

You May Also Want To Consider…

  • eSimple Wiki – A basic free Wiki plugin for WordPress.
  • Wiki Embed – Lets you embed wikis onto any WordPress page or post.
  • WikiPress – An open source plugin that lets you collaborate with other users in your admin section via a Wiki.

Arcade

There are quite a few premium products that allow you to build an arcade website using WordPress. Most plugins come packaged with a theme and charge a little extra for the games to be included in the zip file.

MyArcadePlugin Lite – FREE | My Arcade Plugin – €29.95

In A Nutshell: A feature rich arcade WordPress plugin that lets you install a whopping 29,000 games.

MyArcadePlugin

Pros

  • Games can be downloaded and posted automatically.
  • Great looking design and can be customised with your own brand in minutes.
  • Leaderboard support to encourage visitors to come back.

Cons

  • Free version of the plugin is very limited.

WP Arcade – $33

In A Nutshell: A premium arcade theme store that comes packaged with a plugin that automatically grabs games from MochinMedia.

WPArcade

Pros

  • All themes come with 5 colour schemes.
  • Advertising and Google Analytics integration.
  • Huge amount of customisation through the themes unique options page.
  • Good price for an arcade solution.

Cons

  • There are currently 10 themes available however they are all very similar.

WP Arcade Engine – $29

In A Nutshell: A premium arcade plugin for WordPress.

WPArcadeEngine

Pros

  • The plugin can be set to publish new games every day automatically.
  • Support for any type of game type.
  • Includes a 30 day no questions asked money back guarantee.

Cons

  • The plugin retails for $29 however you don’t get any games for this price. You will need to pay an additional $29 to get a game pack.

You May Also Want To Consider…

  • WP Mini Games – Allows you to easily embed flash games onto posts, pages and sidebars.
  • ArcadePress – An fulley fledged open source arcade solution.
  • WP Games Embed – Lets you embed flash games into your posts and pages using shortcodes.

Job Board

There are a lot of job related plugins available for WordPress though 3 stand out from the rest: the Job Board and Jobroller designs and the very useful Job Manager. I recommend Job Manager for those of you who want to add a job section into an existing WordPress website.

Themes

Job Board – $65

In A Nutshell: A premium theme that uses WordPress to power a job board.

Job Board

Pros

  • Complete control using a dedicated theme options page.
  • Coupons feature to allow certain customers discounts.
  • Automated payment collection via PayPal.
  • Very easy to brand.

Jobroller – $99

In A Nutshell: Turn your WordPress website into a fully functional job board.

Jobroller

Pros

  • Easy to use theme options area.
  • Options for job seekers and employers. Job seekers can also upload their resume/CV for employers to see.
  • Five different colour schemes.
  • Social media integration.

Plugins

Job Manager – FREE

In A Nutshell: An open source job plugin that doesn’t scrimp on features

Job Manager

Pros

  • Can create multiple job boards.
  • Applicants can apply directly through the website.
  • Good template system that allows you to customise the job area into your existing WordPress design.

Cons

  • If you are looking for a dedicated job website, it may be better to use an all in one job solution such as the premium themes mentioned as you would need to use this plugin with an existing design.

WPCareers – FREE

In A Nutshell: A free plugin that lets you create a searchable resume (CV) database.

WPCareers

Pros

  • Users can modify descriptions at a later date and upload their own photos/images.
  • Can manage job seekers and employers.

Cons

  • Limited features when compared to other options.

You May Also Want To Consider…

Membership

WordPress is the perfect platform for a membership website. The premium member plugins are better supported however free alternatives have a huge range of features too.

Members Only – FREE

In A Nutshell: Make your content viewable only by signed in members.

Members Only

Pros

  • Can specify what page the member is redirected to when they log in.
  • Can protect RSS feeds for members too.

User Role Subscriptions – FREE

In A Nutshell: A user role subscription plugin that allows you to restrict content to paid subscribers.

User Role Subscriptions

Pros

  • Can modify the email template for new subscribers.
  • Automatically deletes expired subscribers.
  • Can accept payments via PayPal.

Cons

  • Quite limited. There are better alternatives available.

WP-Members – FREE

In A Nutshell: A membership system that restricts content to signed in users.

WP Members

Pros

  • Can block pages, posts, both or neither by default.
  • Registration process can be changed to suit your needs.
  • Private member area can be determined.
  • Well documented.

Cons

  • No support for paid membership.

Members – FREE

In A Nutshell: A user role and content management plugin.

Members

Pros

  • Capabilities of users can be modified.
  • You can control what user groups can see specific content.
  • RSS feeds can be restricted.

s2Member – FREE | s2Member Pro – $69

In A Nutshell: An feature rich membership plugin.

s2Member

Pros

  • Includes 4 membership levels: Free, Bronze, Silver, Gold, and Platinum.
  • Works with multiple payment gateways.
  • Can setup one off or recurring payments.
  • Can restrict content and downloads to specified member levels.

Membership – FREE | Membership Premium – $39

In A Nutshell: Transforms WordPress into a fully functional membership site.

Membership

Pros

  • Can offer free memberships that turn into paid memberships after a set number of days.
  • Unlimited membership and subscription levels.
  • Can restrict access to members only in lots of different areas including posts, pages, comments, categories, galleries and more.
  • Well documented, well supported and updated regularly.

WP-Membership – $25

In A Nutshell: Sell your content with this premium membership plugin.

WP Membership

Pros

  • Can setup unlimited membership levels.
  • Payments can be made via PayPal and the dashboard shows sales for that month.

Cons

  • Limited number of member options compared to other paid membership plugins.

CMS Members – $59.50

In A Nutshell: A solid membership plugin that boasts some great features.

CMS Members

Pros

  • Create unlimited memberships.
  • Built in mass mailer.
  • Accepts PayPal and 2Checkout as payment from new members.
  • Content within a post or page can be restricted to different member groups.

MagicMembers – $97

In A Nutshell: A premium membership plugin that has a huge amount of features.

Magic Members

Pros

  • Works with a huge number of payment gateways.
  • Integrates with popular auto responders.
  • Premium content can be restricted on a ‘Pay Per Post’ basis.
  • Categories can be protected and RSS feeds can be restricted to paying members too.

Wishlist Member – $97

In A Nutshell: One of the most popular premium membership plugins available today.

Wishlist Member

Pros

  • Sequential content delivery for those who want to drip-feed content to members.
  • Flexible membership options including free, trial or paid. Members can also migrate to other membership levels after a set period of time.
  • Works with many shopping cart systems.
  • Integrates with many popular WordPress plugins.

You May Also Want To Consider…

Review Website

The surge to make money through review websites has died down a little however there are still some good premium plugins out there for those of you who are looking to launch a review website.

My Review Plugin – $90

In A Nutshell: A flexible rating plugin that can add ratings to any WordPress post, page or product.

MyReviewPlugin

Pros

  • Can use stars, letters or percentages to grade items.
  • It’s easy to build horizontal and vertical comparison tables.
  • Add ratings to any area of your site automatically with a one-click install.
  • 45-day money back guarantee.

WF Review – $89

In A Nutshell: A review plugin that was created specifically for affiliate marketers.

WF Review

Pros

  • Import CSV feeds from affiliate networks such as Commission Junction and ShareASale to create thousands of products in seconds.
  • Support for comparison tables.
  • Amazon ratings stars are fully customisable via CSS.

WP Review Engine – $99.95

In A Nutshell: A premium rating plugin that can be customised easily.

WP Review Engine

Pros

  • Rating comments and rating tables can be styled easily via the admin area.
  • 13 star images, 23 buttons, and 6 comparison table image sets are included with the plugin.
  • Add comparison tables to any post or page on your site.
  • 30-day money back guarantee.

Q & A

The following themes and plugins allow you to create a question and answer website. This type of website has become very common due to the popularity of sites such as Yahoo Answers, Stack Overflow and Quora.

Themes

WP Answers – $89

In A Nutshell: Turn WordPress into a cash generating question and answer website.

WP Answers

Pros

  • Pull content directly into your website from Yahoo Answers.
  • Full Facebook and Twitter integration.
  • Packaged theme comes in 6 custom colours.
  • Intuitive points system that gives members points for answering questions.

Plugins

Q&A Lite – FREE | Q & A – $39

In A Nutshell: Add a questions and answers section to your existing WordPress website.

Q and A

Pros

  • WYSIWYG editors for both questions and answers.
  • Integrated reputation points system.
  • User profile pages for those who use the question and answer service.

You May Also Want To Consider…

Overview

Throughout the course of these two articles we have shown you how flexible the WordPress is and how it can be used for a variety of purposes. The products that have been listed in this article can be split into two categories: plugins that integrate with your existing WordPress powered website to add extra functionality to an area of your site and themes or plugins that use WordPress to completely change how WordPress is used (e.g. a discussion forum).

When you are using a product that uses WordPress to power the main areas of your website, you need to consider the stand alone scripts that are available. For example, The G Forums uses the WordPress platform to create a discussion forum. It achieves this through custom theme templates therefore it couldn’t be integrated into an existing WordPress website. The script retails for $29 and has very basic features therefore, in my opinion, you would be better off using a PHP bulletin board such as phpBB or Simple Machines instead. If however you wanted to integrate a forum into your existing website, a plugin such as bbPress may be better than phpBB or Simple Machines.

Another factor to consider is plugins. The official WordPress plugin directory has over 15,000 plugins. The number of add ons available for stand alone scripts is sometimes poor therefore if you need additional functionality on your website, a WordPress product is a good choice (e.g. one click installs of forums, sitemaps, member areas etc).

Also, if you know of any great free or premium WordPress products that extend the functionality of the platform, please share it with other readers in the comment area.

(rb)


  •   
  • Copyright © 1996-2010 BlogmyQuery - BMQ. All rights reserved.
    iDream theme by Templates Next | Powered by WordPress