[OKR] - Blocks

[c0rtexR]

🎯 Objective

Develop an intuitive and modular block system to power the core workflows of data-river, ensuring accessibility for both kids and business professionals.
Why this is important: The block system is the foundation of the platform, allowing users to easily create workflows. It’s critical to make it intuitive enough for beginners and flexible enough for experienced users to extend its functionality.

✅ Key Results

• Complete the development of the five core block types: Start, End, Input, Output, and Logic. #5
• Gather feedback from at least 10 beta testers, including both kids and business professionals, with 70% of respondents finding the block system intuitive and easy to use. #6
• Develop a modular architecture that supports community contributions, with at least 10 custom blocks added by the community. #7
• Implement visual block-to-code conversion #8
• Ensure 100% error-free flow by implementing automatic error detection and stopping if one fails with feedback to end user. #9
• Implement a node graph with ID-based configuration and WebSocket/browser-based result handling #36
• Initial block editor #73

🏆 Success Criteria

Success will be measured by the functionality and flexibility of the block system, particularly in handling multi-request integrations. A successful demonstration would include:

Sending two API requests (e.g., using the Pokémon public API).
Receiving JSON responses from both requests.
Using a value from the first response in the second request to demonstrate multi-step workflows.
Implementing a confirmation/if/condition block to verify that the received data matches expected results, allowing developers to easily test whether the responses meet their criteria.
Ensuring that this process is seamless and intuitive for developers, with error-free execution and positive feedback on the ease of building and verifying these integrations.

⏳ Timeline

Q3 2024

📝 Additional Notes

• Focus on ensuring that the block system supports multi-step workflows, including the ability to chain requests and use values from one API response in subsequent requests.

• The confirmation/if/condition block will be crucial for verifying that the data received matches the expected values, providing developers with an easy way to validate their integrations.

• Regular feedback loops from beta testers, particularly developers, will be necessary to refine the system's ease of use and ensure smooth handling of conditional logic in workflows.

• Weekly sync-ups and collaboration with the community to build and test custom blocks, including API request and confirmation blocks, will be vital to achieving modularity and extendability goals.