Dayquest Day #3 - Building the Dayquest Gamified Productivity App with Unity - Striking the Balance Between Work, Hobbies, and Life
Juggling plates while juggling hats
Hello, fellow adventurers! Vince Quarles here, with another update on my Dayquest gamified productivity app development journey using the Unity game engine. Today, I'll be sharing my thoughts on balancing work, hobbies, and life, and the progress I've made so far.
One challenge I've been facing is finding the right balance between dedicating time to Dayquest without letting it consume all my focus. The beauty of Dayquest has always been its supportive background presence, and I want to maintain that philosophy in the app's development (no unnecessary notifications for users, and a light, flexible codebase for stress-free development).
🌟 Exciting news: I hit a new high score in my Dayquest Airtable last week! 🌟
While many programmers might recommend using the MERN stack for this type of project, I've decided to stick with Unity for the desktop app. I'm focused on making the app as useful as possible before considering any major technology switches.
Tasks Completed:
Make Monsters/Difficulty/Stars Easier/Clearer | Easy | Needs Testing | 4/24/23
Make Monsters == Points clearer | Easy | Needs Testing | 4/24/23
Hide Bulk Update Button | Easy | Done | 4/24/23
Onboarded Interns into New Project | Medium | 4/24/23
Week Object Points Earned | Easy | Done | 4/24/23
Week Object Average Points | Easy | Done | 4/24/23
Calculate Week Values | Easy | Done | 4/24/23
Save Day/Days | Easy | Done | 4/23/23
Save Week/Weeks | Easy | Done | 4/24/23
Working on the project amid my usual day-to-day tasks has been quite challenging - I'm finding it difficult not to focus solely on Dayquest! However, I've learned that holding myself back ultimately leads to greater project success because I'm more thoughtful when tackling tasks.
Most of the tasks today took less than 15 minutes each, except for onboarding interns, which was complicated due to missing GIT. After some troubleshooting, we resolved the issue and are now looking forward to our interns helping push the project forward consistently.
I also started working on the Weeks data structure, and both Weeks and Days now generate save data. However, they're not yet displayed in tables. Over the next week, I'll look for two 1-2 hour blocks to add these tables.
Upcoming Tasks:
Create Day View | Medium | Todo | 4/28/23-4/30/23
Create Week View | Medium | Todo | 4/28/23-4/30/23
Overall, I consider today a successful first weekday of the project, with many app refinements and progress on the "back end" code.
As a bonus, I found a solution to a major design issue regarding payment processing. I plan to implement Simple IAP System to provide a revenue stream for the project while keeping the core system free, with add-ons for personalization available as "DLC" type purchases.
If you're interested in the application upon release, be sure to check out our landing page:
https://dayquest.carrd.co/
Until next time, happy adventuring, and may we all keep slaying our tasks!