Base UI support and more flexible (headless) auth components
Hi, I’m currently using TanStack Router (with preload) and accessing router context throughout the app. This setup requires highly composable and flexible auth flows. At the moment, Better Auth UI feels quite opinionated and tightly coupled to a component-based approach, which makes integration with TanStack Form and router-driven flows more difficult. It also seems to rely heavily on database calls instead of leveraging router context for auth state. Are there any plans to: Support Base UI instead of Radix? Expose a more headless API for auth so it can better integrate with custom form and routing solutions? A more unopinionated approach would make this much easier to adopt in advanced setups.
Afonso Paulo about 10 hours ago
Base UI support and more flexible (headless) auth components
Hi, I’m currently using TanStack Router (with preload) and accessing router context throughout the app. This setup requires highly composable and flexible auth flows. At the moment, Better Auth UI feels quite opinionated and tightly coupled to a component-based approach, which makes integration with TanStack Form and router-driven flows more difficult. It also seems to rely heavily on database calls instead of leveraging router context for auth state. Are there any plans to: Support Base UI instead of Radix? Expose a more headless API for auth so it can better integrate with custom form and routing solutions? A more unopinionated approach would make this much easier to adopt in advanced setups.
Afonso Paulo about 10 hours ago
Allow custom Account/Organization settings pages
The AccountView and OrganizationView are amazing, but I can’t extend them to include settings specific to my application. I’d like to pass those component a prop that adds additional pages to the sidebar list along with the component that will display the settings cards for that page.
Jordan Schoen 5 months ago
Allow custom Account/Organization settings pages
The AccountView and OrganizationView are amazing, but I can’t extend them to include settings specific to my application. I’d like to pass those component a prop that adds additional pages to the sidebar list along with the component that will display the settings cards for that page.
Jordan Schoen 5 months ago
Support the creation of dynamic OrganizationRoles
Provide a route (/organization/roles) for managing dynamic roles for an Organization if it is enabled.
Jordan Schoen 5 months ago
Support the creation of dynamic OrganizationRoles
Provide a route (/organization/roles) for managing dynamic roles for an Organization if it is enabled.
Jordan Schoen 5 months ago
Disable "Create Organization" on the AccountView
Better Auth has the following param: allowUserToCreateOrganization The AccountView and OrganizationsCard should support disabling Organization creation.
Jordan Schoen 5 months ago
Disable "Create Organization" on the AccountView
Better Auth has the following param: allowUserToCreateOrganization The AccountView and OrganizationsCard should support disabling Organization creation.
Jordan Schoen 5 months ago
Rejected
Admin UI
UI to support the admin plugin. Defaults would include user, organization, team, member controls similar to how Clerk dashboard works.
Jordan Schoen 5 months ago
Rejected
Admin UI
UI to support the admin plugin. Defaults would include user, organization, team, member controls similar to how Clerk dashboard works.
Jordan Schoen 5 months ago
Add community-driven translations
Currently, Better Auth UI only provides default English translations. It would be helpful to offer additional translations (e.g., French, Spanish, German) maintained in GitHub, so developers can easily integrate localized versions without reinventing them.
Thibault 7 months ago
Add community-driven translations
Currently, Better Auth UI only provides default English translations. It would be helpful to offer additional translations (e.g., French, Spanish, German) maintained in GitHub, so developers can easily integrate localized versions without reinventing them.
Thibault 7 months ago
Completed
Option to configure social provider buttons position in AuthView
Social provider buttons are currently hard-coded to output below email/password in AuthView. Given the popularity of social auth, it would be valuable to have an option to place these buttons above the email/password inputs. Beyond this, it might eventually be nice to have full control over the full auth view configuration, including controlling the position of all of the hardcoded elements within the current view (e.g. OTP). This isn’t something that’s immediately interesting to me, however, I could imagine if you’re adding control for social provider button location, it might make sense to expand this to a full configuration option.
Mickey Kay 8 months ago
Completed
Option to configure social provider buttons position in AuthView
Social provider buttons are currently hard-coded to output below email/password in AuthView. Given the popularity of social auth, it would be valuable to have an option to place these buttons above the email/password inputs. Beyond this, it might eventually be nice to have full control over the full auth view configuration, including controlling the position of all of the hardcoded elements within the current view (e.g. OTP). This isn’t something that’s immediately interesting to me, however, I could imagine if you’re adding control for social provider button location, it might make sense to expand this to a full configuration option.
Mickey Kay 8 months ago