Uploaded November 2025 | Updated September 2026, 2 weeks ago
In this lesson, we're tackling user authentication—allowing people to sign up and log in to your app using their Google accounts. But here's what's different: we're introducing a new way to write acceptance criteria using user workflows instead of to-do lists!
What You'll Learn:
✅ How to create user stories for authentication features
✅ A new approach: writing acceptance criteria as user flows (step-by-step journeys)
✅ Creating a "New User Workflow" for first-time sign-ups
✅ Creating a "Returning User Workflow" for existing users
✅ Why user flows can be more effective than to-do lists for certain features
---
User Stories
# As a New User, I want to be able to sign up for the app easily, so that I can start using the app immediately without much friction:
**Acceptance Criteria:**
1. Nav Bar should have Login and Get Started for Free button
2. New User clicks on Get Started for Free button
3. New User is brought to the sign-up screen where he can signup via his Google account
4. After New User signs up, he's brought to the to-do app screen
5. There should now be a Logout button for the New User
6. New User clicks on Logout button, and he's brought back to the landing page
Technical Note: Set up the database to manage the above user flows, including user registration, authentication, login and logout
# As a Returning User, I want to be able to login and logout easily, so that I can use the app easily without much of a hassle.
**Acceptance Criteria:**
1. Returning User clicks on Login
2. Returning User is brought to login screen where he logins using his Google account
3. After Returning User logs in, he's brought to the to-do app screen
4. There should be a Logout button for the New User
5. Returning User clicks on Logout button, and he's brought back to the landing page
Technical Note: Set up the database to manage the above user flows, including user registration, authentication, login and logout
---
For Singapore Public Servants: While we're using Google authentication in this course, the exact same workflow applies to Singpass authentication! The architecture is nearly identical—you're actually learning how Singapore's national digital identity system works.
Next Up: In the next video, we'll get your Google Client ID set up so users can actually sign up for your app using their Google accounts. This is where theory meets practice! 🔐
I built this for our public service community. If you find it useful, share it across the public service, please. And when you build something, tag me on LinkedIn ( / yongkiat ) I'd love to see what you create!
Let's grow together. See you in the videos!
Instagram: / rogue.teacher.sg
In this lesson, we're tackling user authentication—allowing people to sign up and log in to your app using their Google accounts. But here's what's different: we're introducing a new way to write acceptance criteria using user workflows instead of to-do lists!
What You'll Learn:
✅ How to create user stories for authentication features
✅ A new approach: writing acceptance criteria as user flows (step-by-step journeys)
✅ Creating a "New User Workflow" for first-time sign-ups
✅ Creating a "Returning User Workflow" for existing users
✅ Why user flows can be more effective than to-do lists for certain features
---
User Stories
# As a New User, I want to be able to sign up for the app easily, so that I can start using the app immediately without much friction:
**Acceptance Criteria:**
1. Nav Bar should have Login and Get Started for Free button
2. New User clicks on Get Started for Free button
3. New User is brought to the sign-up screen where he can signup via his Google account
4. After New User signs up, he's brought to the to-do app screen
5. There should now be a Logout button for the New User
6. New User clicks on Logout button, and he's brought back to the landing page
Technical Note: Set up the database to manage the above user flows, including user registration, authentication, login and logout
# As a Returning User, I want to be able to login and logout easily, so that I can use the app easily without much of a hassle.
**Acceptance Criteria:**
1. Returning User clicks on Login
2. Returning User is brought to login screen where he logins using his Google account
3. After Returning User logs in, he's brought to the to-do app screen
4. There should be a Logout button for the New User
5. Returning User clicks on Logout button, and he's brought back to the landing page
Technical Note: Set up the database to manage the above user flows, including user registration, authentication, login and logout
---
For Singapore Public Servants: While we're using Google authentication in this course, the exact same workflow applies to Singpass authentication! The architecture is nearly identical—you're actually learning how Singapore's national digital identity system works.
Next Up: In the next video, we'll get your Google Client ID set up so users can actually sign up for your app using their Google accounts. This is where theory meets practice! 🔐
I built this for our public service community. If you find it useful, share it across the public service, please. And when you build something, tag me on LinkedIn ( / yongkiat ) I'd love to see what you create!
Let's grow together. See you in the videos!
Instagram: / rogue.teacher.sg
