Created on 23rd February 2025
•
The Problem Our Project Solves:
Independent creators and writers often struggle with limited platforms that allow them to showcase their talent, engage meaningfully with their audience, and gain recognition without the backing of major publishers. Traditional storytelling platforms typically restrict creative freedom, offer minimal reader interaction, and fail to create a truly immersive experience for both writers and readers.
At the same time, readers are often passive consumers of stories, with little opportunity to influence the narrative or feel connected to the creative journey. This lack of engagement leads to lower retention and a less fulfilling experience.
Our platform bridges this gap by empowering indie writers with creative control while offering readers interactive, gamified experiences. Writers can craft dynamic, evolving stories while readers become active participants—suggesting plot twists, introducing characters, making predictions, and influencing the storyline in real time.
By fostering a collaborative storytelling ecosystem, we elevate the creative freedom of indie writers and transform readers from passive observers into co-creators, making storytelling more immersive, engaging, and rewarding for everyone involved.
Challenges We Faced During Development:
Difficulty Accessing Polygon Testnet Faucet:
Obtaining test tokens from the Polygon testnet faucet was unexpectedly challenging, which made testing the Web3 functionalities a careful and time-consuming process. We had to be extremely cautious with our testing strategy to avoid running out of tokens mid-development.
Managing a Multitude of Features:
The sheer scope of features we aimed to implement demanded continuous cross-testing and intense development cycles. This resulted in a high-pressure environment, leading to exhaustion and sleepless nights throughout the 36-hour hackathon.
Time Constraints on Web3 Integration:
Due to time limitations, we couldn’t fully integrate all the planned Web3 functionalities or establish seamless connections with some backend elements. This limited the overall potential of certain features we had envisioned.
Incomplete Role-Based Route Protection:
Implementing role-based route protection proved to be another casualty of the tight timeline. While it was a planned security feature, time constraints prevented us from integrating it into the final build.
Tracks Applied (3)
Polygon
Major League Hacking
Major League Hacking