@itexpert120-contra.near [Posted on DevHub](https://near.social/#/devgovgigs.near/widget/Post?id=1216) ## Idea: Building an Events Calendar & Feed with everything.dev # Building an Events Calendar & Feed with everything.dev I want to share my journey and impressions of developing code on the Blockchain Operating System (BOS) for everything.dev. It's been quite an adventure, from creating an events feed to learning about BOS's unique features and facing some challenges along the way. ## Event Feed Development My development journey kicked off with the creation of an events feed. I started by implementing a form for creating events, and this part was surprisingly straightforward since the code resembled React. It was familiar territory. After that, I moved on to building an event view, although it was a rather basic one at first. ## Calendar Integration My focus then shifted to integrating a calendar into the project. I had to format the events I retrieved in a way that could be smoothly incorporated into fullcalendar. It was important to faithfully replicate the design provided by the designer. Additionally, I worked on implementing filtering options, which turned out to be a significant part of the project. These filters covered various aspects like dates, titles, categories, organizers, and locations. I also introduced modals to enhance the user experience. Finally, I developed the events feed according to the provided design and started work on custom event card options, although that part is still a work in progress. ## BOS Development Experience Overall, I found developing with BOS to be relatively smooth. It closely resembled React, so I was able to adapt quickly. I did need to make a switch to BOS's State API, moving away from React hooks like `useState`. One intriguing aspect was learning about the NEAR Social API, which allowed me to index and retrieve data from the blockchain using path and blockheight. It wasn't the easiest concept to grasp initially, but with time, I got the hang of it. The fact that BOS came with Bootstrap design built-in was a huge advantage. It allowed me to create prototypes that looked good and improve the overall UI effortlessly. ## Limitations and Challenges However, it wasn't all smooth sailing. One thing that bothered me was the absence of TypeScript's type functionality in BOS. Even though everything.dev provided types, the lack of a type system within BOS could sometimes make code management a bit tricky. I also personally felt that Bootstrap was somewhat limiting compared to other frameworks like Tailwind CSS, which offer more customization options. ## BOS Workspace and Deployment The BOS Workspace was a significant asset throughout the development process. It made it easy to create components and test them before deployment. However, the deployment process was not always consistent. Sometimes, it worked flawlessly, while other times, it felt like a game of chance. I had to resort to some tricks, like toggling between dev mode and deploy mode, to get it to work correctly. Another quirk I noticed was that the BOS Workspace didn't always recognize changes made outside of the `yarn dev` command. So, if I made quick changes, I had to run `yarn dev` first before deploying with `yarn deploy`. ## Conclusion In conclusion, my experience developing on BOS for everything.dev was overall positive. Despite a few limitations and challenges, I found it to be a promising platform. The familiarity with React, the NEAR Social API's capabilities, and the built-in Bootstrap design features were significant advantages. I'm excited about the potential for future projects on everything.dev and can't wait to see how the platform evolves.