search

michael-mosler / Pius-App-for-Android

GNU General Public License v3.0
1 stars 0 forks source link

Profiles #15

Open Th3Ph4nt0m opened 3 years ago

Th3Ph4nt0m commented 3 years ago

Adding different Profiles for 1 login. Would be a possibility for parents to view the entries for their children more easily.

michael-mosler commented 3 years ago

Sounds cool, but to me it's not clear what a "profile" in this case will be. Parents will not be able to have their own accounts, ok, that's a clear indicator for introducing profiles. But what exactly should change in the display when I login as "parent"?

May be you could outline this is some more detail.

Th3Ph4nt0m commented 3 years ago

@michael-mosler I think it would be the best practice to stay at one login, so we do not need to make changes to the login.

One App can have multiple profiles. Every profile contains another class/course list, so parents can see the plan for multiple students.

michael-mosler commented 3 years ago

Got it! I lost out of mind that parents may have more than one child :-D.

I would expect parents to use their own device. Our kids definitely hadn't liked to share a single device. If so, actually we do not need multiple profiles but parents should be able to configure multiple classes and course lists. Timetable could also be thought.

This means we have multiple sets of active settings. Push notifications will be received for any active settings. This is different from a profile which is something like a closed environment and only one of which is active.

For substitution and timetable related views in the app and also for iOS widgets some navigation and configuration issues also must be solved.

Also backend also must be able to handle multiple classes, course lists per device token.

Overall this will require some work to do and will affect many parts of the app. A starting point could be to change handling of settings in a way that assigns these to a profile/namespace/context with only one (a default one) being used. With this in place we could think of changing Device Token DB to allow for multiple classes (actually we would change primary key). Afterwards one needs to thing about UI/UX questions.