I recently read about what might be one of the worst movies ever made and clicked through to read some reviews and find out why it was so bad. Doing so, I discovered a list of bloopers appearing the film.
Reading about these bloopers was really useful and reminded me about some of the test techniques I use. Read more on Lights, Camera, Action, Bugs!…
Imagine that an application just like the one you’re scheduled to start developing was released in the App store today. This scenario happened to me recently. I was perusing a website when an article caught my attention. As I started reading, I thought to myself, “This description sure sounds familiar.” And it was familiar because it had nearly identical features to an application we’re scheduled to start building in the next few days. This brought me to an interesting infection point — do I look at the competing application, or not?
It seemed like there were three rational answers: look at the released application and marketing materials now, not look at them until our application is complete, or wait until we are into the development of the application to look. Read more on When To Compare Features of a Competing App…
It’s a well-known fact that many people in the older generation has been struggling with new technologies.
For those of us that work in the software or design industries, it’s easy to take technology for granted. Most of us are “digital natives” — we grew up with electronics, and it can be difficult to set those assumptions aside and design for senior “digital immigrants” who spent most of their lives without any type of digital device.
How Seniors Use Technology
Despite being late adopters of technology, seniors have unique day-to-day needs that modern technology helps them solve. Digital devices help seniors with staying active, keeping in touch with friends and family, and daily medical needs. 76% of all seniors own a desktop computer, and use technology for emailing, social media, keeping track of photos, online shopping, and even gaming. Read more on Creating Accessible Interface Designs for Seniors…
Driving decisions about aesthetics and visual design direction with project stakeholders is a delicate process that can be fraught with frustration on all sides. You can increase the likelihood of success and happiness by using targeted artifacts in your decision-making process, but the real secret for success lies in good communication and guidance.
Style Tiles – Between a Mood Board & a Wireframe
Atomic Object has been using style tiles to help guide the visual design direction of software products. If you’re not familiar with style tiles and how they work, here’s a brief overview.
Early, high-fidelity visual design direction has historically been critiqued by reviewing two types of artifacts:
- Mood Boards – A mood board is collage that generally consists of images, text, and objects that reflect an aesthetic direction.
- Wireframes – A wireframe shows a fully-defined user interface.
However, both mood boards and wireframes can be dangerous to use when critiquing visual design. Read more on Facilitating Visual Design Direction with Style Tiles…
Visual Design: Visual treatment of text, graphic page elements and navigational components.
Visual Design Reinforces Decision-Making
Often I hear the term ‘visual design’ referred to as a layer that can be dealt with later on in the design process. To de-couple visual design like this is a mistake I see made often, especially when designers are dealing with constraints above and beyond their control. As Jesse James Garrett illustrates it, visual design should support all decisions made previous in the design process. If another designer is working on the aesthetics of your app, be sure to communicate intent and hierarchy of information architecture, information and navigation design decisions. Read more on Retrain the Way You Think About Visual Design…
As a tester, I learned the standard test techniques of boundary conditions, equivalence classes, state models, path analysis but I’m always on the look-out for new test ideas, how things can go wrong and the ways that people can use things that were never thought of.
Read more on What’s the Risk? – Learning from Others’ Mistakes…
Imagine your perfectly designed apartment. In the kitchen, there would be just enough counter space and cupboard space to keep you from feeling frustrated or cramped. Not too much space, not too many appliances, not too much food in the fridge. Your serving pieces would be both beautiful and functional. And underneath all of this would be a well-considered floor plan, architecture, and planning — allowing all these little pieces to add up to a comfortable space.
The bedroom would be the same. A closet just big enough to organize a stylish wardrobe, but not so big as to promote stockpiling. Furniture and decoration would add the right mix of functionality and style, without having so much as to become oppressive. It would be both functional and beautiful.
The same concepts apply to product and software design. Read more on Form Does Count – Why Even Small Design Decisions Matter…
There are numerous software options for design teams to communicate. Finding a solution that works for your team can be crucial and daunting. Here are just a few of the commonly used communication channels at Atomic Object: Basecamp, Confluence, Dropbox, Gmail, Google Drive, Google Talk, Google+, HipChat, Pivotal Tracker, Screenhero, Trello, and Yammer.
The AO Designers work closely together and are constantly collaborating. We need tools that are fast, direct, and share content quickly. We are constantly trying new programs which aid us in our work. This post highlights two of my new favorite collaboration tools — Hipchat and Screenhero. Read more on 2 Tools for Better Remote Design Collaboration…
Also posted in UX/Design Tools Tagged coll
I chose to use this stock photo in an effort to visually represent this concept at a high-level. It does not represent actual project code or structure I would go about in my own work.
Designing a whole product experience requires fully understanding your constraints and being able to validate the final outcome of your choices. When you’re creating software, both constraints and validation can be wrapped up in technology and code. Can software designers really make the best possible decisions if they don’t fully understand the technical ramifications of what they’re doing? I don’t think they can.
I was recently considering this idea after participating in an AIGA West Michigan roundtable on the topic of designers & coding. Specifically, the question was around how much coding designers should be doing.
Over the past few years, I’ve been doing more and more coding, and it’s been a very positive experience. Here are the top 4 things I took away from it. Read more on 4 Reasons Designers Should Be Coding…
Disclaimer: I swear this is not a promotional blog post. I genuinely really like using this tool for prototyping.
There are many tools and approaches out there for prototyping, and choosing the appropriate tool for a project depends on your skill set, the project’s needs, and what is most appropriate for the client.
Many times, a prototype that utilizes actual code is superior, especially if more complex interactions need to be demonstrated to the client and to other developers. On the other end of the spectrum, crude paper prototypes are a good option for getting ideas out quickly and validating initial concepts. And in other situations, rough clickable prototypes are more than suitable, and can help to move a project along way faster than anticipated. Read more on Painless Prototyping with InVision App…
Also posted in UX/Design Tools