from the UX perspective the placement & size of the Register/Login switch isn't so great (it's easy to miss on a phone). We probably should change it in the future, but it's not a concern now.
I did some Flutter research recently. Apparently it's an anti-pattern to split the tree into functions returning widgets (like _buildRegisterButton). Instead we should always prefer new widget classes. See: https://iiro.dev/splitting-widgets-to-methods-performance-antipattern/
I'll merge it as it since I made this mistake also in other components and I'll create a new issue for that. But just so that you know: let's use widgets instead of helper methods from now :)
Works great. Just 2 small remarks:
from the UX perspective the placement & size of the Register/Login switch isn't so great (it's easy to miss on a phone). We probably should change it in the future, but it's not a concern now.
I did some Flutter research recently. Apparently it's an anti-pattern to split the tree into functions returning widgets (like _buildRegisterButton). Instead we should always prefer new widget classes. See: https://iiro.dev/splitting-widgets-to-methods-performance-antipattern/ I'll merge it as it since I made this mistake also in other components and I'll create a new issue for that. But just so that you know: let's use widgets instead of helper methods from now :)