In a world of smartphones connected to smart lights, garage doors, alarm systems, and doorbells, it feels as if we can bring smart connectivity to practically anything. Yet it isn’t as simple as having the idea for new technology.
Have you ever stopped to ponder how certain things—Rebecca Black’s “Friday,” the ALS Ice Bucket Challenge, Fidget Spinners, or Planking—manage to take society by storm? Why these things, and not the trillions of other trends, seem to captivate us? If so, you’re not alone.
I recently moved to a new home, where I found that the light in my entryway was basically useless.
For the past few years, Grio has offered User Story Workshops – often as the first step of a new project. In the past, these meetings were held over the course of two days in our San Francisco offices. However, since the move to remote work, we’ve adapted these workshops to an online environment. As we’ve transitioned, we’ve had to figure out just what makes an online workshop successful.
Unlike the theater, where the maxim “always leave them wanting more” is a common philosophy, when we create new apps, our goal is to give our users all the features they desire. In fact, nothing makes us happier than when our power users- those users that maximize our app’s potential- find new elements that they have been requesting. It’s time to give them the thing they didn’t even know they wanted: command palettes.
On December 25, 2021, the James Webb Space Telescope (JWST) launched from Kourou, French Guiana. Hailed as the most powerful telescope ever built, the JWST is expected to provide 5-10 years of infrared imagery that will allow us to learn more about space than ever before.
You’re the lead user experience (UX) designer on a new client project. The project is in the early stages, but things are going well. You’ve completed the user story workshop, you have a good grasp of the client’s vision, you’ve established a comfortable relationship with the client, and you are feeling great.
You look up with a smile, and to your great surprise, everyone in the room is looking at you. What’s going on? Why are all eyes on you?
Every time you set up an online account or download an application, you are putting some of your personal information on the web. All this information, combined, becomes your digital identity. However, while that information is static, who you are in the real world is constantly growing and changing. The discontinuity between your real identity and digital identity impacts you on both a real and digital level. The question then becomes, how do we begin to reconcile these two personalities so that we can be identified by both?
This post provides my opinions on the strengths, weaknesses, and overall usability of these two frameworks. Though I’ve only spent about one year working with each, I’ve had the opportunity to explore many of the features they have to offer and see firsthand how each has been designed to respond to developer needs.
In quality assurance (QA) testing for new applications, it is often the case that there are more buttons that need pushing, or tests that need running, than there are testers to push the buttons in the timeframe by which those buttons need to be pushed. When teams encounter this, there are three common reactions: