@mark.cobo What do you think about making Setting model to hold each setting? I think the current implementation won't be flexible enough.

@robert.yap After careful consideration, I agree with your approach to have a Setting modal to hold the values for each setting. Will update the snippet to match the changes.

@mark.cobo @jerome.requioma LGTM 💯

@jerome.requioma I have read this snippet 🕰

@jerome.requioma @mark.cobo For the Mobile settings, to make your work easier all we will need if restrict_mobile_apps (True) is a whitelist of apps, can be empty if none. We don't have much authority to place restrictions on a user when they leave our app based on Google playstore policies. All we are doing now is showing a pop-up when they leave the app to use another one. General logic would be

if(appWhitelisted){
  //Let user continue using the whitelisted app
} else{
//Interrupt user with a pop-up
showPopup()
}

So you see there's no need for the restricted apps list. All apps are restricted unless in whitelist

@peter.munyao, actually you would need the list of restricted apps because it is a incoming feature where the employer has the power to allow a user to use an app/s for x number of seconds.

cc: @sean.kyle.yu @jace.roldan

@jerome.requioma This feature is not possible in Android due to the reason I've said above

@peter.munyao, I think you are confused with the restricted name. Basically, the feature will still allow you to use apps but the pop up will come up after x number of seconds for a specific app the user opened. For example, if I restrict Alec to use facebook only for 30 seconds, we still allow Alec to use facebook but after 30 seconds, the popup shows.

@peter.munyao I believe this is possible with the current the current implementation using AppUsageStats. When the user leaves the app, the other apps that are on the foreground are constantly monitored so we can check if the package name exists in the restricted app list and if it is, we change the countdown of the popup timer to what that restricted app is set to.

@sean.kyle.yu Maybe I should organize a sync to demonstrate why this is not possible since the main premise behind it is the employer can have dynamic times allowed for a user to use an app

@peter.munyao Alright, let's have it after the meeting

@whippetwilson @peter.munyao @jerome.requioma @mark.cobo So we have agreed that the new implementation for the app tracking will be a blacklist:

Employer Side:

• The employer sets the amount of time each user has before the Are you still working prompt shows up and it should have a minimum of 1 minute
• The employer also sets a blacklist of apps that the mobile app should watch out for

Mobile Side:

• When the user is logged in and exits the app, a timer will start based on what the employer set for that user
• Within this time, the user can open whatever app the user wants and the pop up will only show up after the specified time
• When the user returns to the applybpo app (whether the prompt shows up or if the user returns to the app themselves) a list of apps opened within the time the user exited the app and returned to the app will be compiled
• The apps that will be reported/submitted will only be apps that are in the blacklist that the employer has set

Example:

Compiled List of Apps that the user has opened while timed in:

• Facebook
• Phone
• Message
• Twitter
• Pocket Bible

Employer's Blacklisted Apps:

• Facebook
• Messenger
• Twitter
• Instagram

Apps that will be reported (submitted to backend):

• Facebook
• Twitter

Note: If the app in the returned list for the current shift already exists in the backend, it will add the seconds to the existing entry

@sean.kyle.yu, Thanks!

The employer sets the amount of time each user has before the Are you still working prompt shows up and it should have a minimum of 1 minute

@sean.kyle.yu Please explain the reason why 1 minute is the minimum