console.log: issue 1

ROLE Content Curation, Branding, Editorial Design

console.log is a critique of the current trends and the bubble we've locked ourselves in the creative industry where we only try and make things that are "beautiful" and perfect. I wanted to take the opportunity to create a designed piece about design. As a designer, but more importantly, a student, it’s important to get meta and introspective about norms and trends that emerge and fade in the industry. The only way for us to design for good, is to break out of the ideology that there is only one standard for goodness. Whether we’ve changed for the better or worse, let’s embrace our flawed, but rich, histories and learn from them to better prepare us for the future.

The features are divided into three parts, past, present and future. It didn’t make sense for me to follow a chronological order as hardly anything in design works linearly. There will always be iterations, cycles, going back and forth in all sorts of different directions. I wanted the three parts to also feel like a transition. It starts off traditional by following grids and a predictable design system, but the pages slowly start to evolve as it takes on forms that match the nature of the content, ending in physical representations of digital interfaces.

The goal of console.log is to create an open conversation in the changing field of user experience, touching on topics that range from the future of interaction to ways we can humanize design. The development of web and digital interactions are constantly advancing, and is often followed by rapid changes and trends that affect the way we experience and use the software and hardware that’s available to us. I hope that flipping through the pages, you stumbled upon something that made you rethink and reconsider the physical digital world we live in. 

Using Format