RoarCAD

Case study ยท engineering, not fabrication

PocketRoar needs a camera bridge for iPhone

A Sony camera can expose live video, but an iPhone does not provide the same documented native USB Video Class input path that USB-C iPads do. PocketRoar therefore needs hardware and an app-specific transport that can deliver the camera feed to iPhone.

The simple version

Think of the board as a translator. It receives video from a dedicated camera, converts or compresses it into a form the phone and PocketRoar app can accept, and manages the cable, power, and connection rules between them.

The functional comparison is the Accsoon SeeMo 4K, which accepts HDMI and works with an iOS app. This does not mean RoarCAD copied SeeMo or that the current candidate implements the same proprietary architecture.

What RoarCAD actually produced

What remains unproven

GateWhy it matters
iPhone transportThe current UVC candidate does not prove an app-compatible iPhone video-ingest path.
Complete schematicEleven modeled routes are a feasibility slice, not every support circuit needed for a product.
Signal and power integrityHDMI, USB, clocks, rails, heat, and return paths require vendor models, approved stack-up, and physical measurement.
Firmware and app integrationCompression, accessory communication, reconnect behavior, latency, and sustained streaming must work together.
Manufacturing and complianceDFM, assembly, connector mechanics, licensing, EMC, and safety review happen beyond a clean digital render.
Physical prototypeOnly built hardware can prove compatibility on the exact camera, cable, iPhone, iOS version, and app.
Result: the study is useful engineering evidence, but RoarCAD correctly refuses fabrication-ready status and quoting. Zero digital errors means the modeled slice is internally clean; it does not mean the final product works.

Review the verification record and source research.