Chapter 3
User Features
Do users sign in?
Plenty of tools allow access without the need for creating or signing into an account. Google.com is the most used example, which allows you to search the web without creating an account.
Eventually however, most software has some form of account creation. This allows users to interact consistently with other users or save their information for future use.
The process of a user distinguishing themselves is referred to as User Authentication.
How do they sign in?
Signing in requires some unique identification. While a username or email is the simplest to configure, using third party authentication like Facebook, Twitter, or Instagram can make it easier on the user. Instead of remembering another account, they can lean on a primary resource instead.
There are new tools on the market that rollup common authentication providers. While this approach gives up some control, software like Oauth.io can allow your product to have multiple authentication options with little effort. The security risk makes me vary cautious, but the option exists.
Keep in mind, sign in could involve one or more of these options.
Are there tiers of users?
Tiered access to features can create payment thresholds or security checkpoints. On highly collaborative tools you’ll likely see restricted access like ‘view only’, ‘comment only’, or ‘edit access’.
Do users have profile pages?
Social media paved the way profile pages. These pages allow for a glimpse into a users account activity or a way to engage them directly. It’s by no means required, but if the app includes a public facing element, it can feel like an expectation.
Examples of profile pages include:
Do users collaborate with one another?
Collaborative tools are highly valued in the B2B space. They allow users to work from a shared workspace.
Popular collaborative tools include most of the Google Suite such as Docs and Sheets. Tools like Realtime Board also provide a cutting edge glimpse at how robust collaboration has become.