Architecture idea for B2B2C app
Hi guys! Just integrated Kinde last week for my MVP, loving the product so far šš»šš»
Just wanted to know your thoughts on the best possible architecture for my authentication flow
In short terms, the app is a āB2B2Cā schema. Iāll have two kinds of āuser typesā: āNutritionistsā and āPatientsā
So basically nutritionists enter the webapp as an admin dashboard where they can perform crud operations on patients (add, remove, update, etc) and patients will have access to a mobile app on android/iOS where they will be able to view their own data, track their progress, track meal planning and more.
I donāt know if the best way is to create an organization for each nutritionist, and add patients as members of the organization, or just create a doctor user and attach patients to it.
Iām a little bit confused here. Mostly because I also want the more cost effective way (I know orgs are more expensive than just MAU)
What do you think about it? Do you have any recommendations or ideas?
Thanks and regards,
Matias
7 Replies
Hey @Matias Daloia,
Thanks for reaching out. Great to hear you integrated Kinde. And thanks for the feedback.
It sounds like you are building a great nutritionist application.
Regarding your question about architectural setup in Kinde, to answer your question I would need to know more about how you want to use Kinde.
Organizations allow you to do many things:
1. Make use of multi-tenancy - see here
2. Customise unique login and register screens per organization, so you can have a different login/register screen for nutritionists and patients - see here
3. Assign different roles and permissions that are unique per organization - see here
4. If a patient has a relationship with multiple nutrionists, those users can belong to multiple organizations and easily switch between organizations without having to re-authenticate - see here
5. Have unique properties (custom data) against organiztions - see here
You can read more information about the benefits of organizations for a B2B2C business here
If at least 1 of these benefits is useful to you, I would suggest using organizations.
If not, you can always couple all your users into 1 organization (default organization) and not pay for any organization usage.
Please let me know if ytou have any other questions, I'm here to help!
Hi OlĆ thanks for the detailed response! Really appreciate it
Basically Iām stuck thinking the auth flow, either using or not using organizations.
Because nutritionists would only login to webapp, and end users (patients) would only login to the mobile app.. so I donāt really know if we need organizations
Would you want the login screen for nutritionists to look different to the logic screen for patients?
And can patients belong to multiple nutritionists?
Also, I would suggest having 2 different Kinde applications: 1 for nutritionists (webapp) and another patients (mobile app)
No it should not look different, patients should belong only to one nutritionist in our platform
Okay sounds like @Matias Daloia you don't need any of the benefits mentioned above. So in that case, I would suggest having all your users in a single organization (default organization) and not use Kinde's organization functionality.
You can always move your users to organizations in Kinde at a later date, and I can help guide you on this.
Is there anything else I can help you with to make this decision of using organizations in Kinde or not?
Ok sounds good for me!
Thanks for your help š
No worries! Thanks for reaching out! More than happy to help.
Don't hesitate to reach out if you come across any other issues.