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

What makes players keep coming back? This piece explores the psychology of hot streaks — how momentum, perception, and smart design can turn short wins into lasting engagement.

Article by Montgomery Singman
The Psychology of Hot Streak Game Design: How to Keep Players Coming Back Every Day Without Shame
  • The article shows how hot streaks tap into players’ psychology, turning momentum into motivation.
  • It highlights the hot-hand fallacy, where players overestimate their chances of continued success.
  • The piece argues that ethical streak design should enhance engagement without exploiting addictive behavior.
Share:The Psychology of Hot Streak Game Design: How to Keep Players Coming Back Every Day Without Shame
26 min read

Trusting AI isn’t the goal — relying on it is. This article explores why human trust and AI reliance are worlds apart, and what UX designers should focus on to make AI feel dependable, not human.

Article by Verena Seibert-Giller
The Psychology of Trust in AI: Why “Relying on AI” Matters More than “Trusting It”
  • The article argues that “reliance,” not “trust,” is the right way to think about users’ relationship with AI.
  • It explains that human trust and AI reliance are driven by different psychological mechanisms.
  • The piece highlights that predictability, transparency, and control make users more willing to rely on AI.
  • It concludes that users don’t need to trust AI as a partner — only rely on it as a dependable tool.
Share:The Psychology of Trust in AI: Why “Relying on AI” Matters More than “Trusting It”
4 min read

What if your productivity app could keep you as focused as your favorite game? This article explores how game design psychology can transform everyday tools into experiences that spark flow, focus, and real engagement.

Article by Montgomery Singman
Flow State Design: Applying Game Psychology to Productivity Apps
  • The article shows how principles from game design can help productivity tools create and sustain a flow state.
  • It explains that games succeed by balancing challenge and skill, providing clear goals, and offering immediate feedback — elements most productivity apps lack.
  • The piece argues that applying these psychological insights could make work tools more engaging, adaptive, and motivating.
Share:Flow State Design: Applying Game Psychology to Productivity Apps
12 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.

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