If you have even an ounce of creativity you have to love Lego. Being a Mac geek who owns a working Mac Classice and lego lover I need this kit immediately.
Looking back at Google over the last year, you’d be hard pressed not to notice that they seem to have finally found a consistent and appealing design language. Gone are the ultra engineer driven interfaces in favour of a minimal yet consistent and appealing experience. The gang at The Verge dug in and discovered that the secret to a full on design revolution came in a rather “un-Google” way. Who knew having people actually talk to each other could be the magic ingredient over there?!?
Virtually every project we work on nowadays includes a mobile component in some form. In many cases we end up discussing how responsive design might be the solution depending on the client’s content structures and overall requirements.
Responsive design continues to evolve and the gang over at The Next Web has posted a great reference gallery of some of the freshest responsive stuff as of January 2013.
I’ve got to be honest and say I am not a huge Microsoft fan. Yes I use a Mac and like Apple products but if I had to label myself I’m a browser guy. Give me pretty much any operating system along with a modern browser like Chrome and I’m in business. That being the case, I’m trying to keep an open mind about Windows 8 and find all of the analysis on how they got to the end result as well as criticisms to be very interesting. Continue Reading…
If you are considered “family and friends” of MitreBox you will have received our launch newsletter at some point in the last couple of days. Through the process we’ve fallen in love with Mail Chimp. Not only do they do a great job of handling newsletters, their toolset is extremely easy to use and it makes me smile. This is a rare good thing. Continue Reading…
Thanks to a couple or retweets, I came across a pretty timely post on the merits of divorcing your content from it’s form. Thinking beyond webpages, and moving into mobile (as well as whatever comes next) is a burning hot topic and one that causes a lot of confusion for clients.
I’ll let you read the original post for all the juicy details, but I wanted to draw attention to one particular portion that focused on resistance to change. If anything, this is the number one reason projects can become extraordinarily hard and may or may not end up the way they were intended.
A “content first” approach may require a fundamental perspective change, both on departmental and personal levels. Stressing now over adjusting could save a gaggle of future headaches.
A tough challenge facing organizations is what values and guidelines should change to refine how they create and deliver content. “For example, I talked to a client this week who asked, ‘So, we’re going to have to get over the fact that sometimes blocks of content will end in an orphan [meaning a single word left hanging on a line by itself]. We’d never allow that in print.’ That’s a simple example, but it shows how some deeply ingrained practices have to change when you move to more flexible, dynamic content.”
I’ll extend this concept a step further and point out that a lot of clients are comfortable with the status quo. They may understand their content in a one dimensional (legacy) context. Although this may have worked well in the past, the reality is much more dynamic. Blobs of content that don’t really have any rhyme or reason need to be reconsidered and turned into organized and structured “objects”. This may remove the “flexibility” to create random content on the fly, but it opens the door to platform and device adaptation which is really where we are going.
Yes it means much more upfront planning and organizing, and potentially an initially higher cost for development, but it long term your strategy involves device and presentation layer flexibility, you really need to start asking some tough questions and develop a new relationship and understanding of your content structures.
SOURCE: Content Marketing Institute
I’d be lying if I said the process for creating a great set of wireframes was easy. In my time both on the client side and on the technical services side of things I have simply come across too many wireframes that do not cut the mustard. Sure they may have contained pretty layouts and some may have even verged on full blown designs, but that’s only part of the job a wireframe is meant to do. Continue Reading…