The problem TrackU solves

TrackU SDK addresses the limitations of current analytics tools by seamlessly integrating onchain infrastructure using Fleek to provide a comprehensive solution for tracking user activities across all applications. Traditional analytics tools often struggle to harness the advantages of web3, such as decentralization, verified bandwidth, enhanced security, and scalability. They also pose integration complexities for web2 applications looking to leverage onchain benefits.

TrackU SDK offers:

• Seamless Integration: An easy-to-integrate SDK that works with all the applications, simplifying the setup process and enabling immediate tracking of user activities.
• Advanced Analytics: Comprehensive tracking of user interactions, events, page views, and custom events. Real-time data processing and visualization are provided through a user-friendly dashboard.
• Onchain Infrastructure Benefits: Reduced latency and minimized overhead through edge functions, auto-scaling capabilities, cost-effective pricing, and decentralized storage for data integrity and availability.

By addressing these challenges, TrackU empowers developers and businesses to leverage the full potential of onchain infrastructure while gaining invaluable insights into their user base. It enables data-driven decisions, improves user engagement and retention, and provides a unified analytics solution with real-time insights and enhanced security.

Challenges we ran into

During the development of TrackU SDK, several challenges were encountered:

Bundling:
-Challenge: One of the primary obstacles we encountered was related to the bundling process. Specifically, we faced difficulties with integrating certain packages, such as Mongoose and MongoDB, using the Fleek CLI.
-Solution: We used MongoDB Data Apis that eventually removed the dependency on mongoose and MongoDB packages

Base Sepolia Eth:
-Challenge: Another challenge we encountered was related to accessing Base Sepolia ETH. The Base Sepolia network is an essential component for our SDK, but we found that obtaining easy access to Base Sepolia ETH was not straightforward. This lack of accessibility posed a significant hurdle, as it delayed our development process and required us to seek alternative solutions.