ChatField J28 Development Status for B2B Buyers
Procurement teams need a clear boundary between a product that can be evaluated against published evidence and a development program that may still change. ChatField J28 is currently a separate development program. It should not be presented as a finalized commercial replacement for J25, and specifications or regulatory evidence published for J25 must not be transferred to J28.
ChatField is the brand. Jingxi Box (Shenzhen) Intelligent Technology Co., Ltd. is the company identified in the current J25 regulatory evidence. This article does not claim that J28 has completed certification, entered mass production, or been deployed by a customer, government agency, rescue organization, or public-safety team.
What is confirmed today
The current public evidence base applies to ChatField J25. J25 is a phone-paired LoRa mesh communication terminal: the smartphone provides the user interface, connects to the terminal through Bluetooth, and supported communications move between participating J25 terminals over the local LoRa mesh link.
J25 is not a traditional handheld walkie-talkie. Its current product identity, workflow, specifications, and FCC evidence can be reviewed through the Technology page, J25 Specifications, and Compliance page. The current J25 FCC ID is 2BVP9-J25. That identifier and its supporting records do not establish the status of J28.
What is not established for J28
A development name is not a finished specification. Until ChatField publishes model-specific evidence, buyers should not assume that J28 has a fixed radio architecture, final enclosure, final firmware, final app workflow, certified operating parameters, production schedule, or commercially available feature set.
Earlier descriptions that framed J28 as a finished off-grid PTT radio, claimed direct screen-based operation, or treated planned features as shipping capabilities went beyond the evidence available for this website. Those descriptions should not be used as procurement specifications.
Keep J25 and J28 evidence separate
Product identity
Every quotation, sample, label, manual, test report, and purchase document should name the exact model. A buyer should reject a package that combines a J28 marketing name with a J25 label or FCC record without a documented explanation.
Regulatory evidence
Verify the applicant or grantee, model identifier, FCC ID, label, applicable exhibits, and the physical sample being evaluated. The presence of J25 evidence does not certify J28 or another future model.
Application and workflow
Ask whether the phone remains the interface, which operating systems are supported, how Bluetooth pairing and recovery work, which communications are supported, and what functions remain available if the phone is unavailable. These questions must be answered with the actual evaluation build, not a roadmap statement.
Range and relay language
Do not copy J25 evaluation references into a J28 request for quotation. For J25, the permitted public language is up to 10 km in ideal open terrain, about 5 km in tests involving urban high-rise and structural obstruction, and evaluation with up to two participating relay nodes. These are evaluation references rather than universal guarantees, and they are not J28 specifications.
A B2B readiness checklist for a future J28 evaluation
- Model evidence: obtain the exact model name, hardware revision, label image, manual revision, and sample serial record.
- Regulatory scope: request model-specific regulatory records and confirm that every identifier matches the sample.
- Feature matrix: separate implemented functions, functions available only in a test build, and roadmap items.
- Phone dependency: document the app, Bluetooth workflow, supported phone environment, recovery procedure, and any functions that require a paired phone.
- Field protocol: define routes, obstructions, message types, team size, node placement, test repetitions, and pass/fail thresholds before the trial.
- Production readiness: request written information about tooling, firmware control, quality checks, packaging, documentation, lead time, and change management.
- Commercial status: distinguish an engineering sample, a pilot unit, and a production order. None of these terms should be inferred from a product name alone.
When should a buyer evaluate J25 instead?
If the purchasing requirement is immediate and the organization needs a documented phone-paired LoRa mesh workflow, J25 is the current product with a public evidence pathway. Buyers can review the Products overview and use the published J25 materials to create a controlled field-evaluation plan.
A J25 evaluation still needs route testing, phone-compatibility testing, message and voice workflow checks, power planning, and documented acceptance criteria. Publication of evidence is not a guarantee that the device will meet every operating environment.
Buyer next step
For current J25 procurement or a future J28 development discussion, contact ChatField with the intended market, team size, phone environment, required workflow, evidence requirements, and target schedule. Ask for model-specific documents before treating any feature or status statement as final.
Evidence note: This page deliberately limits confirmed regulatory and workflow statements to J25 and FCC ID 2BVP9-J25. It does not claim completed J28 certification, customer deployment, production availability, or guaranteed performance.