AI 产品解读Wireless screen casting and presentation tool for BenQ Board interactive displays
Enables users to wirelessly cast/mirror their Chrome browser screen and share content (documents, photos, videos, camera) to a BenQ Board display without cables, and remotely control the board
User opens the extension → selects a BenQ Board to connect to (by room code or device discovery) → optionally authenticates via board's room code → gains access to casting controls → can mirror screen, share documents/images/videos/camera, or remotely control the board → host can manage connected users and display layouts
Wireless screen mirroring to BenQ BoardDocument sharing (.doc, .xls, .pptx, .pdf)Image and photo sharingVideo sharingCamera feed sharingMultiple display layout modes (split 2/4/6/9, floating, fullscreen)
- 目标用户
- Teachers and educators using BenQ Board in classrooms / Business professionals using BenQ Board in meeting rooms / Anyone with a BenQ Board interactive display
- The main application JS file (dist/assets/index.669cf293.js, 2.6MB) is heavily minified and could not be fully searched for paid or login logic
- The extension's UI is a Vue/React SPA with routes, but most route logic is bundled in the large minified file
- No config.json was available (only config.json.example which is binary/tiny at 46 bytes)
付费分析未识别到付费功能
No premium, upgrade, subscription, license, payment, or billing-related code was found anywhere in the extension. The 'pro' keyword hits are from generic terms (project, process, protobuf in TF.js model) and are not paid-feature related. The extension connects to BenQ Board hardware via their signaling servers (benqcloud.com) — the BenQ Board itself is a commercial hardware product, but the extension is free software that interfaces with it. No payment platforms, no gated features, no upgrade prompts detected.
- 置信度
- 90
- 支付平台
- --
- 来源
- AI / 中
- 需要登录
- 否
- 登录理由
- The extension uses chrome.identity.getProfileUserInfo() only to read the Chrome browser profile's existing email for display name derivation (part before '@'). The 'authentication' and 'login' signals in the code refer to device-level connection authentication (entering a room code/password to connect to a BenQ Board display), not user account login. PASSWORD_STATE (AUTHENTICATING/SUCCESS/FAILED), HOST_STATE (IN_AUTHENTICATION), and PROJECTION_STATE (AUTHENTICATING) all relate to board pairing/approval, not account authentication. There is no OAuth flow, no account creation UI, and no external service login required to use the core workflow.