The problem YearBlocks solves

YearBlocks solves several problems related to traditional yearbook distribution and ownership. Here are the key problems addressed by YearBlocks:

Centralized Yearbook Distribution: YearBlocks eliminates the need for physical yearbook distribution by providing a digital solution. This eliminates logistical challenges such as printing, storing, and distributing physical copies to students, staff, and parents.

Cost and Accessibility: By leveraging blockchain technology, YearBlocks enables free minting of yearbooks for students and staff whose email addresses are whitelisted by the school. This reduces the financial burden on students and ensures equitable access to yearbooks for all eligible individuals.

Immutable and Secure Ownership: The use of the Flow blockchain ensures that each minted yearbook is uniquely owned and securely stored. Through Hybrid Custody, YearBlocks allows students or parents to gain permanent custody of their yearbooks, ensuring that they have control and access to their memories even after their time with the school has ended.

Simplified Authentication and Onboarding: YearBlocks utilizes walletless onboarding, allowing students to create accounts and log in using their Google for Education email addresses. This streamlines the registration process and eliminates the need for students to set up separate wallets or remember complex cryptographic keys.

Enhanced User Experience: YearBlocks offers a viewer that works seamlessly on both desktop and mobile devices. This provides an intuitive and user-friendly interface for students and other users to navigate, zoom, and search through the yearbook content, enhancing the overall viewing experience.

Long-Term Preservation: By storing yearbooks on the Flow blockchain, YearBlocks ensures the long-term preservation of these valuable memories. Blockchain technology provides immutability and durability, safeguarding the yearbook content from loss, damage, or deterioration over time.

Challenges we ran into

Dev Diary: Issues Encountered with Developing on Flow Blockchain

Introduction:
In this dev diary, we will document the various issues encountered during the development process on the Flow Blockchain. While the Flow Blockchain offers promising features and capabilities, several challenges and limitations have been identified, hindering the smooth development experience.

1. Flow CLI doesn't work on Windows11:
One of the significant issues faced by developers is the incompatibility of Flow CLI with Windows11. This prevents Windows11 users from leveraging the full potential of the Flow command-line interface for their development tasks. The Flow team needs to prioritize fixing this issue to support a broader range of developers.

2. Lack of sufficient documentation for different features, specifically Attachments:
Developers have faced challenges due to the lack of comprehensive documentation for various features, especially regarding Attachments. The documentation gaps make it difficult to fully grasp the functionality and potential use cases, leading to extended development times and increased frustration.

3. Testnet/flows can be very buggy and crashes quite often:
The stability of the Testnet and flows is a persistent concern. The platform experiences frequent crashes, especially when dealing with buggy contracts deployed to an account. This instability hampers development and testing efforts, making it challenging to ensure the reliability of applications.

4. Flowscan don't showcase NFTs owned by a certain account:
An issue that has been observed is the apparent inability of Flows to showcase NFTs owned by specific accounts. This lack of transparency raises questions about NFT ownership and management, and it needs to be addressed or better documented for clarity.

5. Lack of example repositories linked in documentation: more in linked doc...
https://docs.google.com/document/d/106ctcB_sidHFHHvh9TNjGFzz3CPabo2CCmogN4gkcgc/edit