November 14, 2012 — By WPTouch Admin

Responsive Themes vs. Server Side Optimization: WordPress Mobile Solutions Compared

Martin Kuplens-Ewart at WordCamp Toronto

Last month I had the opportunity to present at WordCamp Toronto Developers. I spoke about principles and guidelines to building successful mobile websites and spent a fair bit of time looking at the three main approaches to building mobile websites:

  • using a single pure responsive theme, which adjusts page flow and hides/shows content based on the device’s width;
  • building a separate website for mobile devices;
  • server-side optimizations, which is the approach WPtouch enables.

Pros and Cons of Responsive Design

A pure responsive approach to building a website can be a very tempting proposition. After all, it promises to address both your desktop and mobile website needs in one go. Some design firms will even argue that this approach saves you money, especially if your website will involve merely customizing a pre-existing responsive theme. Images are even automatically scaled by the browser to fit the screen. And if the content isn’t helpful to mobile visitors? You can just hide it!

But being able to adapt to changing user expectations and behaviours is critical to being successful in the mobile web. Here, responsive themes’ strongest advantage proves to be their Achilles’ heel. Because your mobile display is inextricably linked to your desktop display, adjusting your sites display for the way people use it with different devices is unavoidably more difficult and expensive than if you use a separate set of templates for mobile and desktop visitors, particularly smartphone visitors.

For example, because desktop visitors are rarely looking to visit your physical location, most website templates will list your address in the footer or on a contact page. But what if, like many business owners, you learn that the first piece of information your mobile visitors actually want is your location? Now you need to retrofit your site templates to add a map or your address at the top of your homepage, too.

Because you’re using a pure responsive template, you can’t just add the content, check it on your phone, and be happy with it. You now need to add additional styles and possibly code to hide the map and address on large screens and then re-test your site in all display sizes to make sure your change hasn’t caused problems. And, over time, your pages become peppered with sometimes-hidden content and elements.

Remember those images you used because they look great on your 20-inch monitor? Mobile browsers can only scale them after the full image is downloaded. The pictures and content you hid? Mobile visitors are forced to download those, too. In fact, many websites using a purely responsive technique will send upwards of a megabyte of media and HTML that can’t or won’t be shown on mobile devices. One American presidential candidate’s homepage was a full seven megabytes though all you saw were thumbnails and small photos!

With many people, particularly in North America, having between 100 and 500 MB monthly data plans, any website that sends oversized and unused images and content that is then hidden from view is placing an unfair (and unnecessary) burden on its mobile visitors.

Server Side Optimization

In these situations, solutions involving server-side optimizations (or as Google refers to it, dynamic serving) prove their worth. By detecting that a mobile device is accessing your site before sending anything to the device, templates specifically designed and optimized for devices are used to display your website’s content.

Rather than sending those large images sized to look great on a large monitor, they are re-sized on the server to fit the mobile device, dramatically cutting file sizes. And because only the information that is being displayed is sent, no content needs to be hidden, and no waste data is sent.

The separation of your desktop and mobile templates also means that you can freely make major changes to adapt to mobile visitors’ needs and also experiment with your desktop site, installing plugins, advertising, and rich media, without an impact on your efficient mobile interface.

And what if you already have a website and just want to add mobile support? Solutions such as WPtouch that enable server-side optimization allow you to do that without rebuilding your desktop site. A pure responsive approach means tearing up your templates and starting from scratch.

Still tempted?

November 8, 2012 — By WPTouch Admin

WPtouch Pro Tips Central: debono.com.au

On A Clear Day logo

Our “Tips Central” blog series spotlights WPtouch Pro-powered sites built and maintained by designers, developers and site owners like you. Read about other designers, developers, and site owners’ experiences with WPtouch Pro and get ideas for your own projects. Our experts also provide their recommendations for additional site enhancements using WPtouch Pro.

Site URL: www.debono.com.au
Site Owner: Joe Debono
License Type: Single
Joe Debono on Twitter: @joedebono

tips-central-debono-ipad-mobile-themes

How long have you been using WPtouch Pro?
I’ve been using WPtouch Pro for just a little over a year, since October 2011.

Why did you choose WPtouch Pro to power your mobile site?
I chose WPtouch Pro because these days, a mobile-friendly site is absolutely essential. Catering exclusively to mobile users has its restrictions so creating a full site for desktops as well covers all bases. I considered running two completely independent sites but this meant double the work. With a little research, I quickly found WPtouch Pro. It had all the features I wanted and ridiculously easy installation and configuration processes as well. I was up and running in well under an hour.

What do you like most about using WPtouch Pro?
What I like best about WPtouch Pro is that I can go about updating the desktop version of the site as I always have knowing that WPtouch Pro is doing its thing quietly in the background for my mobile visitors.

What improvements would you like to see included in future WPtouch Pro updates?
WPtouch Pro has come a long way in the short time I’ve been on board. Any issues I’ve had have been resolved quickly. I would like an easier way to modify some of the elements. For example, the “read more” chevron is a little pale and many visitors don’t see it (They click on the thumbnail in list view and wonder why nothing happens). I replaced it with a more prominent version but this mod gets lost after an update of course.

SUPPORT NOTE: We recommend that styling customizations be made by adding custom CSS to a WPtouch Pro child theme. These additions will survive future updates to the plugin’s core code.
Support Documentation: Applying Custom CSS

OUR TIPS CENTRAL SUGGESTIONS FOR debono.com.au

Note: Links to support documentation are available exclusively to current WPtouch Pro customers who are logged into bravenewcode.com.

1. Add a title to the home screen icon.
This is a small improvement that many, many users will see so why not add the site’s name to iOS Web-App Mode to make that home screen icon even more custom? The option to customize the home screen icon title is under Active Theme > iOS Web-App Mode > General Options.
Support Documentation: iOS Web-App Mode

tips-central-debono-custom-web-app-title

Custom Web-App Mode Title

2. Add startup screens to iOS Web-App Mode.
To complement other iOS Web-App Mode customizations, startup screens can be added. Options are offered to add startup screens for the full variety of iOS device screen sizes. Startup screens are a great way to add another visual component to your mobile site experience.
Support Documentation: iOS Web-App Mode

tips-central-debono-loading-screen-options

Web-App loading screen options

3. Fix broken mobile menu by resolving plugin conflicts.
Currently the WPtouch Pro menu is broken on debono.com.au. This is likely the result of a plugin conflict where conflicting scripts are causing all the WPtouch Pro menu tabs to be displayed inline simultaneously (we’re seeing a .js error attributed to “Dave’s WordPress Live Search Plugin”). Conflicting plugins can be disabled through WPtouch Pro’s Compatibility options or manually. BraveNewCode provides support and documentation to guide customers in removing plugin hooks manually.
Support Documentation: Removing Conflicting Plugin Hooks

tips-central-debono-plugin-compatibility-options

Plugin Compatibility Options

4. Add the desktop site’s background image to the mobile theme.
The desktop theme uses a cloud image as a site background. To add that background to the mobile theme, include the image’s url under Active Theme > Style/Appearance > Background.

tips-central-debono-custom-background-image-support

Custom background image support

Bonus Tip: Add the desktop theme’s home page custom background slideshow.
Though not possible with every desktop theme, WPtouch Pro customers have customized their WPtouch Pro mobile theme to include full-screen background slideshows. This is an advanced customization requiring the addition of the non-mobile theme’s slideshow functions and styling to the WPtouch Pro child theme. Support for this level of customization is reserved for Developer License holders.


Are you interested in having your WPtouch Pro-powered site featured in our “Tips Central” series? Please drop us a note through our contact form to inquire.

November 5, 2012 — By WPTouch Admin

Responsive Design vs. Server-Side Mobile Solutions with BraveNewCode and Mobile Joomla [Dev1.tv Podcast]

Responsive Vs. ServerSide Mobile Solutions

Recently our Co-Founder Dale Mugford along with Ugur Kaner and Miikka Kukkusuo from Mobile Joomla were interviewed for a podcast on Dev1.tv.

The podcast focuses on comparing responsive design with server-side mobile solutions, sometimes referred to as “dynamic serving” – like Mobile Joomla and our WPtouch plugin. A summary of points discussed during the podcast can be found below.

The differences between responsive design techniques and server-side approaches can be broken down into four categories:

Technical
A significant benefit of server-side solutions is fast and efficient delivery of content. This is a key consideration for mobile users who studies show are only willing wait 4 seconds for content to display on smartphones. Server-side solutions are designed to deliver mobile pages that are up to 500% smaller than the size of their desktop counterparts and load up to 400x faster. In comparison, heavy webpages slowed by responsive techniques can exceed mobile device cache limits, resulting in an increased risk of crashing your browser. Server-side solutions can also swap out larger images and videos for smaller ones and prevent extraneous scripts and assets from being sent entirely— characteristics which are not technically possible in responsive approaches at this time.

Design
Server side solutions leave less room for content formatting requirements to be overlooked. This ensures a polished, dependable design is displayed to site visitors. However, server-side solutions can require additional work to maintain branding across devices. Responsive design’s single set of styles ensures consistent design is applied in all cases, perhaps its strongest benefit.

Content
With responsive design, content which is inappropriate for mobile visitors is only ‘hidden’ through stylesheet formatting. With server-side solutions, site owners can specify content that will not be sent to mobile visitors, further streamlining and optimizing the mobile display of content.

Maintenance
Best practices for responsive design are still being determined. Finding a designer with a strong enough grasp of both mobile technologies and mobile design skills to be able to deliver a dependable responsive design may not be easy and is often expensive. Similarly, maintaining a responsive design on an ongoing basis may mean reliance on expert design support. In contrast, many server-side solutions are set up to be user friendly for the site owner. Ongoing updates and changes can be applied through an easy-to-use interface.

You can listen to the full Dev1.tv “Responsive Design vs. Alternate Mobile Solutions” podcast here.

Further reading:

About BraveNewCode and Mobile Joomla

Mobile experts on the BraveNewCode and Mobile Joomla teams have each been developing mobile solutions for over 5 years. BraveNewCode co-founders, Dale Mugford and Duane Storey, are developers of WPtouch, the most popular mobile solution for WordPress sites. First released in 2008, WPtouch has been downloaded over 3,700,000 times from the WordPress directory and is used by over 30% of the top blogs using WordPress. Ugur Kaner is the founder and developer of Mobile Joomla and Miikka Kukkusuo is head of business development for Mobile Joomla. Mobile Joomla is most popular mobile solution for Joomla websites. Mobile Joomla currently delivers over 15,000,000 mobile Joomla pages. The two teams combined serve a sizeable share of sites using open source CMS mobile solutions and stand behind server-side detection as a best practice for mobile content delivery.

November 2, 2012 — By WPTouch Admin

WordPress Must Reads, October 27-November 2

Our weekly roundup of must read WordPress articles includes top news stories and popular, recently-published tutorials. Catch up on announcements and resources you might have missed over the past week.

http://storify.com/bravenewcode/wordpress-must-reads-october-27-november-2

October 26, 2012 — By WPTouch Admin

Must Read WordPress Articles, October 20-26

Our weekly roundup of must read WordPress articles includes top news stories and popular, recently-published tutorials. Catch up on announcements and resources you might have missed over the past week.

http://storify.com/bravenewcode/must-read-wordpress-articles-october-20-26

October 23, 2012 — By WPTouch Admin

Our Favourite WordPress Plugins: Duane Storey, BraveNewCode Co-founder

One half of BraveNewCode’s founding partnership, Duane Storey has been developing software applications/web-based architectures since he was in the womb. He has built novel web applications, Facebook applications, and even contributed to the voice engine that was once in Yahoo! Messenger.

This week we asked Duane to share some of his thoughts on WordPress and his favourite plugins.

Why do you work with WordPress?

I’ve always really enjoyed the process of writing, and of course having people read and sometimes comment on pieces I’ve written. As a result years ago I started exploring website options and eventually decided that WordPress was the best platform for me to use. Once I started using WordPress I realized that the flexible plugin architecture made it really easy to add functionality to my site, so I started writing code to present my photos in a better way. Eventually this lead me towards the creation of WPtouch, and ultimately BraveNewCode, with Dale.

Top Three Plugins

Flickr RSS by eightface and stefano.verna
This plugin is really basic, but I’ve pretty much used it on every site I’ve worked on where having Flickr photos was important. It does what it says it does, and it’s not confusing. I like simplicity.

Gravity Forms by rocketgenius
Having a contact form on a website is pretty standard these days, and whenever I think about adding one to a site, I almost always go with Gravity Forms. It’s really the best form creation/management plugin on the market. It is a commercial plugin, but I am always happy to hand over some money since it saves me a ton of time and effort when putting a site together with it.

WooCommerce by WooThemes
At BraveNewCode we’ve pretty much tried every eCommerce engine available for WordPress over the years. Without a doubt, WooCommerce is the most reliable and well-written one we’ve encountered, and it definitely simplifies things for us around here. It’s definitely my go-to plugin for doing commerce on WordPress now.

‹ newer posts | older posts ›

Previous Blog Entries

Added To Cart

Item added to cart successfully. You can either continue browsing and add more themes or extensions, or checkout now.

View Cart Checkout