https://q2a.reubro.com/index.php?qa=qa&qa_1=flutter Powered by Question2Answer https://q2a.reubro.com/index.php?qa=7&qa_1=need-advice-on-a-family-members-feature-for-my-health-app&show=15#a15 I would recommend treating Family Members as independent profiles within a single user's account, rather than just as child objects attached to the user. In other words, every health record should belong to a Profile (Self, Mother, Father, Child, Spouse, etc.), and the user account simply owns and manages those profiles. This approach has a few advantages: It keeps the MVP simple—only one login, one account, and no complex sharing or permission management. The data model remains clean because every feature (reports, medications, consultations, vaccinations, analytics) works against a profile instead of being tied directly to the account. If you later decide to support multiple user accounts, you can introduce profile ownership and sharing without redesigning the entire database. You would simply allow another authenticated user to be granted access to an existing profile through a permission layer. Flutter https://q2a.reubro.com/index.php?qa=7&qa_1=need-advice-on-a-family-members-feature-for-my-health-app&show=15#a15 Thu, 06 Aug 2026 06:39:56 +0000