Some of us have been online for decades, and have seen our fair share of walled gardened apps with a login screen hiding the app. We are sort of used to registe

Some of us have been online for decades, and have seen our fair share of walled gardened apps with a login screen hiding the app. We are sort of used to registering, but we are also sick to the teeth of having to register too. The problem can lie in the micro copy too; you often see "10 seconds to register" or, "one click login". It is rarely that - it usually entails a frightful tale of password management, making the password match the requirements of the app (alphanumeric and maximum 8 characters nonsense), alongside a11y issues, PIA (Personally identifiable information) issues, and a slew of other barriers to entry. Very much something that has gone un-noticed by developers for a long time, is that login systems are an obstacle and something to be avoided if we can. Login systems can not be solved with Single Sign On (SSO) / OpenID systems either. (Not all of us have FB/Google accounts, and never presume so) Every developer is scrambling to find a solution for the 'login problem', and completely overlook how login systems complicate things for their users. A lot of login systems suffer from Not Invented Here™ syndrome. Often online forms are a sort of 'mystery meat' where users don't know what to expect there. I once saw an account registration form asking to include an emoji character in my password, for example.