agitodo Beta: Understanding Where Your Game Dev Time Really Goes
Yesterday, I released the beta version of agitodo with a complete redesign of how to measure your growth throughout your game development journey.
What's New?
The beta introduces task-based growth tracking. Instead of growing passively over time like the alpha (which will remain up and free), your skills now develop based on the actual work you put into your game. Every task you complete contributes to your growth across different areas of game development.
Why This Matters
This new approach constantly provides insights into where you're actually spending your time. Let's take a scenario I just experienced: implementing a new combat animation. After 8 hours of work, you might discover you spent:
- 6 hours on artwork
- 1 hour on sound design
- 1 hour on implementation
This breakdown can lead to valuable insights. Is the heavy time investment in art a reflection of your passion? Or perhaps a sign that you need more practice to work faster? Maybe the long investment feels painful and it's revealing that art isn't critical to your game's core fun factor, and you should consider using more pre-made assets?
The Bigger Picture
Now imagine this reflection at scale. After hundreds of hours into your game development:
- Is your time distribution what you expected?
- If 80% of your time goes into art, does your marketing emphasize this unique aspect?
- Are you spending enough time on the elements that make your game fun?
- Could you be more efficient by outsourcing certain aspects?
Current Features
• Task-based skill tracking across game development disciplines
• Detailed breakdown of time investment
• Visual growth tracking
• Insights into your development patterns
Up Next
• Whatever you want!
• Over-time visualization of distributions
• Allow multiple projects
• Customizable skill categories
• Time optimization suggestions
Try It Out
agitodo remains completely free and requires no login. I built it to help game developers better understand where their time goes and how to optimize their development journey. I'd love to hear your thoughts! james@kokutech.com
Thanks for reading,
James