Prototype, Production Unit, Rendering or Concept? A Crowdfunding Hardware Evidence Guide

Prepared by the ChatField Editorial Team. Evidence reviewed August 18, 2026.

Hardware campaigns use photographs, diagrams, videos, interface screens and development images to explain a product. Backers need to know what each visual actually proves. A working J25 unit, a future J28 concept, an appearance model and a system diagram should never be presented as if they have the same development status or evidence.

Short answer

Label every visual with the exact model, unit type, date and purpose. Show working behavior with an uncut or clearly described demonstration. State what remains to change before production. Do not use existing J25 tests, FCC records or range evidence to imply that a separate future product has already passed the same gates.

Working prototype

A working prototype demonstrates specified functions in a real physical unit. The campaign should identify which functions work, which are simulated, which software and hardware versions were used, and whether the unit matches the proposed reward.

Kickstarter's hardware rules require creators in hardware and product-design categories to show working prototypes and do not allow photorealistic renderings. Creators should also explain how the product will be produced and whether they have made something similar before.

Appearance prototype

An appearance prototype shows size, shape, color, fit or handling but may not contain working electronics. It can help explain industrial design, but it does not prove radio range, battery endurance, application behavior or production readiness.

Label it “appearance prototype — non-functional” if that is the truth.

Production-intent sample

A production-intent sample is closer to the intended materials, hardware, firmware, assembly and packaging. State which components or processes remain non-production. A sample built by engineering methods may not prove factory throughput or final quality control.

Finished production unit

A production unit should match the controlled bill of materials, approved firmware, label, packaging and quality process for the product being sold. If the campaign uses current J25 production evidence to demonstrate company capability, keep that evidence clearly separate from a future reward model.

Diagram, UI mockup or concept

A diagram can explain the operating path. A user-interface mockup can explain an intended interaction. A concept image can explore appearance. None is evidence that the depicted function exists in working hardware.

Use visible labels such as “system diagram,” “interface concept” or “planned feature.” Avoid lighting, shadows and camera composition that create the net impression of a finished physical product when no such unit exists.

Keep model identity on every evidence item

Current public J25 evidence includes FCC ID 2BVP9-J25, 5 km urban-obstructed testing and up to 10 km in ideal open terrain. These are J25 evidence statements.

A J28 or future reward product needs its own hardware, software, range, compliance and production evidence. Review the J25 specifications page and compliance page for the current model boundary.

Show the complete operating path

For current J25 use, the smartphone is the interface, Bluetooth connects it to the carried J25 terminal, and the configured terminal carries supported traffic through the local LoRa mesh to another equipped terminal and paired phone.

A photograph of someone holding a terminal like a walkie-talkie would create the wrong product impression. Demonstration imagery should show the phone interface and carried terminal accurately.

The How It Works page provides the current architecture.

Evidence label template

• Model: J25, J28 or other exact identifier
• Unit type: working prototype, appearance prototype, production-intent sample, production unit or concept
• Date and version: hardware, firmware and application
• What is demonstrated: exact supported function
• What is not demonstrated: untested or simulated functions
• Conditions: route, terrain, phones, configuration and editing
• Next milestone: remaining engineering or production gate

FTC claim review

The FTC advises that advertising must be truthful, non-deceptive and supported by evidence. Review the whole impression created by words, images, captions and omissions. A small disclaimer may not correct a dominant visual claim.

Contact ChatField procurement support to request current controlled evidence for the exact product shown in a campaign or quotation.

Sources reviewed

• Kickstarter: Hardware and Product Design Project Rules
• Kickstarter: Plan Milestones
• FTC: Advertising FAQs for Small Business

Kickstarter and the FTC do not endorse ChatField, J25 or J28. Their materials provide platform and advertising context, not approval of a campaign or product claim.