CHATFIELD
Use the phone-network path when cellular service is available.
The interface design assigns a dedicated online-send control for voice communication through the paired phone and its network connection.
J28 PROTOTYPE · LORA MESH · OFF-GRID COMMUNICATION
REQUEST B2B EVALUATION ↗
J28 · PHYSICAL PROTOTYPE STAGE
ChatField J28 smart LoRa mesh communication device prototype
J28 is a physical prototype for a more self-contained off-grid communication device intended for professional teams, distributors and product-development partners. ChatField is accepting B2B project and evaluation inquiries; no public price, certification or commercial release is claimed.
PHYSICAL PROTOTYPE · KICKSTARTER CAMPAIGN IN PREPARATIONB2B INQUIRY ONLY · NO PUBLIC PRICE · NO ONLINE PURCHASE
Kickstarter launch preparation is underway. The verified campaign link and launch timing will be published here after they are confirmed.
PROTOTYPE-BASED VISUALIZATION · NOT A FINAL PRODUCTION IMAGE
The J28 program explores a more self-contained smart PTT and LoRa mesh device while preserving the core requirement: local team communication beyond dependable cellular coverage.
A physical prototype, not a finished specification sheet.
The current J25 uses a paired smartphone as the main interface. The J28 prototype explores a separate next-generation direction with an integrated display and more selected interaction available from the device itself.
Screen workflow, radio configuration, battery, enclosure, accessories, firmware, app dependency, compliance scope and production timing remain development-controlled.
J28 FUNCTION AND INTERFACE OVERVIEW
One device concept, two communication paths and a screen-based operating workflow.
The current J28 hardware and UI design documents describe the following intended functions. They help buyers understand the product direction, but they are not a final production specification or test certificate.
Use the device LoRa path for local PTT communication.
A separate device-send control is intended to route PTT voice through the J28 LoRa radio path when the team cannot depend on cellular coverage.
Integrated touch display
The current design specifies a 3.4-inch, 480 × 854 multi-touch display so selected communication, contact and device-management tasks can be handled on J28.
Dedicated transmit controls
Separate online-send and device-send buttons are intended to make the selected communication path clear during operation. The design also identifies a power key, microphone, speaker openings and status indicator.
Private, group and nearby messages
The message design organizes direct conversations, group communication and a public or nearby-message area, with voice and PTT message handling shown in the interface workflow.
SOS message category
The current UI includes a separate SOS message category for receiving off-grid help messages. This is a local team alert workflow and is not presented as a replacement for public emergency services.
QR binding and account access
On first use, the design requires J28 to be bound through the phone app by scanning a QR code. The device password follows the phone-app account, and password login can be managed in the permission settings.
Messages and contacts
The design shows Bluetooth synchronization with the phone app for private chats, group chats, nearby messages, SOS messages, friend lists, friend details, group lists and group details.
Firmware, language and readability
The settings workflow includes firmware update, text-size adjustment, language selection, login permission and hardware-information pages.
FM radio interface
The UI design includes an FM screen with power, station search, saved stations, volume control and a minimized display.
USB-C and headset interface
The current hardware drawing identifies a Type-C connection and headset socket, together with a data-cable hook. Final connector implementation and accessory scope require engineering confirmation.
WHAT THIS SECTION DOES NOT CLAIM
The UI document does not establish final LoRa frequency, communication range, battery capacity, operating time, dimensions, weight, ingress protection, production configuration or certification. Those values must be confirmed through the final specification, test evidence and destination-market documentation.
J28 SPECIFICATION STATUS · CURRENT SOURCE: HARDWARE AND UI DESIGN DOCUMENT
Confirmed design information and pending engineering values.
This table records what the supplied J28 design document actually establishes. A pending value is intentionally not replaced with an estimate, because procurement, battery transport, radio planning and compliance decisions require model-specific engineering evidence.
- Product stage
- Physical prototype / B2B evaluation Confirmed by current project status
- Display
- 3.4-inch multi-touch Confirmed in J28 hardware design
- Display resolution
- 480 × 854 Confirmed in J28 hardware design
- Transmit controls
- Online send + device send Confirmed in J28 hardware and UI design
- Off-grid workflow
- Device LoRa PTT path Described in current UI design
- Phone relationship
- First-use QR binding + Bluetooth synchronization Described in current UI design
- Physical connections
- Type-C + headset interface Identified in current hardware drawing
- External dimensions
- Pending final mechanical drawing Not stated in the supplied UI document
- Weight
- Pending engineering confirmation Not stated in the supplied UI document
- Battery capacity
- Pending battery specification Not stated in the supplied UI document
- Operating / standby time
- Pending power validation Not stated in the supplied UI document
- LoRa frequency and range
- Pending final radio configuration and field test No J25 value is applied to J28
- Ingress protection
- Pending environmental validation No public J28 rating is claimed
- Certification
- Pending destination-market testing FCC ID 2BVP9-J25 does not apply to J28
- Public price / checkout
- Not available J28 remains B2B inquiry only
J25 AND J28 ARE SEPARATE PRODUCT PATHS
Do not use development information as a current product quotation.
Buyer questionJ25J28
Commercial statusCurrent sample and B2B quotation pathPrototype-stage B2B evaluation; no online checkout
User interfacePaired smartphone remains the interfaceMore direct device interaction under evaluation
Public FCC evidenceJ25 FCC ID 2BVP9-J25 and public reportsNo J28 FCC claim published
Public priceQuotation-controlledNo public price or checkout
Buyer next stepRequest a sample evaluationSubmit a J28 evaluation requirement
PROTOTYPE TARGETS UNDER EVALUATION
Define the operating workflow before locking the hardware.
These are development targets, not final product specifications or guaranteed functions.
LoRa mesh communication
Evaluate how participating devices exchange local team information without depending on cellular data for the radio path.
Selected screen-based workflows
Determine which PTT, message, location and alert tasks should be available directly from the device.
Initial setup and extended functions
Define which configuration, map, account or management tasks remain in the companion-phone workflow.
Professional team coordination
Translate route, terrain, team spacing and shift requirements into measurable prototype acceptance tests.
OEM and ODM scope
Align brand, enclosure, packaging, app, firmware, accessories and destination-market needs before design freeze.
Test and compliance planning
Build the verification, field-test, quality and market-document plan around the final configuration—not the rendering.
PROPOSED SYSTEM LOGIC · SUBJECT TO DEVELOPMENT
The buyer requirement determines the final interaction path.
- 01Initial setupDefine device identity, team, channel, configuration and any required phone-based administration.
- 02Operator actionEvaluate which PTT, message, location or alert tasks should be initiated on the device.
- 03Local radio pathPlan the permitted LoRa configuration and the participating device layout for the target market.
- 04Team receptionConfirm how the receiving operator views, hears, acknowledges or escalates the information.
- 05Field acceptanceTest the prototype on the actual route before any production-readiness decision.
DEVELOPMENT GATES FOR PROCUREMENT
Commercial availability begins only after the evidence is complete.
Requirement definition
Destination market, user roles, workflows, environment, team size, volume and customization scope.
Prototype definition
Hardware, firmware, interface, radio, battery, enclosure, accessories and development responsibilities.
Engineering verification
Functional, radio, power, mechanical, environmental and quality checks against written acceptance criteria.
Field evaluation
Real-route testing with the intended team layout, obstacles, movement and operator workflow.
Compliance review
Market-specific testing and documentation matched to the final hardware and radio configuration.
Production readiness
Approved bill of materials, quality plan, packaging, lead time, commercial terms and release decision.
DOCUMENT AND CLAIM BOUNDARIES
J25 documents do not certify J28.
The J25 product PDF, FCC ID 2BVP9-J25, FCC grants and J25 reports apply only to their identified model and scope. They must not be used as J28 certification, specification or commercial-readiness evidence.
Not yet published for J28
- Final technical specification
- Final production configuration
- Commercial release date
- Public certification or test-report set
- Approved public price or checkout
Required before release
- Design and configuration freeze
- Engineering and field validation
- Destination-market compliance review
- Quality and production-readiness approval
- Approved quotation and payment scope
PRODUCT VISUALIZATION BASED ON THE PHYSICAL PROTOTYPE
Front, three-quarter and side views make the current form easier to review.
This visualization is based on the orange prototype photographs. It is not a dimensioned engineering drawing, and final dimensions, enclosure details and production finish remain subject to confirmation.
REAL J28 PROTOTYPE PHOTOGRAPHY
Review the current physical form from multiple angles.
These are photographs of the current orange prototype. Enclosure finish, controls, dimensions, interfaces and final production appearance may change.
HOW A J28 B2B EVALUATION STARTS
Start with the field problem and intended market.
J28 has no public checkout. Evaluation scope, engineering work, prototype supply, tooling, certification budget and any future production price must be defined in a written B2B proposal.
- Share the market and use case.Country, field environment, team roles and the communication problem.
- List required workflows.PTT, message, location, map, alert, device-screen and phone-management priorities.
- Define the commercial framework.Estimated volume, branding, development ownership, target timing and budget range.
- Review feasibility.ChatField confirms what can be evaluated, what remains unknown and the next engineering gate.
J28 questions from procurement and development teams
Is ChatField J28 available to purchase online?
No. J28 is listed at the physical-prototype stage for B2B project and evaluation inquiries. This page intentionally provides no public price, add-to-cart button or online checkout.
When will the J28 Kickstarter campaign open?
Kickstarter campaign preparation is underway, but the public campaign link and launch timing have not yet been confirmed on this website. This page will be updated when the verified campaign destination is ready.
What is the difference between J25 and J28?
J25 is the current phone-paired LoRa mesh communication product path for sample evaluation and B2B quotation. J28 is a separate development direction exploring more selected interaction from the device itself.
What functions are described in the current J28 interface design?
The current design describes a 3.4-inch touch display, separate online and LoRa device-send controls, voice and PTT workflows, private and group communication, nearby messages, a local SOS message category, phone-app QR binding, Bluetooth synchronization of messages and contacts, FM radio, firmware update, language and text-size controls, login permissions and hardware-information pages. Final implementation still requires engineering confirmation.
Are the functions on this page final J28 specifications?
No. They are development targets used to organize buyer requirements. Final functions, hardware, firmware, radio, battery, enclosure, accessories and timing require engineering confirmation.
Does FCC ID 2BVP9-J25 apply to J28?
No. FCC ID 2BVP9-J25 and the public FCC files identify model J25. They must not be represented as J28 authorization or compliance evidence.
Can an OEM or ODM partner influence the J28 direction?
A qualified partner can submit market, workflow, volume, branding and technical requirements for feasibility review. Acceptance of a development project depends on scope, resources, timing and commercial alignment.
How is a J28 development project priced?
There is no public J28 price. Feasibility work, prototypes, engineering, tooling, certification and production are quoted only after the written development scope and responsibilities are defined.
J28 B2B INQUIRY
Start with the market, user workflow and field problem.
Tell us the destination country, operating environment, required functions, estimated volume and evaluation target.
Product document portal
Download product information or review compliance evidence.
Use the public product PDF for initial buyer evaluation. Review model-specific certification scope before deployment in a destination market.
PDF
First-generation public product document
ChatField Product Introduction
Download the English product introduction currently available in Shopify Files.
Download PDF ↓ CERT Model-specific public evidenceFCC & Compliance Center
Review FCC equipment authorization evidence and the documented battery and transport scope.
Review certification evidence →