Back to all discussions

  •   12 months ago

Whats considered to be significantly started on bolt ?

The rules state that to be eligible, your project should be significantly started on Bolt. Can someone elaborate on what that means?

  • 7 comments

  •   •   12 months ago

    I would like to know this as well. Can hit token limits pretty quickly...

  •   •   12 months ago

    I mean that's not even the real problem, real problem is the fact that its pritty hard to work in certain rail guards that bolt operates in, certain thigs are easier coded on other platforms and spaces

  •   •   12 months ago

    I think that is mean , Start with a prompt in bolt.new , and according to the rules , you should submit the link of your project too after . That is meant they will probably review how bolt was used in your project. That will take you a lot of time to copy past each file to the project if build on other platform.

  • Manager   •   12 months ago

    Good questions all! We have seen a lot of questions on this so the Bolt team worked on adding clarity here. We plan to update the rules by the 30th with all the other details coming out, but sharing here as its relevant:

    While we recognize that not every part of the development process may be ideally suited to Bolt, the core functionality and final experience must run within Bolt. A light degree of flexibility is allowed, but the focus must remain on showcasing Bolt as the primary platform.

    What This Means:
    Primary Development in Bolt:
    • The initial structure and main development must begin in Bolt.new.
    • Projects must demonstrate meaningful use of Bolt’s capabilities and be functional entirely within the Bolt environment.

    External Tools (Allowed in Support Roles):
    • Tools like Figma, ChatGPT, and other AI/code assistants may be used for idea development, design, prototyping, or generating isolated code snippets.
    • Use of other platforms is permitted only in areas where Bolt is currently less suited—this should be kept minimal and clearly documented.

    Badge Requirement:
    • The final, submitted project must include the auto-applied “Built on Bolt” badge, which will be automatically added to qualifying deployments.

    Project Review & Evaluation:
    • While evaluation may involve some subjectivity, judging will prioritize submissions that are clearly and primarily built on Bolt.
    • Creative use of Bolt is encouraged, but the project should still be a representative example of what Bolt can do today.

  •   •   12 months ago

    "The final, submitted project must include the auto-applied “Built on Bolt” badge, which will be automatically added to qualifying deployments"

    Automatic badge is not possible for my project,

    my project would be coded by bolt, but, built/deployed by other softwares, i'll manually include bolt.new badge, is it ok?

  • Manager   •   12 months ago

    Hello Ravisankar, Thanks for reaching out! Yes, please manually add it using instructions here: https://worldslargesthackathon.devpost.com/details/badgeguidelines

    Best of luck!

  •   •   12 months ago

    "Projects must demonstrate meaningful use of Bolt’s capabilities and be functional entirely within the Bolt environment."

    I think it will have very limited usecase when building machine learning-related/computationally-expensive projects, the flexibility of the environment and the amount of hardware compute required is just not there. Considering Bolt is just a Chatbot and not a Serverless Cloud Container. Also no Reasoning mode and Deep Research makes complex apps very much harder to build.

Comments are closed.