Are your end users facing any friction and what are you doing to solve it?
Hey all, I just had one question and was curious to know if you or your team see any sort of friction that is being caused for your end users?
This could be in:
- sign up or login screen
- outbound email marketing (trying to get them to sign up or claim a discount)
- inviting colleagues or users to share stats with
I wanted to understand how a team goes about solving these friction points.
We heavily use our product ourselves, if a new feature is annoying or does not work as intended, we'll notice ourselves.
Hard to explain how to work on these very subjective things, but maybe give these things a shot:
I get what you mean! Sometimes we feel so biased about what we build that it feels fine but maybe I should get a few people to test it so we can get an unbiased view.
The amount of clicks makes sense too! Will def look into those. Thank you
But in terms of auth ( sign ups or email marketing call backs ) have y’all done anything specific for that?
Well, we noticed that a CTA really needs to make sense and is likely to be more successful if the funnel is well done. Simple example would be not to ask people to signup, but to explain what the benefits of signing up are.
yea, that makes sense. I remember watching this talk on Airbnb how they played around with so many different CTAs and they A/B tested what clicked and not. Thanks for that :)
I've completely removed authentication to remove sign-up or login struggles for one of my apps: https://segro.app
For overall stats, use a session-inspection tool like Inspectled.
Oh this is so cool! But how do you track a verified user ( verified credential like an email ) vs a bot or a dummy user)?
Fair point! I have a special environment file for testing where I put tracking off. Thay way I filter out myself and dummy users.
I don’t detect bots ATM, but a guest have some requirements (such as JS enabled, Google Analytics sees it as a user and I store the GoogleAnalyticsID and the user agent. I know it’s not perfect, but since it is a mobile application, I worry a little less about bot traffic.
Oh and I store the deviceID (actually ID for every unique installation). So I use the number of installs/installation reference, instead of a “user”.
Storing deviceID is actually nice way of doing it! I actually like this approach compared to the traditional sign ups or login to see a unique user. Nicely done dude!
& yea, it makes sense. Since its a mobile application, one wouldnt have to worry that much about bot or unverified traffic.
For the web-approach it's harder though. I like the applications though where there is no long account setup.
Recently I came upon an application that only used email (no password). Login screen: email. Then if you log in, you receive an email with an authentication link. And the session/token duration was super long, so no need to do this other if you don't clear your browser cookies and such.
It has downsides, but just wanted to share this with you since I think it was a nice way of maintain some privacy, keeping accurate email addresses and lowering the steps to sign-up.
We’ve actually built that ourselves too! My friends & I co-founded www.ezid.io which is how you can use passwordless auth in multiple ways.
This company called www.vyro.com.au has done exactly that with our APIs! But they’ve even bypassed the email link for the first time to make the flow with zero friction. Quite cool & we called it just-in-time auth which basically meant authenticate the user only when needed.
I was very to know when people don’t use passwordless then how they go about reducing friction & what metrics they look at. But your device id thing was hella nice & really liked your approach!0
Amazing! I'm bookmarking ezid.
I see big opportunities in combination with building an email list.
Basically you can bypass the sign-up process, and directly make them "users" in your system. Then, in your email marketing, you can drop some auth links and voila!