A Quick Guide to Mobile App Types


So you’ve decided to build an app. One of your first steps – if not the first step – in the design process needs to be deciding on the technical approach you will take to build it. From a development standpoint there are multiple options to pick from, each with their own...


Utilizing Cross-Web-Property Headers and Footers


Whether you're redesigning an entire website, modifying footer text, or changing the name of a menu item, running "duplicated code" for any given element across multiple web properties can be a serious pain point. It's not only incredibly inefficient but also leaves gaping holes for human error...


Client-Side Javascript Error Logging – The Forgotten Child of Website Development


As an ASP.NET developer I incorporate server-side error logging in the mission critical projects I work on to track unhandled exceptions and more. In my server side .NET world ELMAH is the go-to solution. It’s an open source error logging solution that is super easy to configure and use. I can’t...


User Experience Makes a Lovely Carrot, But Google Provides the Stick


All the sites we build today are mobile friendly (responsive). But that has not always been the case. We've been building websites since "smart phone" meant a phone, hidden in a shoe.We're proud to say we have a significant number of websites still humming happily along on decidedly older code bases. This speaks to the longevity of their effectiveness as well as to our long-term client relationships. It also illustrates an occasional reluctance to re-invest in improving and modernizing a critical marketing and communications tool.

Well, Google may force some modernization with their latest algorithm updates. According to Jim Stewart, SEO specialist and founder of Stew Art Media:



Which Comes First, Content or Design?


Web design has its own version of the chicken/egg conundrum. Which comes first, the content or the design? The truth is that great websites are not born of stunning visuals alone. They are the result of much planning and strategy, done long before a single pixel is drawn. And where does all of that start? With the content. No matter how talented a designer or how beautiful the interface they create, a website without meaningful content is doomed to fail its users.

At Chronos we like to kick off each web project with a Discovery Phase to get a big picture view of a client’s goals and establish the foundation needed for short and long-term success. Through a series of stakeholder interviews, as well as a thorough assessment of a client’s current online presence, we establish the following items:


Stakeholder Expectations

Stakeholders are more than just the people at the top footing the bill for a new website. They are the team members that use the website as a sales tool. The customers who rely on it as a means to find information and get in touch. The potential employees searching for jobs and trying to feel out a company’s personality.

We interview a wide spectrum of people who will interact with a website in order to establish what tasks it will need to accomplish. These, in turn, help determine what the site will ultimately look like. For instance, why do people come to the website and what do you want them to do when they arrive? What kind of messaging will be used? What items on the current site (if they have one) are lacking or could be improved? What is working well and shouldn’t be touched?

We start off with a set list of questions such as these, but very rarely do we get through all of them with each stakeholder. Many times the person we’re interviewing will bring up something that we hadn’t thought of and the conversation veers off in an entirely new direction. It’s amazing the range of responses generated by these interviews. And oftentimes they point at crafting the site in a way that wasn’t immediately obvious before, either to us or to the client.


Content Strategy

It’s important to clarify that when we speak of content we don’t just mean written copy. Website content may include photos, videos, resource libraries, blog entries, portfolio galleries – the list goes on and on. Knowing which of these will be included in a website goes a long way in helping to establish a meaningful and functional design.

A great first step is to perform a content analysis, which involves cataloging the content currently available for a site and evaluating its usefulness to the audience. Analytics tools typically used for Search Engine Optimization (SEO) can reveal user flows and content utilization patterns that sometimes surprise, and always inform. The combination of statistical analysis, customer and stakeholder interviews and a thorough indexing of current content helps refine the content focus. Web users have a notoriously short attention span and the last thing they want to do is wade through a mountain of outdated or cumbersome content. On the other hand, an analysis may reveal that site content is lacking. Then decisions need to be made about what content will be generated, by whom, and when.

It’s tempting for clients to say “Let’s just get the site designed and we’ll worry about content later.” But at a bare minimum, some parameters need to be established for any content that will be included in a website.

 


Pages

Authors

Art Director
Principal
Web Developer
Office Manager
Principal
App Developer