Headspace Design

The year behind and the year ahead

Posted On January 9th, 2012 Author Kyle Racki Filed Under Headspace News, Comments 0

Just a quick post to let everyone know I'm still alive. We had a busy December, more of which I can talk about soon. So far January is off to a great start.

Last year had it's highlights and challenges. We got to the beta stage of our proposal software, Pitch Perfect. I demo'd the app at Democamp Halifax and was completely blown away by the response, and by the event. The contacts I made there, and subsequently at Mentor Camp, were amazing. Even though the product isn't yet ready to be commercialized (although we've got big plans this quarter), the challenge to get it built in the first place were well worth the effort.

We are ready to soon launch our social media monitoring software, Social Gopher, which has been a long time coming. This month we launch version 1.0 and will be excited to hear users feedback on it. The aim of Social Gopher is to make monitoring easy for small to medium size businesses, and offer relevant search data.

This past fall, Amy Wheaton, our project manager extraordinaire had a bit of an early leave to have Baby Eli. She's busy managing different schedules now, namely feeding and sleep schedules, so we've been doing our best to balance the influx of work and make sure everything runs smoothly. So far we're managing well, but we expect some growth this year, so stay tuned for job postings on this very blog.

I just wanted to write a short thank you to all of our loyal clients, new clients, freelancers, staff and friends for the great year in 2011 and we look forward to working with all of you in 2012.

How to lose a sale

Posted On November 3rd, 2011 Author Kyle Racki Filed Under Business, Marketing, Comments 0

I was looking at a website today and noticed a link to an online application for payroll. Great, I thought. An alternative to ADP. I reviewed their site and found the sign up form to learn about a special offer.

I took the time to fill out the form, which included fields asking how many employees I have, and what I currently use for payroll, and within 30 seconds I received a call from the sales agent. Everything okay so far. But he made several mistakes that lost him the sale in the end:

Uncomfortable Silence

The sales agent seemed like he wanted me to start the conversation when he was the one who called me. After some ums, ahs, and stutters, he asked me what I wanted. He should have already known what I wanted since I filled out a form to learn about a special offer!

Making me repeat myself

The rep then asked how many employees I had and what I currently use for payroll. It wasn’t hard for me to repeat what I already typed in the form, but the point is that I already told them and he should have had that info in front of him already. It just made me start to lose confidence.

He then asked how I found the site and I told him it was through an affiliate site - which he already should have known since the URL and banner on the site showed the online affiliate!

Put me on hold

Finally, he asked me to hold and I waited on the line for about 1 minute hearing shuffling and muffled talking, before hearing music kick in. At that point I hung up. He called about a minute later but by that point I was busy and didn’t care any more.

You would think that these days any company would think of this stuff as common sense what-not-to-do, but amazingly this company is probably wondering why they are having trouble closing deals when the answer is right in front of them - an inefficient sales process and inexperienced sales agents.

I’m sure there are lessons here we all can learn from when it comes to selling for our own companies.

 

Responsive Design vs Mobile App - Your website on a mobile device

Posted On September 18th, 2011 Author Kyle Racki Filed Under Design, Business, Development, Comments 1

Just recently, a big change came along in web design; Arguably the biggest revolution since modern web standards in the early 2000's.

Responsive Design has been invented. It's a term used in new age architecture to describe buildings that behave 'responsively'. That is, they adapt or respond to conditions such as the amount of people in a given room, for instance. They will automatically change heat, air and even room size (yes, the walls expand and contract!) to accommodate more or less people.

And just like Responsive Design in architecture, when it comes to the web, responsive design allows websites to no longer behave like static online brochures that scroll, but rather they adapt by expanding and contracting, resizing themselves to appropriately fit a variety of screen sizes. So for example, a website might have five columns when viewed on a 52" wide screen, but when viewed on a laptop it may scale down to three columns, two on an iPad and down to one column when viewed on a smart phone.

The best way to illustrate this is by viewing this gallery of well-designed responsive sites. You'll see four views for each site, from wide screen down to a small screen. Pretty impressive, huh?

The best part is, designing sites to be responsive does not add a lot of size, scope or complexity to a project. Sure, it adds some work for the designer and developer. But really in the grand scheme of building a website from start to finish, building it responsively is not all that time consuming once you know how.

Now, like all things in life, there's a catch. Building a website with responsive design is not a replacement for a mobile app or site. There are subtle but key differences.

Depending on your business, you may find that you actually need a mobile web application instead of just a website that scales to a variety of devices and screen sizes. The reasons are:

  1. Functionality
  2. Weight
  3. Business Model

 

1) Functionality

The trick with responsive is that it's all in the layout. When a user is on a smart phone, they are looking at the exact same site as on a desktop computer, but the CSS or style sheet is scaling the site visually to look better on a mobile device. It's kind of like window dressing. The HTML page is exactly the same.

Now you may find that on a mobile device, you want to do more than simply make the website look different. You actually want to take advantage of a mobile device' hardware. You may want to let the user shake their phone to randomize a search, upload photo's through their phone camera, plot their location through GPS. These are things you'll actually have to build specifically for the mobile device - you obviously don't want this functionality for users on a desktop!

There may also be a lot of functionality on your main website that you want simplified and altered significantly on the mobile experience. If you have an iPhone, think of how different the main Facebook website is from the iPhone app version of Facebook. On the latter, the functionality is simplified significantly from how you would use it on the website (no instant messaging for example).


An added benefit of mobile websites is that you can include a link at the bottom of the site "Click here to leave the mobile version". This way, you can present your user with choice so they default to the mobile version, but can always load the desktop version on their phone if they so choose.

2) Weight

With responsive, again, the HTML page is exactly the same regardless of what device you're viewing it on. On a mobile device, every bit of information a user has to download counts - because users often have slower internet connections and their phones have less memory than a desktop computer.

So if your main website has a lot of intensive graphics, videos, and sounds that a user has to download, responsive design is not going to change that when the user is viewing it on a smart phone. A mobile web app on the other hand is a completely different site, made specifically for phones, and there are a lot of techniques developers can employ to make the page as fast and lightweight as possible.

I won't get too much into the technical stuff here, but it would include using HTML5 local storage techniques, limiting the amount of http requests, keeping Javascript libraries as compressed and minimal as possible, loading smaller images and a whole lot more.

3) Business Model

If you have a blog, chances are your website will be used the same way regardless of what device you're user is accessing it with. Blog's are always for finding and reading content, and sometimes commenting on a post. In that case, responsive design is probably a perfect solution, since it allows the content to be optimally viewed on a phone.

Now on the other hand, if your website involves a lot of user functionality, like the aforementioned Facebook, which includes adding photos, tagging pictures, posting content, finding friends and more, it's much better to design a specific mobile experience that varies greatly from the desktop experience.

And you don't have to be as big as Facebook either. There are a lot of companies whose desktop websites wouldn't translate well as merely a shrunken down mobile version, but would benefit from a true mobile app. Some examples may be banks, movie theatres, restaurants, concert venues, e-commerce stores, social sites... the list goes on.

The other factor to consider too is whether or not you want to sell your app and/or make it available on the iTunes Store or Android Marketplace. If you do, responsive is not going to work. On the other hand, you could make a native iPhone/iPad/Android app, OR build a mobile web app using open standards and using the insanely clever PhoneGap, you can package your web app as if it is a native app. This will enable you to use the phone hardware like contact lists, voice and camera, and will also allow you to sell it on app stores.

Closing thoughts

As a general rule, I like to think of it like this: If your website is  meant to be viewed, Responsive Design is an amazingly simple technique to please visitors on your site (in fact, I think that building in Responsive is the first place every company should start when they want to dip their toes in the mobile landscape).

On the other hand, if your website is primarily meant for users to interact with (games, accounts, videos, social, e-commerce etc.) then a mobile web app is an important investment worth making.

We’ve had a makeover!

Posted On August 23rd, 2011 Author Amy Wheaton Filed Under Headspace News, Design, Comments 3

Over the spring and summer we’ve been busy working on a new Headspace site, which we’re pleased to unveil today. One of the biggest changes is that our new site utilizes responsive design – it’s accessible from smartphones, tablets, computers, wherever users happen to be. We also placed more emphasis on showcasing our work, our team, our process and our tools of choice.

The old saying when it comes to agency and studio websites is “the cobbler’s children have no shoes” – typically, paying client work comes first (and it should!) Our new site has been a work in progress for some time, and everyone on the team has played a role in getting it ready for launch, from design and programming to copywriting and testing. The site was built in ExpressionEngine 2.0. It also makes use of HTML5 elements, CSS3 (that's where most of those fancy shadows, transitions, rounded corners and gradients are coming from) and JQuery for sliders and modal dialogue windows.

Some of the design elements will look familiar from the old headspacedesign.ca, but we’ve implemented a fresh take on our branding and it figures prominently on the new site. Big thanks to Laura Cosham of Cosham Illustration for her help making us look good and to Kyle, Ricky, and Amy for their work getting everything ready for launch.

We have more features planned to roll out over the next couple of months, so check back often for updates!

Previous Page  Next Page