Skip to content

Publishing an Application

CodeCraft Hub is where applications are published and reused. Browse what the community has built, clone a project to build on it, or publish your own so other people can deploy it.


Every published application is listed in CodeCraft Hub, and you can publish your own work from the same place.

Search applications or choose the highlighted Publish app button to start publishing

How to use CodeCraft Hub

MethodHow it worksUse case
Browse & ReuseClone — copy a published project and modify the copy• Try a development board or sensor
• Modify an existing example
• Adapt official projects for teaching or demos
Create & PublishPublish app → below or, Publish manually → Create a new app in editor• Showcase ideas and receive feedback
• Contribute examples for others
• Build a personal project portfolio

Prepare the following materials.

ItemRequirementsNotes
Project Image• Recommended as cover image
• Aspect ratio: 4:3
• Size < 2MB
• Clear and visually representative
Required
Project Name & Description• Concise and attractive name
• May include device keywords (e.g., Wio Terminal, XIAO ESP32S3 Sense)
Required
Firmware File• Format: .bin or .hex
• Must be tested on real hardware
• .bin for Wio Terminal / XIAO ESP32S3 Sense
• .hex commonly used for Grove Beginner Kit
Required
Source Code File• e.g., .ino file
• Optional, for learning and modification
Optional

The application is built in four steps. You can switch between them at any time using the top navigation bar.

Choose Publish app. The dialog opens on its default AI stage; below the or divider it offers Publish manually, where you choose Create a new app in editor. In that dialog, enter Application Name and choose Confirm — the application is created and the editor opens.

Publish app dialog: below the or divider, choose Create a new app in editor under Publish manually

To start from something that already works, open any published application in CodeCraft Hub and click Clone instead.

Changes are saved automatically once you are in the editor, and the navigation bar shows the save status in real time.

This is how others first learn about your application, so it is worth the time.

Give the application a clear name so others understand what it does at a glance, and summarize the core scenario, technologies and devices in concise language.

The name is limited to 60 characters, and the description to 300 characters.

Choose the most appropriate category tag. It affects discovery and promotion.

Available scenes: Maker/DIY, Smart Home, Industrial, Agriculture, Security, Education, Healthcare, Retail, Other.

Set whether others may copy and modify your work, and whether commercial use is allowed.

  • Allow others to duplicate and modify your app: others can duplicate your application into a new editable project of their own, including all images, documentation, models, code and configurations. If disabled, others can still view and deploy your app but cannot create their own copy. Only enable this if you have the rights to redistribute every asset in the project.
  • Allow your work to be used for commercial purposes: others may use your application — and any derivative works they create from it — in commercial products, paid services or other revenue-generating contexts, without owing you royalties or additional permission.

The first image is used as the cover. You can upload up to 16 images; each file must be 2MB or smaller. A 4:3 aspect ratio is recommended.

This is the core of your application: a detailed application introduction and deployment workflow. Use the button in the upper-right corner to show or hide the live preview at any time, so you can review the deployment flow from another user’s perspective.

The editor uses Markdown. Type / while editing to open a shortcut menu for headings and tool blocks.

Describe the background, principles and design of the project in free text. You cannot add tool blocks that call SenseCraft capabilities in this section.

Describe the deployment process step by step so others can reproduce it, including the prerequisites for each step. Click the + control to add steps, keep the order logical, and use the live preview to check whether someone else could follow them.

In the deployment flow you can insert SenseCraft AI integrated features in one click.

  • AI Vision — deploy vision models for object recognition, detection and classification on supported hardware.
  • AI Audio — deploy speech recognition models on supported hardware.
  • AI Vibration — detect vibration anomalies by learning normal vibration patterns and flagging deviations.
  • Node-RED — build and deploy visual logic flows for reCamera.
  • Aily Blockly — flash programs built in the Aily Blockly visual environment to edge devices.
  • Deploy container app — deploy containerized applications to supported hardware.
  • Flash firmware — flash firmware images to devices in one click.
  • Debug tools (coming soon) — inspect and troubleshoot device behavior during deployment.

See Tool Blocks for full configuration details on each block.

List everything needed to reproduce the application.

Search and add official Seeed hardware directly.

For parts that are not from Seeed (fasteners, special cables, 3D-printed parts and so on), provide name, short description and quantity. Purchase links are helpful.

List required software or platforms — for example Arduino IDE, Home Assistant or Edge Impulse.

Review the full application as an end user would. Before Publish, confirm the required fields are complete, and agree to the CodeCraft Hub Declaration for Publishing, in which you confirm that you have the right to distribute the code and assets and that nothing confidential or illegal is included.

After you publish, the draft is sent for review and cannot be edited until the review completes. If you are not ready to publish, exit the editor — progress is saved automatically.


  1. Content and security

    • Copyright and open-source licenses: you must own or have rights to all code, models, images and assets, or comply strictly with upstream licenses (MIT, Apache and so on).

    • Privacy and data security: especially for camera or microphone use, there must be no hidden exfiltration, unauthorized uploads or backdoors.

    • Law and community standards: no trade secrets, illegal material, malware, or violent, sexual or hateful content.

  2. Model quality and hardware fit

    • Model usability: custom models must load and parse correctly on the platform.

    • Accuracy: real-world performance should match what you describe — no overstated claims.

    • Hardware match: model size and logic must fit the boards you claim to support.

  3. Documentation and reproducibility

    • Clear basics: name, excerpt, tags and cover image are accurate and not misleading.

    • Accurate BOM: listed hardware matches what the deployment steps actually use.

    • Reproducible deployment: steps follow a logical order, and concrete details such as pin wiring, threshold values and MQTT settings are spelled out.

  4. Community guidelines

    • No spam: meaningless duplicates or ads without technical value are not allowed.

Your application appears in CodeCraft Hub. You can copy the application link and share it on social media, community forums or project documentation so more people can find and use it.


Every application has two states that can drift apart:

  • Draft — the working copy you edit. Always private, only visible to you.
  • Published version — the snapshot currently visible in CodeCraft Hub. Updated only when a new draft passes review.

You can manage an application from two places, and the available actions depend on which copy you are acting on.

When you open your own published application from CodeCraft Hub, the actions apply to the published version.

  • Duplicate: create a new standalone project from the published version. Useful for branching off a known-good release.

  • Edit: jump into the editor for this app’s draft (same as opening it from My Applications).

  • Unpublish: remove the app from the hub and switch its status back to private. The draft is unaffected.

The actions here operate on your draft.

  • Edit: open the draft in the editor. Changes do not affect the published version until you publish again.

  • Duplicate: create a new standalone project from the current draft.

  • Publish / Publish update: submit the draft for review. The button is labeled Publish the first time and Publish update afterwards. After approval, the new version replaces the existing public listing in CodeCraft Hub.

  • Unpublish: take a public app off the hub and return it to private status.

  • Delete: permanently remove the application.

QuestionAnswer
What if firmware is missing?- Firmware is essential; without it others cannot run your project
- Always test firmware on real hardware before uploading
- If it was not generated, ask CodeCraft AI: “Please provide a .bin firmware file.”
Are GIFs supported in covers and documents?- Yes, in both cover and documentation
- Recommended for dynamic demonstrations
- Keep the file size small to avoid slow loading
Can videos be embedded?- Yes, video links are supported
- Compatible with YouTube, Bilibili, Douyin and other platforms
- Paste links directly into the editor for automatic embedding