@scotttrinh I see that only the links for the builtin signin/signout are exposed via helper methods. Will there be such methods for the rest of the urls, like the password reset email?

I can imagine, that for custom UI I would ship initially just the Sign in and sign out screens, and for the password flows I would fallback to the default ui. That way, I can progressively ship just the screens which users use the most and fallback to default for the infrequent flows.

I see that only the links for the builtin signin/signout are exposed via helper methods. Will there be such methods for the rest of the urls, like the password reset email?

I don't think that's currently planned since those links have been considered internal and subject to change. Perhaps in the future we might be alright with stabilizing those internal routes, but in the meantime you're welcome to link to them as long as you realize that they're subject to breaking changes in minor versions.

I can imagine, that for custom UI I would ship initially just the Sign in and sign out screens, and for the password flows I would fallback to the default ui. That way, I can progressively ship just the screens which users use the most and fallback to default for the infrequent flows.

Yeah, I can see the value in that approach, although I think it's pretty likely that the cost of building those few screens yourself is probably worth it to match the design and feel of the sign in and sign up pages. It would feel jarring for them to be so different, and if they were very similar, I'm not sure it makes sense that you would do something so similar but make it custom.