Drawing tablet driver bridge for browser-based conferencing

A teacher or creative professional plugs in a drawing tablet, opens their video conferencing tool in a browser, and finds the tablet doesn't register pressure sensitivity or even basic stylus input on the whiteboard — only the mouse cursor works. This is a complaint that shows up verbatim across Adobe Connect and other browser-based conferencing tools: 'I am not able to use my drawing tablet for the whiteboard and only the mouse.'

The reason this hasn't been fixed is architectural. Browser-based whiteboards use the standard mouse event model. Drawing tablet drivers — Wacom, Huion, XP-Pen — expose pressure, tilt, and stylus identity through OS-level APIs that browsers don't natively surface to web applications without explicit support. Fixing this inside a conferencing product requires the vendor to write and maintain native OS integrations for multiple tablet manufacturers, test across driver versions, and support hardware they don't sell. No general conferencing vendor will do this for a minority use case.

The gap is narrow and specific: someone needs to sit between the tablet driver and the browser and translate stylus events into something the browser whiteboard can consume. This is technically a solved problem in theory — browser extensions can access native messaging APIs, and some drawing apps already do this — but nobody has packaged it as a lightweight utility specifically for conferencing tool whiteboards.

Users who depend on drawing tablets for teaching — calligraphy instructors, art teachers, math tutors, anyone who bought a tablet specifically to improve their live writing — face this every session. They've already spent $80-300 on a tablet. They're highly motivated to pay a small amount to make it work. The need doesn't go away because it's a hardware-software mismatch that the conferencing vendor will never fix. That's a durable business: the customer base grows as tablet ownership among educators grows, and churn is low because switching cost is high once someone's workflow depends on it.

What to build

Build a lightweight desktop utility (Windows and Mac) that intercepts stylus input from Wacom, Huion, and XP-Pen tablets via their native SDKs and re-emits it as high-resolution Pointer Events into whitelisted browser tabs running conferencing tools, preserving pressure sensitivity and palm rejection.

Where to start

Launch first for Wacom tablets only on Windows, targeting art and handwriting teachers in Facebook groups and Reddit communities dedicated to online teaching — Wacom has the largest installed base and the most stable SDK, reducing initial maintenance burden while still covering the majority of your target users.

The hard part

Each tablet manufacturer updates their driver SDK independently, and a single driver update can silently break the event translation layer — meaning you're on a permanent maintenance treadmill for hardware you don't control, which is expensive relative to the revenue a small per-seat utility generates.

How it makes money

One-time purchase around $19-29 per user, with free updates for one year and an annual renewal fee for continued updates — keeps the price low enough for individual teachers while creating recurring revenue.