There is nothing more rewarding than watching people use your app and seeing how they interact with it. User testing is a lot like making dinner for someone; you choose a recipe, ingredients, and invest time making a meal you hope your guests will like. Then you sit down with them and talk about what is good about the meal, what could be improved, and if you’d make it again. At Bitovi, we put a lot of value on testing our designs (and our assumptions!) to be sure we’re building the right thing for our clients and our clients' customers.
While re-designing the CanJS website, I ran into a few issues coding the new layout. I needed a way to create a fixed header and a fixed flexible sidebar that would adjust its width based on its content. This meant that the main content container also needed to flex to accommodate more or less sidebar content. This post will show you how I created this layout hack using Flexbox and I will explain how to create your own html template that contains the following:
Most UX processes value low-fidelity design early in a project’s life: simple, hand-drawn sketches, basic wireframes, and even boxy prototypes. It isn’t until later in the process, as the details get filled in, that higher fidelity designs get introduced. It makes sense: lo-fi designs are quick and easy which makes for faster turn-around in an iterative process. But are low-fidelity designs always the best way to go?
After a technology-filled day at work, one of my favorite ways to relax is to sit with my dog and knit something. I love the tactile qualities of fiber. I can create something both appealing and functional (much like the interfaces at work), but without hunching over my laptop.
Lots of design teams can create attractive and functional apps. So what makes Bitovi's design team special?
While doing usability test on a project is a no brainer, it can be challenging to make it part of a fast-moving Agile environment. To overcome this challenge here are 10 best practices you can start using today.
When designing web and mobile apps, we aren’t fully delivering experiences that allow the user to control the interface in a way that makes sense to them. We talk about delighting the user and having empathy, but more often than not, we tend to miss the mark and deliver a frustrating experience. It's time that we consider giving the user more control with how they prefer the interface to function.
Style Guide Driven Development (SGDD) is a fairly new term I first heard from Nicole Sullivan’s talk about her experience on a project for Pivotal Labs. But thinking about some more, I realized SGDD is, at a high level, a practice many are already doing: developing components and documenting them in a style guide.
People have been studying design for ages, but we rarely see much crossover in the design fields. For example, using web design principles are not the only way to design websites. In fact, we web designers can learn a lot from other design approaches to create stronger, more inclusive experiences, on a strong foundation for lasting products.
When I first started mobile first design I used a pretty rigid template for my LESS files. All my designs were split across 5 or so LESS files named: mobile.less, tablet.less, desktop.less, etc. This seemed like a good idea at the time, but I quickly created a mess of impossible to maintain rubbish. I realized, I needed to embrace modules. Here is how I tackled the challenge of creating a maintainable UI library that was mobile first, responsive, and modular.