everkit-supabase

everkit-supabase is a shared building block for the Lab apps: Tea Companion, Dial It In and Matcha Companion. It handles the account and backend work that every app needs but no user ever sees, so each app can spend its effort on tea, coffee or matcha

The problem it solves

Every app with accounts has to do the same jobs. Building them separately in each app means the same bugs get fixed several times, and the apps slowly drift apart

• Signing in with email and password, Apple or Google, plus password reset and email confirmation
• Remembering who you are so you stay signed in after closing the app, and nobody else's data shows up after you sign out
• Talking to the backend (Supabase, the online service that stores accounts and app data) in one consistent way

What an app gets from it

• One sign-in system that behaves the same way in every app
• A gatekeeper that sends signed-out people to the login screen and new people to onboarding (the first-run welcome steps)
• A shared user profile with a name, a photo and a join date, which each app can extend with its own details
• A ready-made profile table for the database, with rules that let people see and change only their own profile
• A safe way to run backend tasks such as deleting an account, with clear errors when something goes wrong
• A shared way to save app events such as screens opened and errors hit, so every app records them to its backend the same way

What stays with each app

The package holds no app names, secrets or screens. Each app brings its own settings, its own login screens and its own look. That keeps the package reusable and keeps each app in charge of its own details

An everyday analogy

Think of the front desk in an office building. Every company in the building does different work, but they all rely on one reception that checks badges, knows who is inside and sends visitors to the right floor. everkit-supabase is that front desk for the Lab apps

For developers: see ARCHITECTURE.md