BOS HACKS
  • βš’οΈAbout BOS Hacks
  • πŸŽ‰Winners
  • ⁉️FAQ
  • Hacker Manual
    • πŸ•‘Schedule
    • βš–οΈHackathon Rules
    • πŸ“Registering
    • πŸ†Prizes & Bounties
    • πŸ“₯How to Submit
    • βœ…Evaluation Matrix
    • πŸ«‚Finding A Team
    • πŸ§‘β€πŸ«Mentors
      • πŸ’ŒFor Mentors
    • πŸ‘©β€βš–οΈJudges
    • 🏨Venues
      • πŸŒ‰NEAR SF
      • πŸ—½NEAR NYC
    • πŸ“šResources
    • πŸ“œCode of Conduct
  • Support
    • πŸ’ΈSponsors
      • πŸ—³οΈExample Bounty
    • 🀝Community Partners
Powered by GitBook
On this page
  1. Hacker Manual

Evaluation Matrix

How judges are evaluating projects?

Evaluation Factors

Projects will be evaluated based on technical ability, usefulness as a product, originality, and likelihood to scale into a business. Some factors in our evaluation matrix include

  • Code complexity & cleanliness: Does the project’s component design patterns showcase a level of maturity? Are children components easy to run? Does their code run efficiently? Does their project showcase a level of technical complexity?

  • Usefulness in NEAR ecosystem & likelihood for communities to fork: is this something that is a primitive someone in the ecosystem would fork? Is this considered developer tooling or something that is infrastructure for BOS? Does the widget metadata include clear documentation for others to do so?

  • Likelihood to continue project into BOS native product: Is this a one time hackathon project or will they continue this into a public good the ecosystem needs?

  • Originality of idea: Is this a novel idea? Is this a use case that would bring external user adoption. If this is based on an idea suggested by an ideas list, how well did they execute the desired ideas.Does the project actually solve a pain point?

  • Product / UX: Does the project have compelling UX? Would a user know how to interact with it without a demo / explanation? Are components mobile responsive and accessible?

PreviousHow to SubmitNextFinding A Team

Last updated 1 year ago

βœ