Menu
  • UX Trending
  • UX PODCASTS
    • DESIGN UNTANGLED
    • UX CAKE
  • UX Reading Room
  • UX Portfolio Building
  • UX JOBS
    • Atlanta
    • Dallas
    • Los Angeles
UXShareLab… everything you need to know about UX and more…
for the user experience design community

Search

Browse: Home   /   Terminology: PIN code or Passcode?

Terminology: PIN code or Passcode?

by UXStackExchange on March 27, 2014 in Devices, E-Commerce, Forms, General, Information Architecture, Interaction Design, Interfaces, JavaScript, LA UX Jobs, Marketing, Material Design, Mobile, Personas, Product Strategy, Prototyping, Resources, Responsive Web Design, Stakeholder interviews, Testing, UI, Usability, User Experience, User Interaction, User Research, User testing, UX Design, UX Rockstars, UX Toolbox, Visual Design

I'm working on an iPhone, and we are currently doing some user testing. This app deals with sensitive personal information. Security is definitely important for us. Instead of using username / password based authentication, we decided to go with 4 digits PIN/Passcode based authentication.

User needs to input the passcode each time he invokes the app, and we don't want to hurt the usability by forcing the user to use his password each time.

Currently, we call this passcode as PIN, because our web application uses the same terminology. User feedback suggests, our beta testers are unable to discover this feature.

When users login for the first time, we suggest them to set a PIN, so this is not something they can miss. I believe this is because iPhone users are more accustomed to the terminology "Passcode" then "PIN".

Maintaining consistent jargon seems like a no-brainer, but should we maintain uniformity between our products or with the system?

If you think about it, "PIN" is a concept people should be familiar with (ATMs use the term "PIN").

Tags: ux stack

Sign Up for the latest in UX News...

Enter your email address to subscribe to UXShareLab and receive notifications of new posts by email.

Join 834 other subscribers

Related Posts

Same date for multiple Date inputs
Same date for multiple Date inputs
What are best practices for blocking UI when application is busy
What are best practices for blocking UI when application is busy
Is it better to separate settings from task tab or to group it?
Is it better to separate settings from task tab or to group it?
Minimum generic initial features per SaaS product [closed]
Minimum generic initial features per SaaS product [closed]

Terminology: PIN code or Passcode?

by UXStackExchange on March 27, 2014 in Devices, E-Commerce, Forms, General, Information Architecture, Interaction Design, Interfaces, JavaScript, LA UX Jobs, Marketing, Material Design, Mobile, Personas, Product Strategy, Prototyping, Resources, Responsive Web Design, Stakeholder interviews, Testing, UI, Usability, User Experience, User Interaction, User Research, User testing, UX Design, UX Rockstars, UX Toolbox, Visual Design

I'm working on an iPhone, and we are currently doing some user testing. This app deals with sensitive personal information. Security is definitely important for us. Instead of using username / password based authentication, we decided to go with 4 digits PIN/Passcode based authentication.

User needs to input the passcode each time he invokes the app, and we don't want to hurt the usability by forcing the user to use his password each time.

Currently, we call this passcode as PIN, because our web application uses the same terminology. User feedback suggests, our beta testers are unable to discover this feature.

When users login for the first time, we suggest them to set a PIN, so this is not something they can miss. I believe this is because iPhone users are more accustomed to the terminology "Passcode" then "PIN".

Maintaining consistent jargon seems like a no-brainer, but should we maintain uniformity between our products or with the system?

If you think about it, "PIN" is a concept people should be familiar with (ATMs use the term "PIN").

Tags: ux stack

Related Posts

What is the easiest way to automatically collect user data in a prototype app?
What is the easiest way to automatically collect user data in a prototype app?
Weekly News for Designers № 663
Weekly News for Designers № 663
20 Stunning Minimally Designed Templates for PowerPoint & Keynote
20 Stunning Minimally Designed Templates for PowerPoint & Keynote
Is There a Word Which Means "Not a Ten-Foot Display"?
Is There a Word Which Means "Not a Ten-Foot Display"?
← What is the appeal of old style numbers and why do modern fonts still include them?
What is the appeal of old style numbers and why do modern fonts still include them? →

Topics

Web Design wordpress UX Toolbox UX User Experience WordPress Plugins uxbooth User testing UX Jobs Dallas UX Jobs Atlanta Visual Design UX Rockstars UX Jobs in Atlanta User Interaction User Research uxstackexchange web-app Usability UI UX Jobs Los Angeles UX Design Universal Design & Accessibility WordPress Gutenberg UI design user-behavior

Feeds

UI UI design Universal Design & Accessibility Usability user-behavior User Experience User Interaction User Research User testing UX uxbooth UX Design UX Jobs Atlanta UX Jobs Dallas UX Jobs in Atlanta UX Jobs Los Angeles UX Rockstars uxstackexchange UX Toolbox Visual Design web-app Web Design wordpress WordPress Gutenberg WordPress Plugins

<span>recent posts</span>

  • UX in 2018: The human element

    • Anywhere
  • Three Takeaways from the Hawai’i Missile False Alarm

    • Anywhere
  • UX in 2018: Content

    • Anywhere
  • UX in 2018: Design, Development, and Accessibility

    • Anywhere
  • The Power and Danger of Persuasive Design

    • Anywhere

connect to uxsharelab

Enter your email address to subscribe to receive notifications of new posts by email.

UXShareLab. Copyright © 2018. All rights reserved.

  • Contact UXShareLab
  • UXShareLab Community
  • UX PROCESS
  • Recommended Reading
  • UX StackExchange