Monday…
Rudy @ March 8, 2010 12:33 pm
SuperSOTM Wallpaper
Chase @ March 2, 2010 2:58 pm
Recently a request came in to our Facebook department from our good friend Nick Grygiel. He asked if we could make a wallpaper out of our new Superman inspired profile image. Nick… you got it buddy. Here it is in all the popular sizes for anyone else interested as well.
Behind the Process | lifetokens part five, webstore
Chase @ February 26, 2010 11:55 am
This final post of the lifetokens process series is about the last big phase of the project, the lifetokens webstore. It’s almost an injustice to condense the entire site down to a single post because it was really more like half the project. As with any online store, the site is the face of the whole company. Someone browsing Gapers Block or notcot for interesting things is not unlike someone strolling down a city street looking into storefronts. We knew it needed to be grabbing, friendly and most importantly, it needed to say what lifetokens is right upfront.
This whole project has come together in a very different visual style than I am used to working in, and this is a very good thing. It isn’t that I am not a colorful, friendly designer… we just tend to have, for lack of a better word, more ’serious’ clients. From a selfish view, lifetokens is a wonderful addition to our portfolio for this reason. This shift in style really became apparent to me when I began working on those first homepage mock-ups.

This is just one of several mock-ups that slowly got us closer to the final site design. When we began work on the website we first mapped out all the functionality we needed to create to have the perfect lifetokens.com. There were going to be some interesting challenges in developing but the design and organization of the site should be pretty simple. Text and images should be big and bold, colors should be bright and eye-catching and it should be very clear where to go for more information or to purchase a token.

It would eventually take a very conscious effort on my part to steer away from what we ended up calling the ’software’ style. This mock-up is clean, well organized, everything you need for a decent website. The problem is you could substitute lifetokens for anything and it would work just as well.

What we needed to figure out was how to give the site the same character we had given to the logo and tokens. We began by flooding the site with color. The backgrounds were no longer white and we even used color as the basis of the site organization. Any general site pages (home, how it works, T&C) would be blue, the shop and checkout would be green, about & contact and the retrieve page is yellow and personal account pages would be red. This worked really well as a method of organizing and separating each section while still having the site feel cohesive.
If you haven’t done so, poke around at lifetokens to see what we mean. The rest of the design really just fell into place with this system.

The retrieval page is the exception to that rule. When someone receives a token in the mail and then takes the time to retrieve it, we wanted it to be a nice rewarding experience. Nothing flashy or over-the-top, just nice. By using Flash we give the experience a little movement and audio. The user enters the code on the back of their token. The Flash movie contacts the database, receives all of the information attached to that code (token design, sender, message) and populates the page with that information. The token then flips and a simple chime (b-flat scale!) is played. Nice…
So that’s it, I would like to thank you for reading all of the lifetokens process posts. You deserve a lifetoken. If you enjoyed them let us know and we will keep doing them for future and past projects.
Behind the Process | lifetokens part four, token printing app
Chase @ February 25, 2010 11:59 am
When we talk to friends and colleagues about the lifetokens project, the big mystery seems to be “how does he print the tokens?”. We could do a whole week just on the trials and tribulations of printing that glorious first token, but for now we will skip ahead to the process we finally settled on.
In the beginning there were two general options of printing the tokens. Option one was having a stock of tokens printed somewhere. There are places online that specialize in printing ‘wooden nickles‘ but the cons of leaving it up to someone else were obvious. Little opportunity for quality control and tweaking, slow turn around when stock gets low and expensive. It was obvious we needed to move the process in-house. After a lot of research (we even tried to build a printer), Jamie settled on using a flatbed printer based on a modified Epson 1390. Printing the tokens in-house solved all kinds of problems such as printing the unique token code on the back and allowing us to keep lower stock of more tokens.
The solution printer also opened up one new problem, there is no special ’software’ out there to help with printing lifetokens on a flatbed printer. A custom tray was created to sit on the bed of the printer to hold up to 20 tokens in place (we will try to get photos of this tray) and Jamie needed to be able to select designs and have them print at the exact same place every time. Unless we expected him to purchase and learn Illustrator himself, it was obvious this software would have to be custom.
Thus the lifetokenstock app was born. Developed in Adobe AIR, we were able to simplify the printing process greatly.
Printing – the primary function of the application is to print the tokens. Using the application you can add up to 20 tokens of any design to print. After printing the front of the token, the application then instructs you to flip the token over before printing the back.
Updating – all of the token graphics are packaged with the application in .swf format. This allows us to add and update token designs by simply sending him an updated version.
Generating Token Codes – another big challenge to the printing process was storing the codes on each token correctly in the lifetokens.com database. The codes used by the printing application are generated by first checking the database to ensure they are not already used. Then, only after Jamie confirms the tokens printed correctly does it send the codes back to the database, adding the new token to stock.
Positioning – because everything needs a little tweaking, we were able to give Jamie the ability to reposition the tokens using very precise increments.
This portion of the project was a lot of fun and I’m sure we will be adding more functionality and tweaks as the company grows.









