A redesign and rebuild of a legacy interface on a complex existing product. My first major release on the mobile team, this effort included a full design process, custom icons, and full implementation, all while learning the ins and outs of iOS development via wrangling an undocumented codebase.
A configuration tool for static builds, created for my team to use when beginning projects. Allows customization of sitewide color palettes, typography, header and navigation styles, mobile behavior, features, widgets, and much more. Produces a full static build including task pipeline and style guide. Drastically reduces frontend project durations and costs while maintaining a stable company framework.
An adaptation of a forum / messaging product that currently only has a web interface. This effort includes a total redesign to best fit the platform followed by full implementation, including interface creation (with high emphasis on usability and feel), data handling, controllers, and networking. Currently a background effort alongside day-to-day development and design duties on main product.
A fun web project from my time on RD's frontend team. This effort included a full redesign phase in which I established a new visual identity for AIAA, which the organization enthusiastically embraced. Like most of our projects, implementation included not only a new interface, but migration to a new CMS and a complete content strategy. This project also included a number of sub-sites for their major events.
A foundational theme that allows our company to quickly and effectively develop sites in WordPress, directly enabling us to expand our SaaS customer pool. This theme integrates tightly with the above build automator for a streamlined workflow, and it includes an entire foundation of custom blocks, layouts, and pages that meet most customer needs without any additional work required. Emphasizes the client experience, with fast page building, easy training, and low maintenance.
Design concepts for a custom recipe app project contracted by the US Dairy Export Council. While these were made before I officially joined our mobile team (and I therefore had to hand it off for the actual implementation), this is a good representation of my mobile design work as relating to how a design evolves over multiple cycles, incorporating client feedback, establishing rapport with external stakeholders, and designing to emphasizing ease of translation into a working product.
The most interesting project from my time in the University of Arizona's Computer Science program: design a working CPU from scratch. Specifications were given for a minimal custom assembly language, which we had to implement in hardware. We then had to demonstrate any program running on this CPU. Programs were small by necessity, as our CPUs only included three usable registers; my favorite one of mine was a prime sieve that flashes all the prime numbers in the range of 1 to 128, which was an extremely fun challenge to pull off given the hardware restrictions.
Another good representation of my work with RD's frontend team. I particularly enjoyed the design phase on this, with a client willing to try new things and establish a forward-thinking visual identity. This tends to be at the top of the list when RD sends out design work examples to potential clients. As with AIAA, this effort also included a brand new frontend, backend, and content strategy.
A tidy, focused internal project to overhaul the support and documentation site for RD's mobile division. While not as complex as the other web efforts in this collection, this is a good demonstration of how a few key design decisions can drastically impact the usability of a product. This effort also included a content migration, and the potential of having a nice-feeling site inspired the support team to audit and revamp our help articles.
The final project for a Java-based object-oriented programming course at the University of Arizona. This group-based project was flexible, and we were allowed to write up a proposal for anything we felt like making so long as it was of significant complexity; my group chose to design and implement a game in the style of Cid Meyer's Civilization. It can be played against simple AI opponents or locally against other people and includes multiple unit types, varied terrain, fog of war, and simple building mechanics.
Aside from judging the quality of our code, this project was also meant to emphasize working with a team, effectively dividing responsibilities, and working with source control. My main domains here were graphics (including an isometric perspective view, as it seemed like fun), UI design and implementation, fog of war mechanics, and unit mechanics.
One more RD website project, this one a good case study on designing and implementing a large collection of sub-sites under one branding umbrella, including wrangling a ton of content, custom behavior, and access restrictions. This was also a good example on navigating the tricky waters of maintaining a design's vision and purpose through mountains of stakeholder input and many rounds of changes.