Flag

We stand with Ukraine and our team members from Ukraine. Here are ways you can help

Get exclusive access to thought-provoking articles, bonus podcast content, and cutting-edge whitepapers. Become a member of the UX Magazine community today!

Home ›› Business Value and ROI ›› 6 Key Questions to Guide International UX Research ›› Seven UX Resolutions for App Design in 2014

Seven UX Resolutions for App Design in 2014

by Drew Davidson
3 min read
Share this post on
Tweet
Share
Post
Share
Email
Print

Save

With 2014 off to a roaring start, here are seven resolutions for designers to follow when designing apps in the new year.

Many innovative trends came into their own this year where experience design and application development converge, specifically the simplicity of flat design and the user-friendly functionality of cross-platform design.

Each of these was a welcome improvement for all app users, and with the new year approaching, this is a great time for app designers to make some UX resolutions for even better digital experiences in 2014.

 

1. I will not use lengthy setup wizards

Users should be able to get inside an app and/or through a setup process without being forced to enter all their profile/account information at the very beginning. Regardless of how important this data is, apps that are built with UX in mind must be designed to offer users the option to enter this information whenever they want to.

2. I will limit feature tours

Multi-page explanations of an app are confusing and the opposite of user-friendly. Well-designed apps and web services should be easy to use and understand, so not only should there be no need for more than three pages of information on usage, if there does need to be a lengthy explanation, it should be provided as users move naturally though the platform.

3. I will leverage retina-level graphics

Anything less just looks unprofessional.

4. I will not blindly follow user requests

Many companies will ask users or internal stakeholders about what design elements they’d like to see incorporated into a web app or service, without doing any research to see if these requests will actually provide the best experience for those users. Ultimately, this approach is destined to end in failure: not only will it fail to solve foundational problems, it may even create new issues.

5. I will not overuse notifications

I’ve heard many people express frustration with the way certain apps abuse their notification systems. Companies think it’s no big deal to send out a plethora of notifications to users, but it’s actually a huge turnoff, the result being that users end up turning off notifications altogether. That’s never a good thing.

New Year’s app design resolution for 2014: I will not blindly follow user requests

6. I will stop using hub and spoke design

The hub and spoke design model refers to design that’s architected around a central hub, with all traffic start there and moving out along spokes that ultimately have to be reversed to get back to that central point. The hub turns into a dashboard that’s purely navigational, forcing users to click something before they can get anywhere else within the app. Let’s see more dynamic hubs in 2014, ones that provide information as well as navigation rather than simply directing traffic to other areas of a site or application.

7. I will not build siloed apps

Applications or web services that don’t allow single sign-on (SSO) options should definitely look to remedy this in 2014. Giving users the option to sign in or sign up through an email or social media account not only helps battle password fatigue, it also allows the app to capture necessary account information. Companies should also take advantage of deep-linking between apps, which supports more efficient interactions with less app-switching frustration. Now that iOS and Android support it, apps need to take advantage.

What are some of your app design resolutions for 2014? Share them on Twitter (#AppResolution) or in the comments below.

 

Image of after party cleanup courtesy Shutterstock

post authorDrew Davidson

Drew Davidson

Drew Davidson is the Vice President of Design at ÄKTA, a digital experience and engagement consultancy. Drew graduated from Purdue University with a bachelor's degree in Cognitive Psychology and a master's in Computer Technology, and his career has allowed him to bring his knowledge of the user experience field to companies across the country, including Nielsen, Motorola, eBay, and NASA. In 2006, Drew won Motorola's People's Choice Award for the best portrayal of a seamlessly mobile society, and in 2013, Business Insider named Drew one of the top 75 technology designers.

Tweet
Share
Post
Share
Email
Print

Related Articles

Another lesson from studying UX with Laura Klein.

Article by Paivi Salminen
The Agile Trap Designers Fall into: Feeding the Beast
  • Agile teams are fast, but designers get stuck in an infinite loop of visual work: redesigning the same components over and over instead of solving real UX problems.
  • Design systems break that cycle, defining the building blocks once, freeing designers to focus on how the product works, not how it looks.
  • When the basics are in place, teams can start working together sooner, prototype faster, and release incremental features without the interface falling apart.
Share:The Agile Trap Designers Fall into: Feeding the Beast
4 min read

Real engagement is about designing experiences that people want to have. Here are some things that games do well that most apps don’t.

Article by Montgomery Singman
Gamification 2.0. Beyond Points and Badges: Designing for Players, Not Metrics. Conclusion
  • Most apps use gamification as a manipulation layer to drive metrics, but people engage with things that are truly worthy of their time, not points or streak guilt.
  • Apps that people stick with do this by designing for intrinsic motivation, making the experience itself rewarding.
  • The true measure of success is whether users feel more capable, accomplished, and enriched for having used your app.
Share:Gamification 2.0. Beyond Points and Badges: Designing for Players, Not Metrics. Conclusion
8 min read

For researchers, AI tools are making the move from advising to building easier than ever. But the real obstacle was never technical. Meet the researchers who allowed themselves to create — and what the cost was.

Article by James Lang
The New Makers
  • The article says that becoming a maker as a researcher is less about learning new tools or skills and more about giving yourself a new identity, and that without fixing the internal permission structures that define your swim lane, even the most democratized AI tools won’t turn a researcher into a maker — you don’t have a founder; you have a frustrated advisor with a prototype.
Share:The New Makers
20 min read

Join the UX Magazine community!

Stay informed with exclusive content on the intersection of UX, AI agents, and agentic automation—essential reading for future-focused professionals.

Hello!

You're officially a member of the UX Magazine Community.
We're excited to have you with us!

Thank you!

To begin viewing member content, please verify your email.

Get Paid to Test AI Products

Earn an average of $100 per test by reviewing AI-first product experiences and sharing your feedback.

    Tell us about you. Enroll in the course.

      This website uses cookies to ensure you get the best experience on our website. Check our privacy policy and