Task Tracker Pro

November 30, 2023

For this task, we'll create a dark-mode.css file first.

January 24, 2023: This was recommended by feedback from an early tester but I'm having doubts about it. Before implementing we should investigate. Most browsers handle this. We can look at other sites as well as consult. January 27, 2023: Given how this may already be handled by many browsers and questions as well as doubts about security, we should lower the priority on this until another or other testers bring up this issue again. There are more pressing features to worry about. April 21, 2023 Consider if this will break anything. If so, move to next phase 1.1 and beyond. Investigate since not a priority.

Nov 4, 2022:

It's possible we need to run a feedback look with several individuals before there's any chance of sharing with the world. Part of our marketing efforts and QA process might be creating training videos for how to use Task Tracker Pro and ways it can help with your projects. It's a this point I may end up a celebrity or spokesperson. I'll have to pray about it but there's nothing wrong with asking Lou for help with this and letting it become a first draft.

June 6, 2023

Consider creating a Task Tracker Pro Facebook group but it might be overkill. If we don't have time for this. Move to Gold Marketing.

We can also automate this for folks who want to sign up!

Potentially find a way to mark a project complete 100% along with a completion date. In the project Summery "ALL" page, it should display greyed out or something but this may need time to figure out. Not a priority.

The intention is to send folks birthday greetings when the time comes. Later we should add the task to automate emails when it's the user's birthday. It's not important and should probably be pushed back to a later date since other systems need to be in place for this to be useful. If possible, consider moving back to a later date or phase.

Nov 4, 2022: I'm not sure what this means except some public means of receiving feedback, perhaps maybe through an embed system. I don't see any immediacy to this, we can move to version 1.1 for reconsideration and kick the can down the street, so to speak.

This may be a huge implemention and most suited for Core next version.

User testing is required for more details. Consider April 20, 2023 Still unsure about this so we can move it over to the next phase for reconsideration.

At this point, it might not be important as much due to the consistency this would have on completion dates. Also, it could be a pain to detect browser date times. Investigate but if it proves to be a pain or more than it's worth, move to Gold. Update April 19, 2023 A GMT might be best if this app is used across the globe. Another option is to let users specify their time zone in their account settings. If it's important for tasks to be assigned based on local time, we could try to detect the user's time zone based on their browser settings or IP address. This can be done using JavaScript or server-side code. However, this is not foolproof and may not work in all cases (e.g. if the user has their browser set to a different time zone than their physical location). At the moment, there's no specific need to set tasks based on local time but the idea of upgrading one's user account so that we can choose which zone we want might be the way to go. Consider. DETAILS To make this work, several things would need to be updated:

• In globals, the time zone would need to look up user's session and prefs need to be get/set for this
• Every instance of NOW() in SQL (and there are many) would have to have its time zone set before entering the task in the database

It's a tremendous undertaking and not worth the work and systems it could break if implemented at this time. Move to Gold and beyond.