The current state of the registration screen is quite static and has a few fixed defined requirements of what should be collected during sign-up. This setup is suitable for the current version of the PR but lacks flexibility.
Solution
Make the registration screen customizable, allowing the collection requirements to be adjusted as needed.
Split some of the fields into smaller, independent components that can be used separately and attached to a more global account-configuration mechanism, similar to the one we have on iOS: SpeziAccount Documentation.
Additional context
The ability to customize the registration fields will provide greater flexibility. It will allow for a more dynamic configuration that can adapt to different requirements and use cases.
Code of Conduct
[X] I agree to follow this project's Code of Conduct and Contributing Guidelines
Problem
The current state of the registration screen is quite static and has a few fixed defined requirements of what should be collected during sign-up. This setup is suitable for the current version of the PR but lacks flexibility.
Solution
Make the registration screen customizable, allowing the collection requirements to be adjusted as needed. Split some of the fields into smaller, independent components that can be used separately and attached to a more global account-configuration mechanism, similar to the one we have on iOS: SpeziAccount Documentation.
Additional context
The ability to customize the registration fields will provide greater flexibility. It will allow for a more dynamic configuration that can adapt to different requirements and use cases.
Code of Conduct