Creating an app with different users and different app experiences

It is possible but depending on how complex the app will be I wouldn't recommend it. Best would be to just make a separate admin app (if that is you use case)

Well the use case is an app that caters for children and parents, not necessarily an admin side as the parent has the same (if not more) functionality than the child side of the app. Would you consider this complex but not impossible to build using Xano and Bravo? 

ps. we love challenges and would be interested in exploring all possible routes to solving this problem 🙂

If we know a user‘s role (parent or child) within our user table (Xano), can we use that to give a user access to a different set of screens based on the value of their role (using a similar approach to the state pages like the video you made)?

Furthermore, my team and I saw that we can only have one login page per app, so if we wanted to have a the app work in the way described would we need to use state pages or would we be able to feed the app a boolean on login that shows each user a different flow using prototyping and not state pages? 

Please let me know if you need anymore clarification on this, would be more than happy to provide.

After reading your specification, I still think that it's possible. You can/should use the state pages for this. E.g. on login, just check one which person logged in (parent or child) and depending on it send them to their version of the app. From there on you only have to make sure that they can't switch (for example with a button). Note that your biggest problem will be Bravo's page limit of around 40 screens which means you only have around 20 screens per version of the app (including login etc which work for both)

you can solve this issue with conditional visibility. I did but its very comple. In my app i have 3 diferent types of user, member wirh no registration, others wirh registration and admin. All them have to log in at first.

Yes, good point! I imagined it to be a completely different experience.
If you have the same app but parents are displayed an additional button for example it would be better to go with Valter's approach

Depeding on the information, it is also possible to show a complete diferent page for each type of user.

Very interesting! May I ask, the reason you used conditional visibility vs. state pages, was that in order to still fit as much functionality in the Bravo 40 screen limit or was there another reason you used conditional visibility over state pages in your app?

With that being said would be open to sharing some tips, tricks and problems you encountered during this journey of creating a multi-user application? (We could also connect over email)

Thank you for the feedback around the login question I posed and the awareness around Bravo's screen limit. Is that page limit on all packages on Bravo? Also does screen limit include modal pages and pop up pages?

Yes, it's a technical limitation from Figma's side so it's included in all packages. Modal and popups count as well. It's actually about the elements so if you are clever you can use a little over 40 pages. Learn more about it here: https://docs.bravostudio.app/good-to-know/troubleshoot/errors-when-importing#your-design-file-is-too-big