Unified-Auth: Clerk-Inspired Authentication System (with Firebase Auth)

This project implements a Clerk-like authentication system using Firebase Auth as the backend. It includes a shared SDK, backend server, web frontend, and mobile frontend.

Why?

The end goal is to create an abstract layer between the auth provider and my application code. For now, the implementation only supports firebase auth.

Disclaimer

This package is currently in active development and should be considered as beta software. While we strive for stability, users may encounter bugs or unexpected behavior. We recommend thorough testing before using this package in production environments.

Key points:

• The API and functionality may change without notice.
• We welcome bug reports and feature requests via our issue tracker.
• Use in production environments is at your own risk.

We appreciate your interest and feedback as we work to improve this package.

Project Structure

• src/server/: Hono.js backend server with token verification
• src/client/: Client TypeScript SDK for Firebase Auth operations

Features

• UnifiedAuth SDK for consistent auth operations across platforms
• Token-based authentication using Firebase Auth
• Automatic token injection for API requests
• Support for multiple sign-in methods (Google, Apple, Email/Password)
• Aim to support protected routes/screens in both web and mobile frontends

Next Steps

1. Implement additional authentication methods (e.g., other OAuth providers)
2. Add user profile management features
3. Implement role-based access control (RBAC)
4. Set up continuous integration and deployment (CI/CD) pipelines
5. Conduct security audits and penetration testing
6. Implement proper error handling and user feedback
7. Add unit and integration tests

License

This project is licensed under the MIT License - see the LICENSE.md file for details.