Hi Mark,
Apologies for my delayed response - the day job got in the way yesterday.
No problem I will try my best to lay it all our here - apologies for the long message.
My app is a habit tracker and it is designed for elite sporting academies. The user groups at MVP will be aged 5-8, 9-12 and 13-16.
When a user first signs up for the app, they will have to choose which habits to track for the 1st month and in month 2 they will add in an additional habit. In month 3 they drop 1 or more of the habits and replace these from the available options of habits.
Users aged 5-8 will choose 4 habits to track for month 1, 5 in month 2 and in month 3 they will drop 1 habit and replace it with another habit to give them a total of 5 habits to track in month 3 and they will track a maximum of 5 habits through months 4-12, replacing habits each month as they see fit.
Users aged 9-12 will track 6 habits in month 1, 7 habits in month 2, and 7 in months 3-12. The users will replace habits as they see fit but will track a maximum of 7.
Users aged 13-16 will track 8 habits in month 1, 9 in month 2 and 9 habits in months 3-12. The users will replace habits as they see fit but will track a maximum of 9.
If the user is aged 5-8 they can choose from the following habits to track:
Sleep
Water
Food
Fruit & veg
Time in nature
Tidyness
Brush your teeth
Fundamentals
New Skills
Learning
Play time
Gratitude
If the user is aged 9-12 they can choose from the following habits:
Sleep
Water
Food
Fruit & veg
Time in nature
Tidyness
Brush your teeth
Fundamentals
New Skills
Learning
Play time
Gratitude
Mindfulness
Reflection
Problem Solving
Self Expression
Relationships
Achievement
Exercise
If the user is aged 13-16, they can choose from the following habits to track:
Sleep
Water
Food
Fruit & veg
Time in nature
Tidyness
Brush your teeth
Fundamentals
New Skills
Learning
Play time
Gratitude
Mindfulness
Reflection
Problem Solving
Self Expression
Relationships
Achievement
Exercise
Limit screen time
Therefore the API call i’m looking to build is part of the onboarding/sign-up process in the app. The API call would display the habits that are available for the users age and the user would select from this list the habits that they want to track for that given month. The habits that they are tracking in a given month would then be stored in Backendless and that’s where the API call that is outlined above in this thread comes in - with the relation in the table schema this should identify the habits that are assigned to the user profile. However the API call that I still need to make, will display the habits available for the user age for them to choose which ones they want to track.
I hope this clarifies what I’m looking to make here. Please let me know if any of this isn’t clear enough.
Many thanks for your help and patience with this too,
Eoin