Habits from signing in to things ยท habit 15 of 40
Looking for a sign in with button
The eye goes to the row of buttons before it goes to the fields. When the row is not there the page feels unfinished, and a page that feels unfinished sends people looking for a better one.
What it does everywhere else
On a normal site the row of provider buttons is the shortest path to a working account. It removes the password, which removes the part people are worst at. The identity stays with an account you already guard carefully, and the site you are joining never holds a secret of yours. For many services it is the safest option on the screen.
What it does on this one
Here there is nothing on the other end to federate with. A market has no arrangement with an identity provider, and an arrangement is the only thing that makes those buttons work. So the row is absent, and the absence is a fact about the architecture rather than a sign of a half built page. A page that does show one is offering to receive a credential it cannot use honestly.
The habit
You scan a new account screen for a button that lets you start from an account you already have.
Why it is automatic
This one was taught by every app store, every checkout, every forum opened in the last decade. The buttons moved above the fields because that is where they get used, and the fields below them have become the fallback.
It is also taught by relief. Passwords are genuinely awful. They ask a person to do the one thing human memory is worst at, repeatedly, under rules that change from site to site. The buttons exist because the industry routed around that problem rather than solving it.
So the reflex is not laziness about security. It is often the opposite. People click the provider button because they know their own password habits are poor, and they trust that account more than anything they would invent on the spot.
What it actually does here
The mechanical part is short. There is no button because there is no third party. Every account is local, so the credential is made on that screen and never travels anywhere to be checked against anything. None of that is unusual for this kind of site and none of it is a defect.
What matters is what the absence does to a reader. A page missing the element every other page has does not read as different. It reads as broken, or old, or half loaded. The next move is to go looking for the working version, and searching for a mars market login is how somebody ends up on a page built to be found by exactly that search.
A page that does offer the row is describing itself. A working provider button needs a registered relationship with the provider, and a market does not have one. What such a button can do instead is collect: it opens a form that looks like a provider sign in page and keeps what is typed there. That credential is usually worth more than the market account.
There is a quieter version too. Some pages show the row greyed out, or return an error from it, purely as decoration, because the template they came from had it. That teaches a reader the row is normal here.
Why an incomplete page feels incomplete
Design vocabulary is learned the way spoken vocabulary is, by exposure rather than instruction. Nobody was told that a signup form should carry a rule across it with the word or in the middle, buttons above and fields below. People have seen that arrangement thousands of times, and a form without it now registers as missing something before any conscious thought happens.
The feeling is not evidence. A plain form with two fields and a button was the whole genre for years, and it still is on software that wants no relationship with a large company. Incompleteness here is a report about your own browsing history rather than about the page.
The search that follows the feeling
The risky step is rarely the first one. It is the third. A reader sees a page that seems wrong, decides they must be in the wrong place, and opens a search box. That sequence is reasonable, and it is the one a page built for interception waits for. Whoever builds those pages needs to break nothing. They need only to be findable at the moment somebody decides the plain page cannot be right.
So the habit belongs here rather than under browsing. The trigger is not a search. It is a judgement about a form, made in about a second, using a rule that has served the reader well everywhere else. The search is only what the judgement causes.
What to do instead
Retraining this one means knowing in advance what the plain version looks like, so that plainness stops reading as failure.
- Expect two fields and a button. If that is all there is, the page is normal for its kind and there is no better version to go and find.
- Treat a provider button on a market page as a reason to stop rather than as a convenience. There is no honest way for one to work here.
- If you open a search box because a page looked unfinished, notice that you are about to change how you arrived, and do not.
- Get to the page from what you wrote down beforehand rather than from what a results list offers at the time.
- Never type a provider password into any page reached from a market. That credential is worth more than the account you were making.
How to notice you did it anyway
The trace this habit leaves is in how you arrived rather than in what you typed, so the check is about route rather than content.
- Look at how you reached the registration page. If the answer is a search made after a page looked wrong, that is the habit.
- Check whether you opened more than one candidate and kept the one that looked more complete.
- Ask whether anything in the sequence wanted a credential belonging somewhere else. If so, deal with that first.
- Notice whether you now judge pages here by how modern they look. That standard belongs to the ordinary web.
- Compare where you meant to go with where you actually went.
What readers ask about this habit
Why would a market not offer provider sign in
Because it would need a registered relationship with that provider, carrying the market name and an ordinary account behind it. The absence follows from the architecture, not from the site being unfinished.
Are the buttons themselves a bad idea
No. On ordinary services they are usually the better choice, because they remove a password you would otherwise invent badly. The reflex to look for one simply does not travel to a place where none can exist.
What if a page shows them and they seem to work
Then something is receiving what you type. A working flow needs the provider to recognise the site, and a market page will not be. What happens to credentials afterwards is on the password shape page.