2026 Shenzhen Maker Faire · MAKERS CHALLENGE
BEG. BUILD. SHOW. — the booth-to-demo maker experiment
No fixed BOM. No finished robot in your backpack. Discover the components, meet the makers, build a weird functional prototype, and demo it live.
Peter Pan's Techland is proposing this independent community activity. Maker Faire Shenzhen 2026 is publicly scheduled for December 12–13, 2026, Nanshan District, Shenzhen, but the challenge itself, organizer authorization, challenge venue, participation, schedule, sponsors, and awards are not confirmed. The official event website is Maker Faire Shenzhen. This page describes a proposed format open for discussion.
← Challenge hub · LOOKING FOR SPONSORS / Products / Equipment / Funding →
01 / The big idea
Maker Faire is full of builders, products, ideas, and idle demo boards. What happens if a team starts with almost nothing and creates a new device by visiting participating booths?
- For participants: improvise under constraints, practice talking to other makers, and ship a real demo.
- For exhibitors: see your product appear in an unexpected working build, plus verified credits and documentation.
- For attendees: watch the real creative process—not just a display case or presentation.
- For the community: connect teams, exhibitors and independent makers through a visible contribution trail.
Tagline: BEG. BUILD. SHOW. / MAKE SOMETHING RIDICULOUS. “Beg” is playful maker slang; contributions are always voluntary and respectful.
02 / Proposed event at a glance
| Item | Working proposal; subject to approval |
|---|---|
| Dates | Saturday–Sunday, December 12–13, 2026 (same dates as the published fair) |
| Area | Nanshan, Shenzhen; exact workbench / stage location TBD |
| Format | Two-day, in-person maker scavenger hunt + rapid prototype + live demo |
| Size | 8–12 teams, 2–4 builders per team; 20–30 participating exhibitor booths sought |
| Admission | Expression of interest only until organizer approves access, capacity and conditions |
| Core stages | BEG / BUILD / SHOW |
| Output | Safe live demo, Maker Passport, provenance/BOM, 3-minute pitch, image or short video |
| Working languages | Chinese and English; bilingual signage and support as available |
| Organizer status | Independent proposed initiative by Peter Pan's Techland; approval pending |
| Core partners needed | Maker Faire organizer, willing booths, space/power, equipment, volunteers, mentors, media |
03 / Who can join and what to bring
Proposed: teams of 2–4, including independent makers, hardware developers, students, designers, artists, engineers, educators and curious builders. Mixed-discipline teams are encouraged. Solo applicants may request team matching. Minors need event-organizer approval, guardian consent and supervised safe tool use.
Bring: personal laptop, IDEs, reference material, normal debugging software, safety glasses and reasonable personal hand tools. Permitted pre-existing knowledge, libraries, open-source code, SDKs and development environments do not count as a pre-built solution.
Do not bring: a functioning core competition device; a preassembled hardware kit designed for your planned demo; undeclared premium components to bypass sourcing; dangerous equipment or prohibited substances. Teams may propose access accommodations; organizers should ensure comparable support.
04 / Maker Passport & the booth economy
Every team gets a numbered Maker Passport (physical card + optional QR record). Every voluntarily participating exhibitor gets a simple CONTRIBUTOR marker and knows what it is willing to offer.
| Contribution type | Ownership / control | How it is recorded |
|---|---|---|
| GIFT — product, module, component, material, consumable | Donated to the team only with explicit agreement | Booth name, description, quantity, reference value if supplied, receiver, timestamp |
| LOAN — test gear, reusable module, camera, robot hand | Remains the owner's property; return by logged deadline | Asset ID / condition, approved use, responsible borrower, checkout / return |
| TOOL ACCESS — shared soldering, 3D printer, oscilloscope | Supervised use only; never transferred | Slot, operator, hours / material use |
| MENTOR HELP — debugging, SDKs, technical explanation | Advice / assistance, not goods | Mentor name, booth, type of help |
| EXCHANGE — team-to-team part swap | Only if original donor terms permit | Both teams, transfer reason, updated provenance |
Suggested sourcing mechanics (subject to final materials supply):
- Booth participation and donation are opt-in, and a booth can say no at any time. Suggested limit: at most one donated unit per team per visit; exhibitor may set stricter quantities or distribute via a common parts pool.
- Teams should aim for five distinct exhibitor interactions and integrate tangible contributions from at least three distinct exhibitors into the final demo. Organizers may lower or waive thresholds when stock or accessibility does not support them; no team should be penalized for donors' refusals.
- A shared baseline essentials pool (breadboard, standard connectors, basic controller if available, fasteners, wire, safe power) prevents the entire challenge from becoming a lottery of who found the most expensive board. All use must be logged.
- Premium equipment and scarce modules should be handled through a common checkout / reservation queue, not by private exclusive arrangements. Fairness overrides sticker price; gift value does not score points.
- Each contribution can be registered on the passport through a stamped card, handwritten record or QR form. The final story map credits the contributor with their consent.
- Optional Mystery Object: every team receives one equally distributed silly low-risk item, e.g. a rubber duck, cardboard object or old phone shell, and must incorporate it meaningfully. Only activate if supplies and safety are confirmed.
What makes a great donation?
A useful gift is small, safe, documented, and available in quantities: a sensor breakout, LED ring, motor driver, ESP32 board, cable bundle, display, 3D-printed joint, enclosure offcut, switch or button. Exhibitors are never required to donate display samples or costly inventory.
05 / The three challenge phases
Phase 01 — BEG / Meet + Collect
At the briefing, teams receive the safety rules, the common-pool policy and passport. Explore only the approved exhibitor area; explain your intent, obtain permission before picking up anything, ask for a component or technical advice, record every transfer, and tell the booth owner what you hope to build. No aggressive solicitation, crowd blocking, misleading sponsorship claims or dismantling booth displays.
Phase 02 — BUILD / Remix + Test
Return to the common build zone, inventory parts and choose a feasible demo. Sketch an architecture with power/safety constraints, prototype in small increments, book shared tools, and test integration early. Teams can ask mentors and use AI code assistants; however, their team must perform the key hardware integration, understand the implementation and disclose substantial third-party help.
Phase 03 — SHOW / 3-Minute Live Demo
Each team gets 3 minutes to demonstrate + 2 minutes for judges' questions (proposal; final timing depends on stage availability). Show the device operating, say which booths made it possible, explain the engineering trade-offs and be truthful about limitations. A video may document a previous working state but cannot substitute for the required safe live demonstration for the main award. Minor failures are judged transparently; do not hide them.
06 / Proposed two-day running sheet
Illustrative times, not the official fair schedule. Confirm public access, load-in, quiet hours, safety and the stage with the organizer before publishing a timetable.
| Time | Day 1 — Saturday, Dec 12 | Day 2 — Sunday, Dec 13 |
|---|---|---|
| 09:30–10:00 | Staff setup, check-in, consent, power/safety check | Workspace opens, tool / loan audit |
| 10:00–10:30 | Kickoff, passport handover, rules / safety | Standup, mentoring / build priorities |
| 10:30–12:30 | BEG: approved exhibitor visits and contribution logging | BUILD: assembly, debugging and final integration |
| 12:30–13:30 | Lunch / shared-pool inventory | Lunch / stage setup |
| 13:30–17:00 | BUILD: ideation, prototype, tool booking, mentor visits | 13:30 demo freeze + safety check; 14:00–15:30 SHOW / judging |
| 17:00–17:30 | Daily show-and-tell, asset security / shutdown | Awards, contributors' photo and short interviews |
| Closing | Lock up and confirm loan custody | Return loans, teardown, cleanup / documentation |
Operational contingency: If only a single day or a small workshop area is approved, use a 6-hour fast format: 60 min BEG, 3.5 h BUILD, 45 min SHOW, remainder for briefing and reset; shrink team count to match capacity.
07 / Judging and awards
Safety is a pass/fail gate, not a score bonus. The judges may stop unsafe demonstrations immediately; teams receive a reasonable chance to fix low-risk issues before the scheduled demo cut-off.
| Criterion | Weight | What judges look for |
|---|---|---|
| Working live demo | 30 | Functional core interaction, clear proof, reproducible operation |
| Creativity / surprise | 20 | Imaginative use, original concept, playful experience |
| Cross-booth collaboration | 20 | Meaningful integration, accurate passport credits, respectful collaboration |
| Engineering & resilience | 15 | Safe circuits, sensible architecture, debugging, robustness |
| Demo storytelling | 10 | Clarity, audience engagement, acknowledgement of support |
| Resourceful / reusable design | 5 | Sensible use of offcuts, repairs, minimal waste |
| Total | 100 | Ties: higher live-demo score, then judge consensus |
Suggested award categories (subject to award sponsorship): FrankenMaker Award (best cross-booth monster), Most Useless Useful Invention (delightfully ridiculous), Hardcore Maker Award (engineering), Cyber Beggar / Networking Master (collaboration), and People's Choice (attendee voting). A participation certificate or sticker can replace cash prizes; no prize pool is guaranteed at this stage. Exhibitors and monetary sponsors may not purchase votes, judgeships, or scoring advantages.
08 / Shared workbench, devices and safety
Needed zones: check-in / passports, contribution registry, shared hardware pool, build tables, controlled soldering/tool area, supervised 3D printing, charging and safe power, a small stage or demo desk, fire egress and waste/recycling area. Appoint named on-duty safety and equipment custodians.
Baseline safety policy proposed for venue review:
- Use protected, low-voltage DC electronics by default (ideally 5–24 V) with fuses/current limits and checked wiring. No participant-built mains/220 V circuitry on the public workbench. Venue-managed electrical equipment must be installed and inspected by qualified staff.
- No exposed mains wiring, open flame, pyrotechnics, pressurized projectiles, hazardous chemicals, weapons, or Class 3B/4 lasers. Restrict high-powered lasers, high-energy motors, fast-spinning mechanisms and autonomous moving systems until specifically assessed and contained.
- Li-ion/LiPo batteries require protected, intact packs, proper chargers, supervision and appropriate fire response procedures. Damaged / swollen batteries are not permitted.
- Soldering, cutting and 3D printers operate only in approved, ventilated areas under tool-steward supervision. Wear eye protection; children require guardian supervision and age-appropriate access.
- No camera/microphone capture of private data without consent. Use wireless devices within approved frequency and venue rules. No unapproved network scanning or interference.
- Equipment check-in/out records include condition photos where appropriate, usage boundaries, custody, emergency contacts and agreed damage terms. Insurance, liability, deposits and replacement arrangements must be established by organizers and contributors before loans begin, not improvised on-site.
- Anyone may call STOP for an immediate safety concern. Safety stewards can suspend a demo or disconnect power. Emergency evacuation follows venue staff instructions.
09 / Production team and responsibilities
| Role | Proposed staffing | Responsibilities |
|---|---|---|
| Challenge producer / organizer liaison | 1 | Approval, site map, running sheet, exhibitors, escalation |
| Booth and sponsor coordinator | 1–2 | Opt-in outreach, commitments, inventory / acknowledgment |
| Registration & passport stewards | 2 | Check-in, item provenance, loan tracking, basic help desk |
| Safety lead & tool stewards | 2–3 | Power, hot tools, 3D printer scheduling, safety approvals |
| Technical mentors | 3–5 rotating volunteers | Electronics, software, mechanical integration, AI or design |
| Stage host & demo timer | 1–2 | Presentations, Q&A, timekeeping, votes |
| Documentation / media | 1–2 | Photos, project shots, consent, contributor credits |
| Judges | 3 impartial people | Rubric, conflicts of interest, scores and award decisions |
Keep the core team separate from roaming volunteers where possible; staffing scales with confirmed participation.
10 / What teams must submit
- Team / project card: a name, one-sentence premise, and contact person.
- Maker Passport: contributor booths, donated/borrowed components, mentor assistance and return records.
- Proof of building: a working (safe) live demo and a simple circuit / system sketch; disclose any known limitations.
- 3-minute story: the concept, integrations, a surprise or debugging insight, and thanks to supporting exhibitors.
- Documentation: 2–5 images or a 30–90 second video, permission-cleared sponsor credits, and a short parts list. Open-sourcing source code is encouraged but not mandatory; third-party IP and contributor rights remain intact.
11 / Sponsor and exhibitor cooperation
We are LOOKING FOR SPONSORS who can contribute more than money: donated exhibitor products, modules, consumables, shared tools, 3D printer time, equipment loans, mentors, spaces, internet / power, photography, maker prizes and general production funding.
Sponsors receive accurate opt-in attribution, integration stories and (subject to organizer approval) on-site recognition; not guaranteed media impressions, sales, exclusivity or influence over judging. All inventory, lending terms, image rights and logos are agreed in advance.
View the detailed sponsor wish list, equipment terms, benefits and outreach template →
12 / Indicative budget and funding goals
A planning illustration for 10 teams / 2 days, not a quotation or confirmed funding requirement:
| Cost line | Estimate (RMB) | Notes |
|---|---|---|
| Shared consumables and safe power | 1,500–3,000 | Breadboards, wiring, fuses, tape, accessories |
| Printing and workshop materials | 1,000–2,500 | Passport, signage, labels, filament |
| Site logistics / benches / transport | 2,000–5,000 | Assumes many venue elements might be supplied in kind |
| Safety, tools and support services | 1,000–3,000 | PPE, supervision and additional support as applicable |
| Photo/video and community documentation | 1,000–3,000 | Lean crew or in-kind production |
| Awards and contingency | 1,500–4,500 | Flexible; non-cash awards possible |
| Indicative total | 8,000–20,000 | Excludes venue charges, staff wages, taxes, insurance and major rentals if required |
Never treat these amounts as actual quotes. If the organizer provides the space, infrastructure and volunteers, in-kind sponsorship can reduce the cash need substantially. If paid staffing, insurance, venue rental or production charges apply, rebuild this budget accordingly.
13 / Milestones and go / no-go decisions
| Timing (proposed) | Decision or deliverable |
|---|---|
| ASAP | Confirm organizer's permission to pitch an on-site side event and proposed branding |
| Before public registration | Assign a producer, safety lead, area, electricity, storage, accessible routes, terms and insurance arrangements |
| 4–6 weeks before fair | Confirm 15+ voluntary booths / 6+ interested teams; finalize sponsor inventory and baseline kits |
| 2–3 weeks before fair | Lock 8–12 teams, mentors, equipment reservations, prize categories and media permissions |
| 1 week before fair | Publish confirmed schedule and stage map; rehearse passport & loan workflow |
| Day 1 | Check-in, source materials, build, audit all borrowed equipment |
| Day 2 | Safety approval, public demos, awards, returns, cleanup |
| 7–14 days after fair | Deliver recap, partner credits, photos, project links and loan reconciliation |
Go / no-go thresholds: No approved space, no safety/insurance arrangements for loans, too few voluntary booths, or insufficient supervision means postpone, shrink or switch to an off-site independent meetup. Do not advertise a confirmed official event prematurely.
14 / FAQ
Must booths donate something? No. Every gift, loan and mentoring interaction requires consent. No one may pressure a booth or remove display items.
Can a team purchase extra parts? To preserve the premise, direct competitive purchasing is prohibited once the build starts. Documented organizer-provided necessities and accessibility accommodations are exceptions.
Can we bring laptops and existing code? Yes. Standard programming tools, libraries and SDKs are allowed. A ready-made integrated demo brought in from outside is not.
Can we use AI tools? Yes. Teams must understand and responsibly integrate the result and disclose major outside assistance.
What if some teams can't get enough parts? The common pool, shared reservations, fair allocation and a possible lowered minimum booth threshold are there specifically to prevent this.
Who owns the finished prototype? Teams keep their original work and properly donated items, subject to pre-agreed contributor/IP terms. Loaned assets must be returned. Do not promise ownership of untransferred sponsor property.
Are there real registrations or prize money already? No. This page is a community proposal seeking participant interest and partnerships, not a confirmed ticket, sponsor list or cash prize announcement.
15 / Join the discussion
- Teams & maker volunteers: Email your expression of interest, with team size, skills and example projects.
- Exhibitors & sponsors: View the sponsor call or email us.
- Host / organizer discussion: We welcome a conversation about an authorized satellite activity and will align terms, permissions, safety and brand use before any on-site launch.
Document version: proposal v1.0, October 18, 2026. Event dates sourced from Maker Faire Shenzhen. Independent concept; no organizer authorization or affiliation implied.