Author: 0xe400a85a6169bd8be439bb0dc9eac81f19f26843
Update Status: On Time
Project Health: 
On Track
Introduction
How we doin Decentraland Community? Howie Doin here with our first update on our exciting new Decentraland Grant, making Atlas Analytics Open Source! Today we’ll share with the community a brief update about our roadmap, timelines, and generally what we’ll be doing over the next few months. As we’re not just maintaining the existing functionality but augmenting it, it’s important that we align our direction with the feedback we get from builders and users in the community.
Highlights
As a prelude to our update, I feel that it’s important to use this opportunity to thank everyone who participated in the voting process, regardless of which way your support landed, on and off the formal forums. Your feedback and criticisms will be taken to heart as we progress throughout the course of the year. Your support demonstrates all of the building, grinding, polishing, and debugging we’ve done over the course of the past three years and wasn’t for naught. So thanks for making it all worth it.
We’ve spent the past few weeks getting organized. We’ve met with the DAO facilitation group to get all the project management platforms we’ll use to track progress in order and configured. We’ve defined a high level roadmap with a large set of features that we at Atlas Corp have identified over time that could add value based on use cases we’ve come across in the past. Many of these features were identified in other metaverses with development platforms; a lot of ideas can be generated from what Roblox or Fortnight offers its creators in order to get KPIs and feedback on their metaverse investments. Other features are more Decentraland-centric and would highlight features native to our more decentralized home.
We’ve assembled a “Focus Group” this month to address the concern of prioritization, as we don’t want to make these decisions in a vacuum. The group was assembled by looking at who used the Atlas Analytics platform the most - seemed appropriate for us to have analytics on analytics. We’ll be engaging this group informally at first and a bit more formally over time to ensure that we are capturing an appropriate cross section of use cases from people who want or depend on the platform. The group has been made as a private channel in the DAO discord, so if you find yourself in that group I encourage you to participate! (We’ll try to give credit where credit is due if preferable!). We’ll relay any feedback we get from that group throughout these
Blockers
No blockers at this time.
Next steps
Development on new features has already commenced. We’ve started on some of the items that we know need to be prioritized - specifically, the work around ease of access. We want to first move the implementation of Atlas Analytics into an NPM package. We want to do this as early as possible as the current workflow requires developers to paste a typescript file into their repositories which isn’t very conducive to change management. We plan on making a lot of changes to the capabilities of the platform over the next year so we want to make sure users have an easy way of incorporating any changes required to the data collection from their scenes without having to take extra steps.
This feature will be published and made open source early, and made available in the official DCL DAO github repo once we’ve completed the work.
We’ve also spent some time trying to mitigate cost and infrastructure bloat. We know that uptake of the product grows, data - which is already growing linearly - could grow exponentially and the costs to support it along with it. We’ve done some early mitigation this month to minimize the impact of future growth, with much of the cost savings coming from paring back our backup management protocols, and eliminating redundant data collection activities that are now the exclusive purview of the other DAO Data protocols from former grants.
Future conversations can take place about how to optimize data storage costs and will be topics to be discussed with the Analytics Focus Group - how far back should we persist the data, how fast do users require responses, how much data can be requested in a single call, what can be cached, etc…
If anyone not currently in the focus group has ideas or suggestions, please do not hesitate to reach out, we want to hear from you too!
Additional notes and links
Thanks to Zino and Fehz and the core DAO teams for their help in getting the DAO discord channel set up for the Focus Group. Will be a big help going forward and as always we appreciate your time!