← Blog · 20 Nov 2026

What is authentication? Sign-in explained for people building their first app

Authentication is how your app knows who someone is: sign-up, sign-in, passwords, Google sign-in and sessions. What it does, what can go wrong, and what to ask for.

Who are you, and what may you do?

Authentication answers “who is this?” — sign-up, sign-in, a password or a Google account, and a session that keeps you signed in.

Authorisation answers the next question: “what may this person do?” A member sees their own runs; a coach edits plans; you approve members. Most app security problems are in the second part.

What a good sign-in includes

Sign-up and sign-in, “forgot password”, a way to stay signed in safely, sign-in with Google if your users expect it, and a way to delete an account. Passwords stored scrambled (hashed), never as written.

What goes wrong

Pages that hide a button but leave the data open; one user able to load another’s records by changing a link; admin pages anyone can open. These are the things to test, not just “can I sign in”.

How Chirai handles it

Every site Chirai builds has its own customer accounts — email and password, and Google where you want it — with access rules in the database. Before you see the preview, two test accounts try to read and change each other’s data, and before every publish Chiru tries to break in.

Try this prompt

Build a members area for my running club: members sign up with email or Google, see the training plan for their group, mark the runs they joined; coaches post plans; I approve new members.

Build it with Chirai