01
Cross-school teams
The best collaborator may be at another school. The room should make that easy, not awkward.
04 / CommunityStudents first / Wider community welcome
Built bypeople whoshow up.
The community is the point. HackMeld is being designed for people who would rather make a first version than talk about a perfect one.
- Focus
- Young builders
- Base
- Hangzhou, CN
- Stage
- Community forming
- Projects
- None published
No invented profiles
People and projects appear here only with permission. Until then, this page describes the room we are trying to build.
01 / Who is in the roomHigh school students first
Differentpeople.One room.
HackMeld is being built around a simple bet: put different kinds of curious people in the same room, give them a real problem, and something useful will happen.
The six groups below come from the brand introduction. They describe who the room is for, not a count of who has joined.
- 01
AI enthusiasts
Curious first, technical second. People who try the new thing before they know what to call it.
Curiosity / Open to beginners
- 02
Independent developers
Students who ship on their own time and have opinions about how things should work.
Code / Open to beginners
- 03
Student founders
Building before university. Willing to test an idea in public while it is still unfinished.
Ventures / Open to beginners
- 04
Designers
Making the product make sense: interface, story, hierarchy and the last ten percent.
Design / Open to beginners
- 05
Creative technologists
Working between code, image and interaction. Interested in what the tool makes possible.
Experiment / Open to beginners
- 06
Young entrepreneurs
Finding the real use case. Asking who needs this, who pays for it and what happens next.
Product / Open to beginners
02 / What we are building towardIntended culture / not a track record
A room witha longermemory.
A hackathon can be a weekend and nothing more. We want the useful parts — the team, the lesson, the unfinished prototype — to have somewhere to go afterwards.
02
Public demos
Work gets shown, not hidden. A demo is a conversation starter, not a final verdict.
03
Documented failures
What did not work is part of the evidence. We want the lesson, not only the launch.
04
Collaboration after
The room should not close when the event does. Keep the project, the people, or both.
03 / Projects and storiesIndex / 000
Real workonly.
This is not a gallery of stock projects. It stays empty until there is real work from a real team, published with permission.
Project index / 000Awaiting first build
Nothing
published
yet.
The first cohort is still forming. Selected work will appear here only with the team's permission.
Be in the first cohort04 / How we want to workOperating values / not achieved outcomes
Four valuesfor theroom.
These are operating values. They are how we want to behave while the community is small enough to know everyone in it.
Make to learn
Build the smallest useful test. Show what changed your mind, not just what worked.
Build with others
Invite a different skill into the team. Name the contribution behind the demo.
Take initiative
Start with a real question. Ask for help early and leave the next person a useful handoff.
Make responsibly
Explain limitations, respect people and data, and choose problems with a person on the other side.
05 / Open callFirst edition in planning
The first cohortis still forming.
If you are a student who wants to build, or a young builder who wants to help make the room, there is a place to start.
No community profiles or project submissions are open yet. Official channels will be published first.